R1. The prime purpose of the IARDS is to automatically display astronomical data as it is acquired. In general, it should therefore not require significant interaction from the observer or operator to function correctly. However it is acceptable to require some initialisation/configuration, and for example some further interaction when switching between projects.
R2. The IARDS should be considered a tool for the Observer (or operator acting in that capacity) performing ``standard'' astronomical observations. The assumption is that observations will have been commanded through the GO user interface, the Glish FITS files will be available, and so on.
R3. There is no requirement for the IARDS to be able to support ``engineering observations'' that have not been commanded from GO (e.g. data produced by a backend with either the Scan Coordinator or backend itself being directly commanded through CLEO)
R4. the IARDS should be launched either as part of the GO startup procedure, or in a similar manner. It is acceptable for some reasonable amount of configuration information (e.g. project id, observer's name, etc) to either be obtained from the GO session if possible, or to be required from the user.
R5. If it simplifies implementation, we should consider having the IARDS driven by commands issued from the GO observing procedures. If this approach is adopted, such commands should be well isolated, so that they may be easily removed/modified at a later date.
R6. It is acceptable for the IARDS to have to be reconfigured if, for example, the project id is changed, the IARDS application is stopped and restarted, etc (i.e. the IARDS does not need to maintain context between invocations).
R7. In general, it should be possible for the IARDS to run unattended once configured. In some situations (e.g. designation of an OFF scan to use with a given set of ONs) it is permissable to require explicit user intervention. The IARDS should default to some sensible mode of operation (e.g. display total power only) if this information is not provided.
R8. It is acceptable for some features of the IARDS (e.g. Y axis scaling) to require some user intervention (e.g. effort should not be devoted to developing advanced auto-scaling mechanisms).
R9. No accepted ``Early Science'' proposals call for continuum science observations. Therefore there is no strong requirement for the IARDS to process and display these types of observation. The only continuum observing modes to be supported initially are therefore pointing and focus measurements. These may be incorprated into the IARDS, or left in the current ``GOpoint'' procedures - see requirement 13 below. Further continuum observing modes may be incorporated at a later date if this proves straightforward; the requirements for these are not discussed here.
R10. Very few accepted ``Early Science'' proposals call for any form of mapping observation. All aspects of mapping have therefore been placed at Priority 2; i.e. should be implemented only if straightforward, and after Priority 0 and 1 items are complete.