Skip to content

TP Pipeline bug: No valid MSs found for imaging #311

@thomaswilliamsastro

Description

@thomaswilliamsastro

It seems that sometimes some files can be named differently to how we'd expect. I've hit:

[WARN] [          runALMAPipeline] Did not find uid___A002_X130f861_X4c3d.ms.atmcor.atmtype1_bl
[WARN] [          runALMAPipeline] Did not find uid___A002_X13128dc_X10c80.ms.atmcor.atmtype1_bl
[WARN] [          runALMAPipeline] Did not find uid___A002_X1314bf3_X186e.ms.atmcor.atmtype1_bl
[WARN] [          runALMAPipeline] Did not find uid___A002_X1314bf3_X2ae8.ms.atmcor.atmtype1_bl
[INFO] [          runALMAPipeline] No valid MSs found for imaging.

The filenames are actually uid___a002_x1314bf3_x2ae8.ms.atmcor.atmtype4_bl (4, not 1). Don't know how widespread this is or if there are other variations

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions