Skip to content

Kumo-TS v1.0.1

Latest

Choose a tag to compare

@agautam478 agautam478 released this 10 Nov 16:51
· 1 commit to main since this release
30bbf68

Kumo-TS v1.0.1 adds anomaly explainability and historical attribution, missingness-aware forecasting, and inference and fine-tuning reliability improvements.

Changes since v1.0.0.

Added

  • Anomaly explanation metrics, per-feature contributions, companion CSV exports, and consolidated PDF reports. (#68, #72)
  • YAML-configured anomaly explanation settings and optional reconstruction diagnosis. (#75, #77)
  • Historical attribution for anomaly explanations, including event validation and report timestamp preservation. (#93)
  • Configurable shared feature embeddings for anomaly detection, with a positional compatibility mode. (#80)
  • Missingness-aware forecasting in the forecasting SDK: ForecastingConfig(handle_missingness=True) routes inputs with
    NaN gaps to a missingness-aware model (impute/, Backbone-LF+ CRS) that reads per-channel/per-timestep observation
    masks instead of zero-filling. Options: impute_ckpt, impute_normalization (history / provided / checkpoint),
    impute_history_rows, impute_scaler_stats, impute_source_dataset, impute_channel_alignment (name / positional),
    plus fit_impute_scaler_stats.
  • The released missingness checkpoint is loaded from hf://nvidia/Kumo-Forecast/kumo-forecast-1.2.0 (any
    hf://org/repo[@revision][/subfolder] reference or local folder is accepted).
  • examples/missingness_quickstart.py and sdk/tests/test_imputation.py (real-checkpoint tests opt-in via
    KUMO_IMPUTE_CKPT / KUMO_IMPUTE_HF / KUMO_IMPUTE_CSV).

Changed

  • Renamed the repository to Kumo-TS, forecasting to Kumo-Forecast, and AD Diffusion to Kumo-Anomaly; updated package names, directories, artifact prefixes, model references, and documentation. (#83, #84, #85, #86)
  • Added published Kumo blogs and research papers to the repository README. (#91)
  • The NULL zero-fill warning now points to handle_missingness=True; clear_model_cache() also clears cached
    missingness models.

Fixed

  • Replayed saved fine-tuning feature order and preprocessing during anomaly inference rather than fitting transforms to the scoring batch. (#32)
  • Corrected preprocess_simple target-dimension forwarding. (#44)
  • Made forecasting RevIN statistics request-local to prevent interference between concurrent calls. (#70)
  • Removed GPU-count-dependent diffusion random-number behavior. (#78)
  • Corrected DPM-Solver++ timesteps, clipped schedules, and cumulative unconditional noise; anomaly inference now uses DPM-Solver++ exclusively. (#89)
  • Restored fine-tuning run-config support for validation data, labels, dropped columns, pretrained models, and model configuration. (#90)
  • Aligned anomaly inference window, split, and scale settings with saved fine-tuned checkpoints, including preprocessing overrides and multi-device paths. (#92)

Notes

  • Repository release version: v1.0.1; package versions: kumo-forecast 1.0.1 and kumo-anomaly 1.0.1.
  • Missingness-aware forecasting is introduced by #87. Its kumo-forecast-1.2.0 model asset version is independent of SDK release 1.0.1.
  • Anomaly output remains int64 (0 = normal, 1 = anomaly). Explanation and historical attribution are opt-in.
  • Missingness-aware forecasting is inference-only in this release and cannot be combined with forecasting interpretability.

Known issues

  • Pretrained anomaly inference identifies and excludes timestamp/ground-truth columns only when reporting or historical attribution is enabled. Otherwise numeric metadata (including datetime values converted to epoch numbers) can enter the model and alter detections. Pass signal-only inputs consistently, or retain identical reporting/attribution metadata settings when selecting and explaining events. Fine-tuned checkpoints with saved feature schemas select their recorded features. See the input metadata guidance. This behavior predates 1.0.1; this release documents the workaround without changing detection behavior.

Full changelog: v1.0.0...v1.0.1