1. Date & Time of delivery 23 Apr 2012 16:44 UT 2. ICC individual to be contacted where problems arise with the delivery (1) Sunil Sidher (RAL) Note: always copy spire@stfc.ac.uk 3. Cycle for which the data being delivered is applicable. Cycle 066 4. Delivery information - names of all files contained in the tar file SPIRE_MC_pv94_C066_68_CUS_CAL.xml SPIRE_MC_pv94_C066_68_CUS.def SPIRE_AOR_C066_68_CAL.aor SPIRE_AOR_C066_68_ENG.aor SPIRE_AOR_C066_68_REDYandSTBY.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C066.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_94 (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 3282 6. AOR File issues (a) HSpot, PHS & MPS versions used : Note if you don't use MPS then no need to mention it HSpot 6.1.1 PHS 718. But now using jre Java(TM) SE Runtime Environment (build 1.6.0_02-b05), rather than build 1.6.0_22-b04 (see SXR http://herschel.esac.esa.int/jira/browse/PHS-1737 for further details). MPS 1387, HCSS Track 2.0 (b) Number of AOR files delivered in the .aor file CAL: 31 ENG: 9 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 12.0 hours (12:00:03) ENG: 2.0 hours (02:02:15) 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_issueMOC13_201110111030 (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 SPIRE-4098 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. (c) Instructions for the Mission Planners - This delivery includes the following new AORs for the SPIRE mode transition scripts in the AOR file SPIRE_AOR_C066_68_REDYandSTBY.aor: SpireEngREDYtoPHOT_STBY SpireEngREDYtoSPEC_STBY SpireEngPHOT_STBYtoREDY SpireEngSPEC_STBYtoREDY The duration of each of these AORs has increased by 2 seconds. ** IMPORTANT NOTE: These new AORs should only be used from OD 1111 onwards, i.e. they can be used for the SPIRE-S ODs 1111/1112. ** - 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. Davida Hebe Thisbe Hygiea Neptune Uranus #SPIRE-P observations for ODs 1101-1102 ===================================================== 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. 1) The AORs SPhoto-PointS-Rep4-GammaDra and SPhoto-SmallM-Rep4-GammaDra should be performed contiguously. 2) The AORs SPhoto-PointS-Rep4-Neptune and SPhoto-SmallM-Rep4-Neptune should be performed contiguously. 3) The AOR SPhoto-SmallM-Rep4-Davida should be performed as late as possible in OD 1102 to avoid clouds. 4) The load curve AOR SpirePhoto_Cal_StdLoadCurveGen-DarkSky-PSWE6 should be the last observation in OD 1102 (before STBY2REDY). Observations: ------------- - Dark Sky: A: SPhoto-SmallM-Rep4-DarkSky B: SpirePhoto_Cal_PhaseUpCosine-nomBias C:*SpirePhoto_Cal_StdLoadCurveGen-DarkSky-PSWE6 - Neptune: A:*SPhoto-SmallM-Rep4-Neptune A:*SPhoto-PointS-Rep4-Neptune A: SPhoto-SmallM-Rep4-Neptune-bright - Asteroids: A:*SPhoto-SmallM-Rep4-Davida A: SPhoto-SmallM-Rep4-Thisbe A: SPhoto-SmallM-Rep4-Hebe A: SPhoto-SmallM-Rep4-Hebe-bright - Gamma Dra: A:*SPhoto-PointS-Rep4-GammaDra A:*SPhoto-SmallM-Rep4-GammaDra - Others: A: SPhoto-SmallM-Rep4-AlphaHya A: SPhoto-SmallM-Rep4-BetaPeg Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Covered by Rcal Plan section 4.2.2 Phase Ups C: Covered by Rcal Plan section 4.2.1 Detector Load Curves #SPIRE (in REDY mode) observations for ODs 1103-1110 ================================================================== Scheduling instructions (for obs marked with '*'): -------------------------------------------------- 1) The AOR SpireEngUpdateTablesGen-SM21 *must* be scheduled in OD 1103. 2) The observation SpireSpectro_Cal_JfetVssTestCGen requires the SPIRE cooler to be fully discharged. Apart from this constraint this observation can be scheduled on any PACS OD. 3) SpireEngDumpMemoryGen must be run from SPIRE REDY mode and does not require the instrument to be cold. The AOR should be scheduled about bi-weekly (14+-3 days) in an 'unused' DTCP time-slot when real time science is available (but do not mark as a real time science observation!) otherwise it should be done during science time. As suggested at planning meeting #50 this could be in the DTCP RTSW of a 2nd or 3rd non-cooler recycling PACS photometry OD, otherwise it should be done during science time. In cycle 65 we have requested that this AOR be scheduled in OD 1096 or OD 1097. For this cycle we propose to schedule it in either OD 1109. Observations: ------------- - No Pointing: A:*SpireEngUpdateTablesGen-SM21 A:*SpireEngDumpMemoryGen B:*SpireSpectro_Cal_JfetVssTestCGen Justifications: --------------- A: A health monitoring AOR to be added to the SPIRE RCal Plan. B: Covered by Rcal Plan section 4.3.2 Detectors, JFETs. #SPIRE-S observations for ODs 1111-1112 ================================================= 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. The AOR 'SpireEngSmecLedLvdtGen' should be run on the spectrometer day after the SPIRE checksum AOR (SpireEngCheckPMGen) leaving a 15min MOC reaction gap between the two (add HIFI check inbetween). This AOR must be run from SPIRE REDY mode before any cooler recycle. 1) You will need to schedule an additional High Resolution dark observation from the new AOR file RC_spec_darks_HR.aor (delivered on Mon Mar 26 2012) list. 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 HR scans (repetitions) in the day. 2) If Low Resolution science observations are planned, then you will also need to schedule an additional Low Resolution dark observation from the new AOR file RC_spec_darks_LR.aor (delivered on Mon Mar 26 2012) list. 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 LR scans (repetitions) in the day. 3) The 2 AORs SpireSpectroPointGn-HR-Rep4-Bright-highBias-DarkSky and SpireSpectroPointGn-LR-Rep4-Bright-highBias-DarkSky should be scheduled *after* the additional dark observation, as referred to in 1) above. 4) The 2 AORs SpireSpectroPointGen-LR-Rep4-Hygiea and SpireSpectroPointGen-HR-Rep4-Hygiea should only be scheduled in OD 1112 to avoid clouds. 5) The AORs SpireSpectroPointGen-LR-Rep22-DarkSky-SM02, SpireSpectroPointGen-LR-Rep4-DarkSky-SM21 and SpireSpectroPointGen-HR-Rep22-DarkSky-SM02 must be performed contiguously. 6) The AORs SpireSpectroPointGen-LR-Rep22-Uranus-SM02, SpireSpectroPointGen-LR-Rep4-Uranus-SM21 and SpireSpectroPointGen-HR-Rep22-Uranus-SM02 must be performed contiguously. 7) The AORs SpireSpectroPointGen-LR-Rep22-Neptune-SM02, SpireSpectroPointGen-LR-Rep4-Neptune-SM21 and SpireSpectroPointGen-HR-Rep22-Neptune-SM02 must be performed contiguously. 8) The load curve AORs SpireSpectro_Cal_StdLoadCurveGen-DarkSky-PSWE6, SpireSpectro_Cal_StdLoadCurveGen-Uranus and SpireSpectro_Cal_StdLoadCurveGen-Neptune should be the last three observations in OD 1112 (before STBY2REDY). Observations: ------------- - No Pointing: A:*SpireEngSmecLedLvdtGen - Dark Sky: A:*SpireSpectroPointGen-LR-Rep22-DarkSky-SM02 A:*SpireSpectroPointGen-LR-Rep4-DarkSky-SM21 A:*SpireSpectroPointGen-HR-Rep22-DarkSky-SM02 B:*SpireSpectroPointGn-HR-Rep4-Bright-highBias-DarkSky B:*SpireSpectroPointGn-LR-Rep4-Bright-highBias-DarkSky C:*SpireSpectro_Cal_StdLoadCurveGen-DarkSky-PSWE6 - Uranus: A:*SpireSpectroPointGen-LR-Rep22-Uranus-SM02 A:*SpireSpectroPointGen-LR-Rep4-Uranus-SM21 A:*SpireSpectroPointGen-HR-Rep22-Uranus-SM02 C:*SpireSpectro_Cal_StdLoadCurveGen-Uranus - Neptune: A:*SpireSpectroPointGen-LR-Rep22-Neptune-SM02 A:*SpireSpectroPointGen-LR-Rep4-Neptune-SM21 A:*SpireSpectroPointGen-HR-Rep22-Neptune-SM02 C:*SpireSpectro_Cal_StdLoadCurveGen-Neptune - Hygiea: A:*SpireSpectroPointGen-LR-Rep4-Hygiea A:*SpireSpectroPointGen-HR-Rep4-Hygiea - Others: A: SpireSpectroPointGen-LR-Rep4-AFGL2688 A: SpireSpectroPointGen-HR-Rep4-AFGL2688 A: SpireSpectroPointGen-LR-Rep4-NGC7027 A: SpireSpectroPointGen-HR-Rep4-NGC7027 A: SpireSpectroPointGen-LR-Rep4-IRC+10216 A: SpireSpectroPointGen-HR-Rep4-IRC+10216 Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: New standard darkSky for isBright setting C: Covered by Rcal Plan section 4.2.1 Detector Load Curves 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