From cc0cd75ff950027e6c3ad33f53c0f96201402e5b Mon Sep 17 00:00:00 2001 From: dev Date: Tue, 13 Oct 2026 00:02:53 +0530 Subject: [PATCH] Document NUM exclusion rationale (audited, not assumed) Integer explanations end with the answer but phrasing varies enough that regex extraction would mis-key questions. A wrong key is worse than no question. NUM stays hand-added until NTA keys transcribed. --- DATA.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/DATA.md b/DATA.md index 29c29e1..92a0339 100644 --- a/DATA.md +++ b/DATA.md @@ -58,3 +58,14 @@ li table tbody thead tr th td span h3`, attributes always stripped, Re-run the importer against a newer pickle release. For NUM questions the upstream data carries no answers, so they are excluded until a verified answer source exists. The `answer` column for MCQ is a single letter. + +## Why NUM answers are not extracted from explanations + +Audited 2026-10-12: integer-question explanations do end with the numeric +result (`= 80`, `Total 11`, `is 8`), but the phrasing varies per question +(`Hence`, `Clearly`, `no. of integers in S is`, bare `= X` mid-derivation) +and several tails contain multiple numbers. A regex would mis-key a +meaningful fraction, and a wrong answer key teaches the wrong result — +worse than no question. NUM import stays out until NTA final answer keys +(authoritative per-shift source) are transcribed. The grader already +supports NUM with 0.1% tolerance for hand-added questions.