Closed cyriltasse closed 1 year ago
I checked in the various parsets and did not see where the fmin/fmax of the calibration were set...
It's possible that SBs > 168 MHz don't have solutions, as more than 50% of it got flagged during prefactor. I would remove SBs at 168 MHz and higher and re-run, or reduce the `! min_unflagged_fraction = 0.5' in the prefactor parset and re-run if you really want those frequencies.
Well done! :)) I've moved this files elsewhere and I'm now rerunning the Delay-Calibration.parset
from scratch (not rerunning Pre-Facet-Calibrator.parset
and Pre-Facet-Target.parset
) - do you think it's fine?
I presume this would be fine...
do you think it's fine?
Yep that's fine. Stuff above 168 MHz is usually discarded for this reason.
Hmmm, this is a bit strange, because the pipeline has a step that specifically checks the prefactor solutions for frequency coverage. Do you have the prefactor solutions somewhere?
Hmmm, this is a bit strange, because the pipeline has a step that specifically checks the prefactor solutions for frequency coverage. Do you have the prefactor solutions somewhere?
The trick is good enough for me for now but I have posted the h5 here if you want to take a look. I close for now! Thanks for the support!
Hi
I got these error messages when running the
Delay-Calibration.parset
etc...
I checked at the
[...]/Pre-Facet-Target/results/cal_values/solutions.h5
and sawI checked and my calibrator and target MSs have exactly the same frequencies (240 MS between 120310974.12109375 and 187303161.62109375). This is how the frequencies of the dataset and TGSSphase.freq differ
I guess there is some filtering going on somewhere - maybe I need to remove some MSs and restart the processing?