README CONTENTS The Readme file shall consist of the following fields. 1. Date & Time of delivery 15th January 2010 16: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 007 4. Delivery information - names of all files contained in the tar file SPIRE_MC_ASTR_pv64_C003_43_CUS.def SPIRE_MC_ASTR_pv64_C003_43_CUS_CAL.xml SPIRE_AOR_C007_44.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C007_44.txt 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_65 (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 1786 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.3.5, PHS 593 over 1721 (reported as 1), (MPS 1724) (b) Number of AOR files delivered in the .aor file 23 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds 07h06m02s 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) N/A 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 SpireScr:2227, SpireScr:2297, SpireScr:2300, SpireScr:2308 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. N/A (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. Juno All the usual instructions about the min time for using the spectrometer etc are valid as per the schedulung guidelines. All of the observations for a sub instrument should be scheduled together in one block (except for those observations where it is explicited stated otherwise below) as much as possible except if this means that long slews are necessary (and hence it leads to less efficient use of observatory time) (and obviously observations on the same target within a sub-instrument should be scheduled together). Observations should be scheduled on the second day of a cooler recycle period and towards the end of the period of use of the sub-instruemnt. Following discussions with HSC our spectrometer cycle 6 calibration observations are actually being carried out in cycle 7 on OD260. In addition we also require that all spectrometer observations delivered in cycle 7 are also carried out on this OD (apart from the Vss test - see below). Sorry that the following additional instructions are a bit much, we will update our scripts in the near future to make it less complicated (concaternation is not possible). In addition, please schedule the following observations according to the following instructions In order for the aims of the PV-SOF2 observations to be carried out correctly it is necessary to schedule observation SpireEngUpdateTablesGen-0000 while SPIRE is in REDY mode, i.e before running SpireEngREDYtoSpec_STBY and before running the SOF2-PV observations. This can be done before or after the cooler recycle (but generally better to do afterwards as it gives longer (21s only though) for the cooler to stabilise. For the Vss tests, i.e. SpirePhoto_Cal_JfetVssTestCGen-0000 and SpireSpectro_Cal_JfetVssTestCGen-0000, the script starts from SPIRE REDY then go back to SPIRE REDY at the end (i.e. it is a standalone test that needs nothing else scheduled with it) and the observations need to be done at 4K rather than 300mK (not cold) can't be done on SPIRE/PMode days and shouldn't be done just after a SPIRE day as the cooler needs to be properly run out. They are no pointing observations (so can be done in a DTCP if you like). Probably it would be best to schedule them during PACS 2nd or 3rd OD DTCP for example. They can be scheduled together or separately. Note that the observations with PV-SOF2 in the label are actually PV observations, not routine calibration. They should all be scheduled together. Photometer observations with the word 'copy' at the end of the AOR label should be placed in a photometer OD about a week away (roughly) from the main set of photometer observations delivered for this cycle as these observations should be carried out about weekly. Photometer order for observations with AOR labels starting with the following, the set of observations should be scheduled as listed, note there are Dark Sky sets (without and with - copy in the label) and Juno sets: SpirePhotoPcalFlashGen... SpirePhoto_Cal_StdLoadCurveGen... SpirePhotoPcalFlashGen... Spectrometer order for observations with AOR labels starting with the following, the set of observations should be scheduled as listed, note there are just a set for target Juno: SpireSpectroPcalFlashGen SpireSpectro_Cal_StdLoadCurveGen SpirespectroPcalFlashGen 11. CusCmdscript output file (see note below) (a) Name of CusCmdScript SPIRE_CUS_THCP.py MC_ASTR_pv65_FULL_44 (b) Expected durations when this is run see SPIRE_Duration.txt