ikf-forecast-ingest-validator

Forecast data ingest validation parses column-based CSV and heatmap-based XLS files, enforcing strict rules for tickers, horizons, and predictability values to ensure accurate mapping into canonical database rows for UI rendering.

Parsing a heatmap-based forecast file involves extracting real number signals and 0.xx predictability values, then mapping them into a Heatmap Contract output and canonical database rows for accurate dashboard rendering.

Yes, multi-format ingest supports validating both column-based CSV and heatmap-based XLS forecast files, ensuring all tickers, horizons, and real number signals conform to strict database schema rules.

During forecast data validation, strict rules enforce that signal values are real numbers and predictability values follow a 0.xx format, ensuring correct horizon mapping before data enters the canonical database structure.

Forecast horizon mapping fails during ETL ingest when horizon formats are not correctly normalized, such as failing to map '3d' to '3D', preventing accurate rendering in canonical database rows.

You do not need to manually normalize horizon formats before validating stock market forecast data, as the validation process automatically maps values like '3d' to '3D' to ensure canonical database schema compliance.