Simulation of beam models and visibilities DD corrections

Step 1: there is an ongoing discussion concerning the validity of the simulated polarisation response for SKA1-LOW. In PI5, the SKA1-LOW beam model was implemented in the LOFAR software. A comparison should be made between the results produced by the two independent software package to build confidence in these simulations and/or pinpoint errors that need to be corrected. At the end of this step, we should have two packages that predict the same instrumental response for SKA1-LOW. This is the main goal in PI6

Step 2: These simulations of the instrumental response should be combined with the simulation of ionospheric corruptions developed in SP-651 to allow realistic simulation of DD effects along a given line of sight including both instrumental and ionospheric effects. This is a stretch goal for Pi6.

Step 3: Create and make available a small number of reference visibility data sets for SKA1-LOW with varying levels of DD corruptions (beam, ionosphere). These simulations should be accompanied by a set of reference beam images/models and/or the scripts for generating them. These should be large enough to cover the first few side lobes of the primary beam and do not need to generated at the full time or frequency resolution of the visibility simulation. Another way to keep the size of the simulated visibility set manageable is to use fewer stations, for example those identified for AR1 or AR2. This is a stretch goal for PI6.

Step 4: Set up a similar simulation for SKA1-MID building on the results from SP-651 to model the troposphere. Due to capacity constraints, this will not be done in PI6.

Step 5:  Create and make available a small number of reference visibility data sets for SKA1-MID with varying levels of DD corruptions (beam, troposphere). These simulations should be accompanied by a set of reference beam images/models and/or the scripts for generating them. These should be large enough to cover the first few side lobes of the primary beam and do not need to generated at the full time or frequency resolution of the visibility simulation. Another way to keep the size of the simulated visibility set manageable is to use fewer dishes, for example those identified for AR1 or AR2. This is a stretch goal for PI6. Due to capacity constraints, this will not be done in PI6