Skip to content

Partitioning script does not complete, ends up producing mostly *.mms.data visibility files #63

Description

@Sam-Legodi

I have been trying to use the master version of the pipeline (via: source /idia/software/pipelines/master/setup.sh) but have been met with errors mostly at the partitioning stage of the pipeline. So far, I've tried running the pipeline on several observations of similar datasets with slightly varying results. The common issue is that the partitioning stage results in *.mms.data visibility files instead of *.mms files in the sub-SPW subdirectories that are specified by the "spw" parameter in the config file. Sometimes I have had successful partitioning of data and sometimes not, leading to my confusion and unsuccessful attempts at a workaround. The partitioning stage error logs report errors like the one near the following log text:

"
2024-03-18 14:10:13 INFO msmetadata_cmpt.cc::open Performing internal consistency checks on /idia/raw/meerkat-cal/EXT-20210318-RT-01/1691421383/1691421383_sdp_l0.ms...
2024-03-18 14:10:16 INFO MSMetaData::_computeScanAndSubScanProperties Computing scan and subscan properties...
2024-03-18 14:10:22 INFO mstransform::::casa ##########################################
2024-03-18 14:10:22 INFO mstransform::::casa ##### Begin Task: mstransform #####
2024-03-18 14:10:22 INFO mstransform::::casa mstransform( vis='/idia/raw/meerkat-cal/EXT-20210318-RT-01/1691421383/1691421383_sdp_l0.ms', outputvis='1691421383_sdp_l0.12991350MHz.mms', createmms=True, separationaxis='scan', numsubms=62, tileshape=[0], field='', spw='*:12991350MHz', scan='', antenna='*&', correlation='', timerange='', intent='', array='', uvrange='', observation='', feed='', datacolumn='DATA', realmodelcol=False, keepflags=True, usewtspectrum=True, combinespws=False, chanaverage=False, chanbin=1, hanning=False, regridms=False, mode='channel', nchan=-1, start=0, width=1, nspw=1, interpolation='linear', phasecenter='', restfreq='', outframe='', veltype='radio', preaverage=False, timeaverage=False, timebin='0s', timespan='', maxuvwdistance=0.0, docallib=False, callib='', douvcontsub=False, fitspw='', fitorder=0, want_cont=False, denoising_lib=True, nthreads=4, niter=1, disableparallel=False, ddistart=-1, taql='', monolithic_processing=False, reindex=True )
2024-03-18 14:10:23 INFO ParallelDataHelper::::casa Analyzing MS for partitioning
2024-03-18 14:36:52 INFO ParallelDataHelper::::casa 15 subMSs failed to be created. This is not an error, if due to selection when creating a Multi-MS
2024-03-18 14:36:52 WARN ParallelDataHelper::go::casa Error post processing MMS results /idia/raw/meerkat-cal/EXT-20210318-RT-01/1691421383/1691421383_sdp_l0.ms: [Errno 39] Directory not empty: '/idia/projects/meerkat-cal/process/Sam/1691421383_run14/12991350MHz/1691421383_sdp_l0.12991350MHz.mms.data/1691421383_sdp_l0.12991350MHz.mms.0007.ms' -> '/idia/projects/meerkat-cal/process/Sam/1691421383_run14/12991350MHz/1691421383_sdp_l0.12991350MHz.mms.data/1691421383_sdp_l0.12991350MHz.mms.0000.ms'
2024-03-18 14:36:52 INFO mstransform::::casa Task mstransform complete. Start time: 2024-03-18 16:10:22.129315 End time: 2024-03-18 16:36:52.293223
2024-03-18 14:36:52 INFO mstransform::::casa ##### End Task: mstransform #####
2024-03-18 14:36:52 INFO mstransform::::casa ##########################################
"

OTHER error messages that I've seen are similar to the following:
"
2024-03-18 14:10:30 SEVERE mstransform::::casa::MPIServer-4 Task mstransform raised an exception of class OSError with the following message: Output MS /idia/projects/meerkat-cal/process/Sam/1691421383_run14/880933MHz/1691421383_sdp_l0.880933MHz.mms.data/1691421383_sdp_l0.880~933MHz.mms.0003.ms already exists - will not overwrite it.
"

ANOTHER thing I've noticed is that the "vis" parameter in the sub-SPW subdirectory config files is set to the raw data visibility file that is not writable, is this normal behaviour? I have been manually changing these to the name of the .mms file for each specific sub-SPW directory. I do this before submitting my jobs. I've also ran the pipeline without doing this and have seen cases where some of the scripts try to write to the raw data .ms file which is not supposed to happen.

I've attached a typical config file I use for your perusal, if needed.
1691421383_run14-default_config.txt

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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