-
Notifications
You must be signed in to change notification settings - Fork 0
added a validation_reporting directory for AMICA #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Caroline-99
commented
Dec 17, 2025
- Added a proper validation-reporting package (src/amica/validation_reporting/) with config, loaders, pure stats, and Markdown renderers so the CXG outputs can be summarized without copy-pasted scripts.
- Added scripts/generate_validation_reports.py (main script) as the main entry point under scripts/, exposing flags for directory overrides, report selection, ontology controls, and reuse via amica.validation_reporting.generate_reports.
- Documented the workflow (docs/validation_reporting.md), covering required inputs, CLI usage, and ontology requirements, and verified the script against the real output/ data (raw and filtered report regenerated).
| Key flags: | ||
|
|
||
| - `--output-root`: base directory that contains `raw_output/`, `pandasaurus_cxg_outputs_30/`, and `reports/`. Defaults to `resources/cxg/output`. | ||
| - `--raw-output-dir`, `--match-type-dir`, `--reports-dir`: override individual directories if they live elsewhere. | ||
| - `--skip-filtered`, `--skip-examples`, `--skip-raw-stats`: toggle which reports are generated. | ||
| - `--skip-ontology`: skip the online OLS lookup entirely. | ||
| - `--ontology-adapter`: use a custom oaklib adapter string (e.g., `pronto:/path/to/cl.owl`) for offline runs. Defaults to `ols:cl`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you expand the docstring/README to explain when someone should use --raw-output-dir, --match-type-dir, or --reports-dir, and what happens if those directories are missing? Similarly, can you describe the intended use cases for the --skip-* toggles and clarify whether --skip-ontology impacts the accuracy of the filtered stats?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ubyndr I have updated the doc. Could you please review it and let me know if I need to add anything else? Thank you
ubyndr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.