31 lines
1.6 KiB
Markdown
31 lines
1.6 KiB
Markdown
# Linear-stage Characterization Transfer Package
|
|
|
|
This package contains the reusable report workflow only. It contains no
|
|
project evidence, generated report, agent-populated values, or dependency
|
|
cache.
|
|
|
|
1. Copy the contents of this folder to the root of a new project.
|
|
2. Place new-project evidence in the empty `ECMC`, `Encoder`, `Motor`,
|
|
`Measurements`, `Measurement_System`, and `Media` folders. Keep evidence
|
|
filenames unchanged.
|
|
Keep designs and build records for FAT fixtures or adapters in `Mechanics`.
|
|
This folder is not a report input.
|
|
3. Complete the editable project fields and checklist responses in
|
|
`FAT_Checklist.xlsx`.
|
|
4. Populate `Report/python_script/Agent_Report_Data.json` only with values
|
|
supported by new-project evidence, giving each populated field its source
|
|
path under `field_sources`. Use concise source facts in displayed values;
|
|
keep evidence comments and qualifications out of report table cells. Follow
|
|
`Report_Input_Manifest.json`.
|
|
A legible, unambiguous photograph in `Media` is valid evidence for the
|
|
directly visible component or instrument information permitted by that
|
|
manifest; cite the exact image path.
|
|
5. Ensure `uv` is installed and on PATH. Run `Edit_Characterization_Report.bat`
|
|
to review and edit report, workbook, and document values in a table. The
|
|
checklist rows are read only in the app. Select
|
|
`Save changes`, then `Create working draft PDF`. The original batch launcher
|
|
remains available.
|
|
|
|
The generator expects images named `I1` through `I6` in `Media` and appends
|
|
every top-level PDF in `Measurements` in filename order.
|