Other AIPS++ Dependencies

SDCalc is relying on ongoing development within aips++. The following are known items SDCalc will need to pay attention to and use when ready.

Help

A prototype help system written in will be available sometime this fall.. We will use this as soon as it is ready.

Parameters and state

We need to be able to store previously used parameters and other state information. It is not clear where this stands within aips++. We will need to use a short term solution.

MeasurementSet development

The MeasurementSet has just been reviewed. The primary data axis remains frequency. The design of SDCalc is intentionally isolated from that of MeasurementSet however the SDIterator will need attention whenever MeasurementSet changes. It will continue to be impossible to store a general SDRecord in a MS.

Single dish FITS IO

An initial SD-FITS reader and writer to and from a MeasurementSet is still not available. This will eventually be the main path of UniPOPS DATA into aips++ and hence SDCalc. A direct FITS storage manager is required so that an SD-FITS file can be used as an SDIterator.

UniPOPS SDD IO

In order for the 12m and 140' to be useful beta sites it must be easy to get SDD data into SDCalc. This can initially be via SD-FITS (which will require some work in UniPOPS by Garwood) but eventually users will expect a MeasurementSet to be built directly from an SDD file (i.e. the SDD storage manager will need to be revived). This is not required for a considerable length of time.

M&C

While not an aips++ dependency, the activity of GBT Monitor and Control will impact SDCalc development. This includes the long term support we have been providing for engineering work. It also includes dealing with new backends and new Data Associated Parameter files and changes in the existing DAP files. This is difficult to predict.