Errors and Exit Codes
| Signal | Meaning | Recovery |
|---|---|---|
Exit 0 |
Command completed its software contract. | Inspect artefact statuses and diagnostics. |
Exit 1 |
A resolved stage failed during validation or execution, or inference returned failed. |
Read the terminal error and stage logs; no reportable result is available. |
Exit 2 |
Argument parsing or initial CLI configuration resolution failed. | Correct the command syntax or config path/content. |
GeoLiftConfigError |
Config file, value, or supported SparseSC key is invalid. | Correct the named key or path. |
GeoLiftDataError / analysis data error |
Panel cannot be prepared under the selected policy. | Fix identifiers, dates, duplicates, gaps, non-finite values, or windows. |
GeoLiftResultsError |
SparseSC output cannot satisfy the result contract. | Preserve logs and inspect estimator output; do not substitute zeros. |
GeoLiftPlotterError |
Plot construction failed. | Use JSON results only after verifying they completed; fix map or plotting inputs separately. |
Power valid: false |
No successful simulations or failure rate above threshold. | Do not use the row for MDE; diagnose simulation failures. |
Inference partial |
Estimate exists with warnings or incomplete uncertainty. | Resolve or disclose every warning before use. |
Inference failed |
Required result fields or gates failed. | Do not report an effect; redesign or repair. |
Unknown non-sparse_sc_* YAML keys are not comprehensively rejected. If a
setting appears ineffective, compare it with the exact stage configuration
reference rather than assuming it was applied.