Open vmahat opened 1 year ago
Hi Vijay -- okay, this is helpful. Do the *.msdpppconcat frequencies match pre-facet-target?
Hmm, seems not entirely. The number of files matches (22), but there is inconsistency of central frequency between 130 MHz and 138 MHz as above
Pre-Facet-Target:
L541949_SB000_uv_128830FFAt_127MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_127MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_129MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_129MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_131MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_131MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_133MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_133MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_135MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_135MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_137MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_137MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_138MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_138MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_140MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_140MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_142MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_142MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_144MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_144MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_146MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_146MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_148MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_148MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_150MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_150MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_152MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_152MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_154MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_154MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_156MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_156MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_158MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_158MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_160MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_160MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_162MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_162MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_164MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_164MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_166MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_166MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_168MHz.ms_concat_target_0
L541949_SB000_uv_128830FFAt_168MHz.ms_concat_target_0_CONCAT
L541949_SB000_uv_128830FFAt_168MHz.msdpppconcat
L541949_SB000_uv_128830FFAt_168MHz.msdpppconcat.h5
L541949_SB000_uv_128830FFAt_168MHz.msdpppconcat.h5imp_gsmcal
There is also an inconsistent central frequency between 4 msdpppconcat and .pre-cal_ddf.h5 files (between 130 MHz and 138 MHz), see below.
Theses msdpppconcat you are talking about come from the concatenate in Delay-Calibration right? This inconsistency might be due to a difference in reference SB that was used for the concatenate there and in prefactor. Are they the same between your prefactor and lofar-vlbi runs? Delay-Calibration.parset uses a hardcoded value:
While prefactor's default is set to None:
## concatenating the target data
! num_SBs_per_group = 10 ## make concatenated measurement-sets with that many subbands, choose a high number if running LBA
! reference_stationSB = None ## station-subband number to use as reference for grouping, "None" -> use lowest frequency input data as reference
You could to try setting reference_stationSB = None
in your Delay-Calbration parset or rerunning prefactor/LINC with the same reference SB. The former is probably easiest, as the latter would also require rerunning ddf-pipeline.
Okay, I will re-run Delay-Calibration (since it's quicker) -- we'll see what happens by Monday. Though, if this inconsistency between parsets was the cause then I'm surprised this hasn't happened before
The Delay-Calibration has now finished without errors -- thanks Frits. I'll close the ticket, but perhaps we ought to change this in the Delay-Calibration parset.
Reopening this issue because the behaviour between pre-facet-target and delay-calibration should be the same. We had to set this because there were issues of inconsistent concatenation if it wasn't set, so this needs further investigation on how to ensure it's always the same.
The Delay-Calibration part of the pipeline crashes at the beginning of the
ndppp_applycal
substep of theapply_ddf
step.This happens because Delay-Calibration has produced 22 msdpppconcat files, but there are only 21 .pre-cal_ddf.h5 files to apply. There is also an inconsistent central frequency between 4 msdpppconcat and .pre-cal_ddf.h5 files (between 130 MHz and 138 MHz), see below.
Running make_mslists.py (the script that produces "big-mslist.txt", a list of MS files used as input for ddf), that causes ddf to produce the solutions as shown here (the last subband had a flagged fraction of 95%, hence did not have a ddf h5parm, but that subband is produced by Delay-Calibration as shown, leading to the index error).
Note this is non-LoTSS data, with 48kHz subband width and 16 channels per subband.