Repository navigation
Add resumable Agent DIC workflows and traceable scientific field analysis - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Raw DIC image sequences can now be analyzed through a headless Agent workflow with bounded parameter pilots, resumable per-frame computation, quality states and traceable scientific exports. The existing GUI, 1D extensometer, campaign workflow and
ezDICcommand/executable compatibility remain available.The new
straintrace agentCLI andstraintrace_agentPython API cover project creation, input inspection, planning, analysis, cancellation/recovery, batch execution, verification, field plotting, ROI/path extraction and export. Native frame identity and missing-frame time gaps are preserved. Mechanics synchronization requires explicit clock/units/gap constraints; physical displacement and stress require supplied calibration and area. Unsupported values remain unavailable.Field analysis adds consistent strain validity masks, Green–Lagrange and infinitesimal components/principal values, fixed-reference virtual gauges, sparse common-scale maps, position–time plots and labeled mechanics/gauge histories. CSV, safe NPZ checkpoints, strict JSON, content hashes and reports distinguish numerical quality from experimental validation. No third-party DIC source code was copied.
The reproducible
examples/agent/create_demo.py --runworkflow exercises known deformation, clock offset/unit conversion, bounded load interpolation, missing/corrupt frames, field extraction, checkpoint reuse, batch execution, source integrity and lock recovery. CI runs it through both an installed wheel and the Windows portable CLI.Checkpoint reuse binds exact native/source/reference/time identity and the planned solver parameters; direct execution validates the plan checksum. Cancelled/incomplete runs cannot report a numerical pass, stale post-processing bindings are rejected before writes, runtime failures can retry, and repeated
analyze/batchreuse a current plan and run. Windows transient replacement and strict cp1252 JSON output are covered.Validation on runtime
9662c9eaand final example8ad47cb:Reproduce the complete synthetic experiment after installing the project dependencies:
The workflow uses fixed-reference in-plane 2D DIC. Automatic ROI/gauge candidates do not confirm physical specimen geometry. Experimental uncertainty calibration, stereo/3D DIC and crack topology tracking are outside this change. A numerical quality pass does not approve a scientific interpretation. Long path scatter plots retain their selected samples; the field guide documents direct streaming CSV extraction for millions of samples without invoking that renderer.