count-exact-rows-before-you-fit-a-correction
SolidUse at implementation and experimentation when the target may be a deterministic function of the inputs - a computed score, a derived column, a simulator or rule-based output - your reconstruction of it is close but not equal, and the next thing you planned was to train a model on the difference. Covers the fraction-reproduced-exactly measure that mean error hides, how to choose its tolerance from the residuals instead of by taste, how to read a residual that takes only a few distinct values, and the gate a learned correction must clear before it goes on top of an analytic base.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- tangxiangru
- Repository
- tangxiangru/AutoR
- Created
- 6 months ago
- Last Updated
- 2 weeks ago
- Language
- Python
- License
- NOASSERTION
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
chemistry-reproduce-the-scoring-path-before-you-replace-it
Use at implementation, experimentation and analysis when you are reproducing a published benchmark number and the source's scoring path is one you can read — which rows are scored, in what order, how many the loader drops, which epoch is reported, how tasks are pooled, over how many seeds. Covers implementing that path exactly before improving it, the one-row-per-step ladder from the published rule down to your own honest estimate, and why one un-replicated step makes the reproduction gap you report uninterpretable.
a-cut-point-is-a-fitted-parameter-not-a-setting
Use whenever a column of your submission is decided by comparing a continuous score against a number you chose -- whether to commit an answer or declare the row unanswerable, whether to flag a borderline case, which output to emit when the model is unsure. Covers the two questions that number silently answers, why it gets fitted on the smallest labelled sample in the run and then applied to the largest split, the statistic it should have been swept on, and the commit-rate print-out that tells you it is on the wrong side of the tail.
rseng-numerical-accuracy
Covers floating-point correctness in research code: why 0.1 + 0.2 != 0.3, choosing absolute vs relative tolerances in tests, accumulation error and safe summation, precision choices (float32 vs float64), catastrophic cancellation, NaN and infinity handling, and cross-platform or cross-library result drift. Use PROACTIVELY when floating-point comparisons fail mysteriously, when writing numerical tests or choosing tolerances, when results differ across machines, compilers, BLAS builds or library versions, or when precision or numerical stability questions arise in analysis or simulation code.