Skip to content

Add H5 compatibility checks for mp-300k exports #14

@MaxGhenis

Description

@MaxGhenis

Parent plan: #16

Goal: prevent a dataset from becoming release-track unless it satisfies the PolicyEngine-US H5 contract.

Deliverables:

  • Add an automated H5 compatibility check against the current policyengine-us loader.
  • Validate entity tables, IDs, joins, weights, periods, dtypes, and missing-value conventions.
  • Validate that source-dataset diagnostic variables are absent from the exported model data.
  • Produce a machine-readable compatibility report for the dashboard.

Exit criterion: every mp-300k release candidate has a passing compatibility report before publication.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions