agent couldn't parse sweep results with missing values and failed with a missing data error
Handle missing values as data, not as parse failures: sweep tables legitimately contain blanks where runs crashed or metrics were never logged. Use when an agent analysing sweep results that include crashed runs. Not for a file whose missing values come from a truncated export rather than crashed runs, where the fix is re-exporting completely.
TL;DR
Handle missing values as data, not as parse failures: sweep tables legitimately contain blanks where runs crashed or metrics were never logged. Parse with per-cell tolerance, represent missing as an explicit null in the output, and keep the run in the dataset with its missing fields marked, because dropping crashed runs biases every sweep conclusion toward the survivors.
agent couldn't parse sweep results with missing values and failed with a missing data errorUse this when
- The run or call fails with this symptom: agent could not parse sweep results with missing values and failed with a missing data error.
- You are working on an agent analysing sweep results that include crashed runs and the failure repeats on the same run or configuration.
- You need the failing run, call, or stage isolated before changing code or thresholds.
Not for this skill when
- A file whose missing values come from a truncated export rather than crashed runs, where the fix is re-exporting completely.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.
Steps
- Locate the cells the parser rejected and confirm they are empty or placeholder values, such as NaN strings, rather than corruption. Verify: the missing values' form is identified
- Adjust parsing to map the observed placeholders to nulls while keeping strictness on genuinely malformed rows. Verify: the table parses with nulls preserved
- Check which runs the missing values belong to and whether they cluster on crashed configurations. Verify: the missingness pattern is understood
- Produce the analysis with missing-aware statistics and the crashed-run count stated alongside. Verify: conclusions account for the incomplete runs
Variant phrasings
agent parse sweep results missing values missing data error
The verbatim phrasing.
sweep results blanks crashed runs agent parser tolerant fix
The tolerant phrasing.
agent sweep analysis failed empty metric cells nulls
The nulls phrasing.
Compatibility: Agent parsers reading sweep result tables with missing values
Why it happens
Missingness in sweep output is information, usually about which configurations crash, and parsers that demand complete rows throw away exactly the evidence the sweep existed to gather. The parse error is the tool refusing the dataset's most honest feature.
Edge cases / pitfalls
- Placeholders vary by exporter, empty, NaN, null, dashes; catalogue the ones in your exports explicitly.
- A metric missing on every run points to a logging bug, not crashes; the pattern decides the interpretation.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_ihMlFsc2Vnupy34u9lAX6Q