You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed elsewhere in calibration implementation the (compulsory) POINTING table is not being generated. This means that the pointing information (necessary for applying the far field response to a model) is lost on datasets that were rephased.
I suspect the following is never actually added into the generation of the dataset:
@ludwigschwardt to first order I think this needs to be filled with requested pointing values per scan - this was quite a problem for the Lunar data (we manually built the table for the AIPS data to get the PA calculations working). I understand it is probably low on the rung so to speak - I just documented the issue so that we don't forget about it
As discussed elsewhere in calibration implementation the (compulsory) POINTING table is not being generated. This means that the pointing information (necessary for applying the far field response to a model) is lost on datasets that were rephased.
I suspect the following is never actually added into the generation of the dataset:
katdal/katdal/ms_extra.py
Lines 855 to 900 in 4898eaf
The text was updated successfully, but these errors were encountered: