GBD Processing Validation
Data meaning, uncertainty, age mappings and normalization rules live in the GBD method. Keep processing code in the calling project; this reference is an operational checklist.
- Confirm that fresh results match the reviewed query and round before exporting. Follow the first-download guide.
- Preserve the original export and its schema. Write derived tables and validation reports separately under the task output directory in
AIRMOSAIC_ASSETS_DIR; cache publication is a separate authorized operation.
- Define an explicit mapping from source dimensions to project columns. Join by the full applicable key, including round, context, year, location, measure, metric, cause/risk, age and sex; do not assume project aliases such as endpoint or agegroup are source fields.
- Compare mapped values to source rows within a declared numeric tolerance. Report requested combinations missing from the source, unexpected derived combinations, duplicates, non-finite values and invalid uncertainty ordering.
- Keep raw exports, derived health tables, account information and temporary download links outside Git. Share only a reviewed summary.