Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1367

News	FAQ
Search	Home

Calibration and Associated Processing

• Calibration, like flagging, should be reversible, with the ability to store calibration information and apply it ``on-the-fly''. However, it should also be possible to apply calibration information ``once-and-for-all'', creating a new, calibrated data-set.
• Calibration should be made as generic as possible; site-specific/instrument dependent code should be kept to a minimum.
• Calibration of data should be possible from derived tables of instrumental parameters such as system temperature and gain vs. elevation. It should be possible to derive such tables from calibration observations.
• The calibration process should include flexible interpolation and averaging of calibration data under the control of the user.
• Redundancy (possibly including crossing points) should be used whenever possible, as an additional constraint on calibration and self-calibration.
• Model fitting should be possible in both the image and uv-planes, and it should be possible to use the resultant model in the same way as a CLEAN component model in calibration and self-calibration.
• Fringe fitting (normally only for VLBI data) should be possible by baseline, as well as globally.
• Cross-calibration of different instruments should be possible, (e.g. flux scale, pointing) particularly where data from different arrays are to be combined.