Fort7 Workflow
Direct command workflow for repairing corrupted fort.7 files.
This module implements CLI workflow orchestration for its command family, including argument parsing, request construction, execution dispatch, and result presentation handoff.
Usage context
- Command routing: Resolve CLI aliases and normalized command names.
- Task execution: Build request objects and invoke registered tasks.
- Output handling: Forward results to table, plot, export, or report flows.
Command: repair_fort7
Arguments
No command-specific arguments found.
Common Runtime and Presentation Arguments
These are shared workflow-level CLI flags added before command-specific options, covering runtime context (engine/input/storage) and output presentation/export behavior.
| Flag | Required | Default | Help | Choices |
|---|---|---|---|---|
--file |
No | fort.7 | Input fort.7 file. Example: --file runs/job1/fort.7, which reads that file as repair source. | |
--output |
No | fort7_fixed | Output repaired fort.7 file. Example: --output fort7_repaired, which writes repaired content using that output name. | |
--progress-every |
No | 5000 | Progress interval in lines (stored for metadata compatibility). Example: --progress-every 10000, which records progress in larger line-step chunks. | |
--copy-to-dot |
No | Also copy generated output to current directory. Example: --copy-to-dot, which keeps a convenience copy where you run the command. | ||
--run-id |
No | Run identifier for run-scoped layout (e.g., run_91ac0e). | ||
--project-root |
No | Project root that contains inputs/, data/, analysis/, etc. | ||
--analysis-id |
No | Optional analysis artifact id; defaults to run id. |