Closed landmanbester closed 3 years ago
As discussed, the single correlation path is still a work in progress. For now, setting input_ms.select_corr=[0,0]
will solve the problem (by virtue of making the problem appear diagonal). We can leave this open as a reminder to me to communicate when this changes.
Setting input_ms.select_corr=[0,0] solves the problem
The master branch should now work correctly for single correlation MSs, provided you use the complex
or slow_complex
solvers. I am still working on the parameterised terms.
I am going to close this - I believe that all the solvers now correctly handle 1,2 and 4 correlation data. Please reopen if you encounter problems.
I ran into this while trying to calibrate a tiny MS I split out for testing purposes. Definitely an edge case. MS and parset are on oates at /home/bester/projects/ESO137/msdir/ms1_primary_scan1_corrXX_chan950to1050.ms and /home/bester/projects/ESO137/qcal_1gc.yaml respectively. I can reproduce the segfault locally as well. Interestingly two consecutive runs produces slightly different errors viz.
and
Any idea what could be going wrong here @JSKenyon?