Skip to content

Diagnose dry-run valid-MS discovery reporting zero despite staged FIELD directories #22

@jakobtfaber

Description

@jakobtfaber

Parent

Discovered during #16, under parent PRD #15.

What to build

Diagnose why batch_pipeline.py --dry-run reports Found 0 valid MS files for the staged 2026-01-25 hour-22 audit window even though the filesystem contains 11 .ms entries for that hour and each checked path has a FIELD directory. The current warning text says Skipping corrupt MS (no FIELD table), which may be misleading if the failure is actually CASA table access, adapter/runtime configuration, symlink target health, or another validation issue.

Acceptance criteria

  • Reproduce the dry-run valid-MS discovery result for 2026-01-25 --start-hour 22 --end-hour 23.
  • Capture the actual exception behind the current broad Skipping corrupt MS (no FIELD table) warning.
  • Determine whether the staged MSs are corrupt, inaccessible through the configured table adapter, affected by environment/runtime setup, or incorrectly filtered.
  • Update diagnostics so operators can distinguish a missing FIELD path from a table-open/runtime failure.
  • Add focused test coverage for the discovered failure mode without requiring real telescope data.

Blocked by

None - can start immediately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageA maintainer needs to evaluate the issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions