1. Date & Time of delivery 16 Jan 2012 16:10 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 059 4. Delivery information - names of all files contained in the tar file SPIRE_MC_ASTR_pv92_C059_66_CUS.def SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml SPIRE_AOR_C059_66_CAL.aor SPIRE_AOR_C058_67_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C059_66.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_90 (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.0 PHS 705 MPS 1387, HCSS Track 2.0 (b) Number of AOR files delivered in the .aor file CAL: 14 ENG: 4 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 3.6 hours (03:37:09) ENG: 0.3 hours (00:19:40) 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 N/A 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. (b) The AOR SpireEngLoadAllTablesGen does not need to be scheduled in this cycle, and there are no plans to schedule it in any future cycles. It is included in this delivery for completeness and because its duration has increased by one second, as a result of an additional command to set the size of an obsolete OBS table. The corresponding procedure at the MOC, which is a contingency procedure, has already been updated accordingly. (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. Iris Europa Harmonia Juno #SPIRE (in REDY mode) observations for ODs 1001-1004 and 1013-1014 ================================================================== Scheduling instructions (for obs marked with '*'): -------------------------------------------------- 1) The AOR SpireEngUpdateTablesGen must be run from SPIRE REDY mode and does not require the instrument to be cold. This AOR updates an OBS table which is to be subsequently used for all SPIRE Spectrometer single pointed sparse observations. It must be scheduled as early as possible in this cycle, i.e. well before the SPIRE-S ODs in this cycle. We request that this AOR be scheduled between ODs 1001-1004 2) 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 58 we have requested that this AOR be scheduled in OD 999. For this cycle we propose to schedule it in OD 1013. Observations: ------------- - No Pointing: A:*SpireEngUpdateTablesGen B:*SpireEngDumpMemoryGen Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: A health monitoring AOR to be added to the SPIRE RCal Plan. #SPIRE-P observations for ODs 1005/1006 ===================================================== 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. Observations: ------------- - Dark Sky: A: SPhoto-SmallM-Rep4-DarkSky - Asteroids: --------------- A: SPhoto-SmallM-Rep4-Iris A: SPhoto-SmallM-Rep4-Europa A: SPhoto-SmallM-Rep4-Europa-bright A: SPhoto-SmallM-Rep4-Harmonia - Gamma Dra: A:*SPhoto-PointS-Rep4-GammaDra A:*SPhoto-SmallM-Rep4-GammaDra - Others: A: SPhoto-SmallM-Rep4-EpsLep A: SPhoto-PointS-Rep4-AlphaAri A: SPhoto-PointS-Rep4-AlphaAri-bright Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs #SPIRE-S observations for ODs 1011-1012 ================================================= 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 dark observation from our RC_spec_darks.aor (delivered on Fri Jul 9 2010) 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 scans (repetitions) in the day. 2) The AOR SpireSpectroPointGn-CR-Rep4-Bright-highBias-DarkSky should be scheduled *after* the additional dark observation, as referred to in 1) above. Observations: ------------- - No Pointing: A:*SpireEngSmecLedLvdtGen - Dark Sky: B:*SpireSpectroPointGn-CR-Rep4-Bright-highBias-DarkSky Asteroids: A: SpireSpectroPointGen-CR-Rep12-Juno - Others: A: SpireSpectroPointGen-CR-Rep4-NGC6302 A: SpireSpectroPointGen-CR-Rep4-AFGL4106 Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: New standard darkSky for isBright setting 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