README CONTENTS The Readme file shall consist of the following fields. 1. Date & Time of delivery 16th August 2010 17:50 GMT 2. ICC individual to be contacted where problems arise with the delivery (1) Tanya Lim (RAL) Note: always copy spire@stfc.ac.uk 3. Cycle for which the data being delivered is applicable. Cycle 022 4. Delivery information - names of all files contained in the tar file SPIRE_AOR_C022_58_CAL.aor SPIRE_AOR_C022_58_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C022_58.txt SPIRE_MC_pv84_C022_58_CUS_CAL.xml SPIRE_MC_pv84_C022_58_CUS.def 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_84 (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 5.0.5 PHS 626 over 1579 (HCSS 3.0.0), MPS 1387, HCSS 2.0.1 (b) Number of AOR files delivered in the .aor file CAL:12 ENG:11 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 4:20:22 ENG: 1:44:01 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) SPIRE gives go ahead 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 SXRs: N/A + Astronomer AOT SxRs: N/A + Expert AOT SxRs: SPIRE-2761 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 new Program Memory check script is called SpireEngCheckPM. It is intended for daily execution from the MTL at the start of an OD, but only when SPIRE is in REDY mode. It takes 45 seconds to execute and does not require the SPIRE bus profile to be selected. No science data are generated by this observation. Other AORs which also need to be delivered are: SpireEngREDYtoPHOT_STBY SpireEngPHOT_STBYtoREDY SpireEngREDYtoSPEC_STBY SpireEngSPEC_STBYtoREDY This is because of changes to the reporting of VM tables as described in http://herschel.esac.esa.int/jira/browse/SPIRE-2761. These are delivered as the mode transistion scripts need to be delivered each time they are changed. They are applicable to all SPIRE REDY/STBY mode transitions. It is recommended to start using both the SPIREEngCheckPM script and the mode transition scripts from the earliest possible date. (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. 1 Ceres 93 Minerva 29 Amphitrite #SPIRE (in REDY mode) observations for OD 484 or 485# ============================================== Scheduling instructions (for obs marked with '*'): -------------------------------------------------- This AOR should be scheduled about bi-weekly (14+-3 days) in an 'unused' DTCP time-slot when real time science is available. As suggested at planning meeting #50 this could be in the DTCP RTSW of a 2nd or 3rd non-cooler recycling PACS photometry OD. So we suggest OD 484 or 485. It should be done during science time. Observations: ------------- - No Pointing: A:*SpireEngDumpMemoryGen Justifications: --------------- A: A health monitoring AOR to be added to the SPIRE RCal Plan. #SPIRE-P observations for OD 486-487# ===================================== Scheduling instructions (for obs marked with '*'): -------------------------------------------------- Note, after the REDY2STBY there is no longer the need to wait any time before the first science observation can be scheduled. However, it would still be nice if you could move any left-over seconds in the schedule to right after the REDY2STBY. Observations: ------------- A: SPhoto-LargeM-Rep4-15x15-Ceres B: SPhoto-SmallM-Rep4-GammaDra B: SPhoto-PointS-Rep4-GammaCru B: SPhoto-SmallM-Rep4-GammaCru A: SPhoto-SmallM-Rep4-DarkSky Justifications: --------------- A: Observed for cross calibration with Planck and PACS B: Covered by RCal Plan section 4.2.4 AOTs #SPIRE-P observations for OD 492-493 or 495# ============================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- Note, after the REDY2STBY there is no longer the need to wait any time before the first science observation can be scheduled. However, it would still be nice if you could move any left-over seconds in the schedule to right after the REDY2STBY. Observations: ------------- A: SPhoto-SmallM-Rep4-Minerva A: SPhoto-SmallM-Rep4-GammaDra - 0001 A: SPhoto-PointS-Rep4-GammaDra A: SPhoto-SmallM-Rep4-DarkSky - 0001 B: SPhoto-LargeM-Rep4-15x15-Amphitrite C: SpirePhoto_Cal_PhaseUpCosine-nombias Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Observed for cross calibration with Planck and PACS C: Covered by RCal Plan: Phase-ups #SPIRE-S observations for OD 494# ================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- For the spectrometer day (here assumed to be OD494), you will need to schedule a dark observation from our RC_spec_darks.aor (delivered on Fri Jul 9 2010). This should be done at least 2h after the REDY2STBY, and be of equal number (or more) of SMEC scans (repetitions) to the SOF1 or SOF2 science observation with the most SMEC scans (repetitions) in the day. The AOR 'SpireEngSmecLedLvdtGen' needs to be scheduled BEFORE the mandatory cooler recycle in the day. Note, the SPIRE-S day needs to be the first of the two SPIRE days covered with the cooler. Note, after the REDY2STBY there is no longer the need to wait 10min! However, it would still be nice if you could move any left-over seconds in the schedule to right after the REDY2STBY. The observation SpireSpectro_Cal_StdLoadCurveGen-DarkSky should be scheduled at the end of the SPIRE spectrometer day (before SPECSTBY to REDY). Observations: ------------- A:*SpireEngSmecLedLvdtGen B:SpireSpectro_Cal_PhaseUpCosine-nomBias C:SpireSpectro_Cal_PhaseUpCosine-highBias B:*SpireSpectro_Cal_StdLoadCurveGen-DarkSky B:SpireSpectroPointGen-CR-Rep4-CRL618 B:SpireSpectroPointGen-CR-Rep4-Ceres Justifications: --------------- A: Switching on SMEC before cooler recycle allows for stabilisation and improves quality of first hour science B: Covered by RCal Plan C: Observation in support of bright source release (remaining PV) #SPIRE Engineering observations ================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- The new Program Memory check script is called SpireEngCheckPM. It is intended for daily execution from the MTL at the start of every OD (including non-SPIRE days), replacing the manual check currently done at MOC. It must be only executed when SPIRE is in REDY mode therefore the second day after a cooler recycle should be excluded. It takes 45 seconds to execute and does not require the SPIRE bus profile to be selected. No science data are generated by this observation. This script should be used from the earliest convienient date. The four mode transition scripts are baseline AOTs to be copied for execution at the start and end of SPIRE days as appropiate. Observations: ------------- A:*SpireEngCheckPMGen-0000 B:*SpireEngREDYtoPHOT_STBYGen-0000 B:*SpireEngPHOT_STBYtoREDYGen-0000 B:*SpireEngREDYtoSPEC_STBYGen-0000 B:*SpireEngSPEC_STBYtoREDYGen-0000 Justifications: --------------- A: Automates a manual procedure increasing safety and reducing risk B: See SPIRE-2761 11. CusCmdscript output file (see note below) (a) Name of CusCmdScript SPIRE_CUS_THCP.py (b) Expected durations when this is run SPIRE_Duration.txt