README CONTENTS The Readme file shall consist of the following fields. 1. Date & Time of delivery 4th March 2010 17:00 GMT 2. ICC individual to be contacted where problems arise with the delivery (1) Sarah Leeks (RAL) Note: always copy spire@stfc.ac.uk 3. Cycle for which the data being delivered is applicable. Cycle 009, OD 302 in particular 4. Delivery information - names of all files contained in the tar file SPIRE_MC_ASTR_pv73_C009_50_CUS_CAL.xml SPIRE_MC_ASTR_pv73_C009_50_CUS.def SPIRE_AOR_C009_50_RCal.aor SPIRE_AOR_C009_50_SOF2.aor SPIRE_SSF_OD0302_50.ssf SPIRE_POS_OD0302_50.pos SPIRE_ICP_OD0302_50.icp SPIRE_CUS_THCP.py SPIRE_Duration_50.txt SPIRE_Readme_C009_50.txt SPIRE_SOF2_justification_updated_OD0302.pdf 5. Cus Script & Calibration files ICC internal configuration control issues (a) Name of ICC mission configuration from which files were exported (for reference purposes only) pvPhase_mconfig_73 (b) Name of the CVS Tag related to this delivery (if relevant) N/A (c) Name of the ICC Database containing this delivery (for reference purposes only) mps_phs_1 (d) HCSS Cus version used when working with these files 1387 6. AOR File issues (a) HSpot, PHS & MPS versions used : Note if you don't use MPS then no need to mention it HSpot 4.4.4 PHS 609 over 1436 (HCSS 2.3.0), MPS 1387, HCSS 2.0.1 (b) Number of AOR files delivered in the .aor file SPIRE_AOR_C009_50_RCal.aor contains 1 AOR SPIRE_AOR_C009_50_SOF2.aor contains 9 AORs (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds SPIRE_AOR_C009_50_RCal.aor : 00h18m55s SPIRE_AOR_C009_50_SOF2.aor : 15h04m00s 7. Spacecraft Database issues (a) ICC MIB version applicable to these cus & calibration files SPIRE 4.0.02 PR (b) HPSDB version (if known) that contains this MIB HPSDB_MOC_HERSCH_CCS_issueMOC5_200910261200 (c) OBSM software version on the instrument applicable to this MIB the one currently loaded on the S/C 8. Go-ahead of the ICC CCB (if applicable) Given in SDAGs and in CCB#26 9. SxRs applicable to the updates of the scripts delivered in this release - If there is an ASTR Mission Configuration delivery, then flag the high level SxR which contains the list of SxRs since the last ASTR delivery that affect a released AOT + list other SxRs that are calibration MC specific High level SxR: PHS-1347. SPIRE-2432 released aots: SPIRE-1887 (photometer inc pmode) SPIRE-2341 (spectrometer) PHS-1324 (PMode) unreleased aots: SPIRE-648 (7pt/point source) SPIRE-1887 (photometer) SPIRE-2341 (spectrometer) SPIRE-2421) (spec raster maps) other sxrs: SpireSpr:2390 , SpireSpr:2391 (these two mean HcssScr:1165 is fixed), SpireScr:2430 10. Additional notes (a) Update Information : If this corresponds to an update since the last delivery, explain what the updates consist of e.g. 2 more AORs added. The is an update delivery. We deliver SOF2 PV aors in one file and a delta Rcal observation in another. This delta Rcal observation is used instead of SpireSpectroPointGen-CR-Rep16-DarkSky sent with cycle 9. This as been done as with the SOF2 PV observations we already have 10 Reps in another observation so we have the delta observation for 6 Reps. This delta AOR is delivered in file end RCal.aor (so named because it is justfied by the RCal plan). i.e. all of the cycle 9 observations (both from this delivery and also the orginial cycle 9 deliver) get scheduled by this OD that I deliver apart from SpireSpectroPointGen-CR-Rep16-DarkSky which will remain unused. It contains SOF2 PV observations justified in SOF2_justification_update.pdf, the observations are in AOR file ending with _SOF2.aor that are to go in OD302 and as with those and our RCal cycle 9 observations we fill the non-DTCP part of the day apart from about 400s then we also provide the scheduling files (ssf, pos and icp). We also include in our scheduling an observation of IK Tau, we do not deliver an AOR for this, please used the released KPGT_mgroen_01 AOR SSpec-0000 - IK Tau - we would like this to be carried out as we would like to compare our line fluxes against the HIFI line fluxes of this object (HIFI have performed a full spectral survey of the source) and the object disappears before the next cycle and we thought it would be a waste of Helium to schedule a special calibration observation when it needs to be done for the astronomer anyway. (b) Instructions for the Mission Planners A list with all the solar system objects that are going to be observed. This will include specification of the constraints (if any) that has to be modified in the MPS properties file. none included in this delivery (but asteroid Europa observation from full delivery is scheduled in OD302) All the usual instructions about the min time for using the spectrometer etc are valid as per the scheduling guidelines. As I provide the ssf file I do not provide much in the way of scheduling guidelines, apart from: All cycle 9 observations for the spectrometer) to be scehduled and SOF2 PV observations to be scheduled in cycle 9 are scheduled in OD302 in the SSF file included in the delivery. The SSF file includes the entries for the IK Tau observation (KPGT_mgroen_01 AOR SSpec-0000 - IK Tau ) and the REDY/STBY observations. We do not deliver these observations, the HSC should schedule the AORs that they have in their database (but of course updated to use the MC delivered in this package) Justifications for the IK Tau observation given above (but it is an astronomer observation anyway). Justification for RCal delta obs see above (its covered by the plan). Justification for the PV SOF2 obs attached. 11. CusCmdscript output file (see note below) (a) Name of CusCmdScript SPIRE_CUS_THCP.py MC_ASTR_pv73_C009_50 (b) Expected durations when this is run see SPIRE_Duration_50.txt