← Back
📝 Notes / reports / baseline-run-check-20260926-0950 / STATUS

📑 Contents

CASMI baseline run check — 2026-09-26 09:50 MYTCurrent stateAction

CASMI baseline run check — 2026-09-26 09:50 MYT


Current state


  • Faithful, visible-test-bank-included private kernel: jamesl8/enveda-casmi26-baseline (Enveda CASMI26 Baseline). Kaggle CLI reports KernelWorkerStatus.RUNNING. Kaggle's kernel listing shows it was created/pushed at 2026-09-26 01:24:16.843 UTC (09:24 MYT); this check was at 01:50 UTC, about 26 minutes later.
  • kaggle kernels logs jamesl8/enveda-casmi26-baseline returned no log text.
  • kaggle kernels files jamesl8/enveda-casmi26-baseline --format json returned []; kaggle kernels output ... returned no output files. No generated CSV or run logs are available to retrieve yet.
  • The previously created no-bank comparison package was removed locally at the user's request. An attempt to delete Kaggle kernel jamesl8/enveda-casmi26-haideptry-v32-baseline was rejected with HTTP 403 Forbidden; remote deletion is therefore not confirmed and requires Kaggle account permission/owner action. The current selected baseline is jamesl8/enveda-casmi26-baseline.
  • Existing local faithful package identifies the bank as haideptry/casmi26-v33-champion-artifacts, file test_verified_isomers_with_ms2.parquet; it records bank inclusion and no competition submission. This is a query-ID-keyed visible-test artifact, so results must be labeled transductive/query-specific, not hidden-test performance.
  • Local competition runtime test file has 1,213 rows and 400 unique molecule_ids. No predictions are present yet, so no validation or scores were computed.
  • The separate local replica kernel jamesl8/enveda-casmi26-haideptry-v32-replica currently reports KernelWorkerStatus.CANCEL_ACKNOWLEDGED; it is not the renamed faithful target and supplies no completion evidence for that target.

    • Action


    No output folders or prediction manifests were updated because no completed output is available. No competition submission was made. A single bounded follow-up check is scheduled for 2026-09-26 10:10 MYT; it will recheck both requested slugs and, only if outputs exist, retrieve them into version-specific folders, inspect logs, validate IDs against the runtime test set, and update the appropriate package documentation/manifests.