Release 1.5.0: text_metrics_v4 and evidence refresh#23
Merged
Conversation
- Add new documentation for the Extraction & Analytics Layer Audit, detailing the scope, methodology, and findings. - Update various files to include `dictionary_version` in version outputs for consistency across metrics and scoring. - Modify `compute_section_metrics` to accept `form_type` as a parameter, ensuring accurate processing for different filing types. - Enhance extraction and scoring functions to aggregate section warnings and manage extraction metadata effectively. - Update tests to validate the inclusion of `form_type` in scoring and metrics calculations, ensuring comprehensive coverage for new features.
…s and section diffs - Update extraction and scoring processes to include `confidence_details` in responses, providing a breakdown of confidence penalties. - Modify the `_parse_blocks` function to return warnings when the section parser is unavailable, improving error handling. - Introduce `section_diffs_v2` in API responses to support enhanced analytics. - Update documentation to reflect changes in validation scopes and scoring model versions. - Add tests to ensure the correct implementation of new features and validate the presence of `confidence_details` in outputs.
- Upgrade metrics engine from `text_metrics_v3` to `text_metrics_v4`, enhancing boilerplate scoring with new ratios: `boilerplate_cross_firm_ratio` and `boilerplate_combined_ratio`. - Add a new baseline for FY2025 boilerplate 4-grams in `data/baselines/item_1a_risk_factors_boilerplate_4grams_fy2025.json`. - Update documentation to reflect changes in metrics and scoring, including the introduction of the new boilerplate metrics. - Modify scoring functions to utilize the combined ratio for improved risk assessment. - Implement scripts for building and diagnosing boilerplate baselines, ensuring accurate metric calculations across filings.
…lignment. This publishes the text_metrics_v4 narrative consistently across public docs, updates install/version pins, and keeps public-branch validation report checks aligned with files that are actually shipped. Co-authored-by: Cursor <[email protected]>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
Summary
text_metrics_v4changes already on localmain(metrics v4 + extraction/scoring fixes + audit follow-up) through a reviewable release branch1.5.0, regenerate doc artifacts, and keep validation report version checks consistent with public-branch shipped filesTest plan
python3.11 -m pytest -q -m "not integration" --cov=disclosure_alpha --cov-fail-under=75python3.11 scripts/generate_http_endpoints_docs.py --checkpython3.11 scripts/generate_docs_examples.py --checkpython3.11 -m sphinx -E -W -b html docs docs/_build/htmlMade with Cursor