Fix documentation: eval_type parameter and module structure#82
Merged
Conversation
- Fix eval_type="EXPVOL" to eval_type="VOL" in README, DEVELOPMENT.md, and specs (the code adds the EXP prefix internally) - Update module structure in DEVELOPMENT.md to include all 11 estimators and missing modules (evalidator, validation, utils) - Update CLAUDE.md project structure to match actual layout - Add note about variable-width EVALIDs for single-digit FIPS codes
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
eval_type="EXPVOL"toeval_type="VOL"in README, DEVELOPMENT.md, and specs — the code adds theEXPprefix internally, so passing"EXPVOL"would search for"EXPEXPVOL"evalidator,validation,utils)Test plan