1. Date & Time of delivery 29 July 2011 12:00 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 047 4. Delivery information - names of all files contained in the tar file SPIRE_MC_pv90_C047_64_CUS.def SPIRE_MC_pv90_C047_64_CUS_CAL.xml SPIRE_AOR_C047_64_CAL.aor SPIRE_AOR_C047_64_ENG.aor SPIRE_AOR_C047_64_REDYandSTBY.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C047_64.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 2106 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.0.1 PHS 690 MPS 1387, HCSS Track 2.0 (b) Number of AOR files delivered in the .aor file CAL: 13 ENG: 7 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 3.5 hours (03:28:32) ENG: 1.6 hours (01:36:44) 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 SPIRE-SCR-3622 SPIRE-SCR-3624 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. This delivery includes the following new AORs for the SPIRE mode transition scripts in the aor file SPIRE_AOR_C047_64_REDYandSTBY.aor: SpireEngREDYtoPHOT_STBY SpireEngREDYtoSPEC_STBY SpireEngPHOT_STBYtoREDY SpireEngSPEC_STBYtoREDY The duration of each of these AORs has increased by 2 seconds. (b) The AOR SpireEngUpdateTablesGen-SM02 must be scheduled before the first SPIRE OD in this cycle. (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. Alexandra Hygiea #SPIRE (in REDY mode) observations for ODs 834-835 ============================================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- The AOR SpireSpireEngUpdateTablesGen-SM02 (duration 15 seconds) updates a table of BSM positions on-board and must be scheduled before the start of the first SPIRE day in this cycle. Since ODs 836-837 are SPIRE days, this AOR should ideally be scheduled on OD 834. Execution of this AOR should have no impact on HIFI or PACS. Observations: ------------- - No Pointing: A:*SpireSpireEngUpdateTablesGen-SM02 Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs #SPIRE-S observations for OD 836-837 ================================================= 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 SMEC scans (repetitions) in the day. 2) The AORs SpireSpectroPointGen-CR-Rep4-SM02-CRL618 and SpireSpectroPointGen-CR-Rep4-SM02-AFGL4106 *must* be scheduled using the SPIRE internal MC pvPhase_mconfig_90 in this delivery, which corresponds to the HSC MC S64. Please also note that these non-standard AORs test the effect of change in BSM positions and are not suitable for release to the public. 3) The three Dark Sky AORs SpireSpectroPointGen-HR-Rep16-DarkSky, SpireSpectroPointGen-MR-Rep16-DarkSky and SpireSpectroPointGen-LR-Rep16-DarkSky must be scheduled contiguously. 3) The AORs SpireSpectro_Cal_StdLoadCurveGen-DarkSky and SpireSpectro_Cal_StdLoadCurveGen-Hygiea *must* be the last two SPIRE-S observations in OD 837 (before STBY2REDY). Observations: ------------- - No Pointing: A:*SpireEngSmecLedLvdtGen - DarkSky: A:*SpireSpectroPointGen-HR-Rep16-DarkSky A:*SpireSpectroPointGen-MR-Rep16-DarkSky A:*SpireSpectroPointGen-LR-Rep16-DarkSky B:*SpireSpectro_Cal_StdLoadCurveGen-DarkSky B:*SpireSpectro_Cal_StdLoadCurveGen-Hygiea - CRL618: A: SpireSpectroPointGen-CR-Rep4-CRL618 A:*SpireSpectroPointGen-CR-Rep4-SM02-CRL618 - must use MC S64! - AFGL4106: A: SpireSpectroPointGen-CR-Rep4-AFGL4106 A:*SpireSpectroPointGen-CR-Rep4-SM02-AFGL4106 - must use MC S64! - Hygiea: A: SpireSpectroPointGen-CR-Rep4-Hygiea Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Covered by Rcal Plan section 4.2.1 Detector Load Curves #SPIRE-P observations for ODs 840-841 ===================================================== 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 Gamma Dra AORs SPhoto-SmallM-Rep4-GammaDra and SPhoto-PointS-Rep4-GammaDra should be scheduled contiguously. 2) The AOR SPhoto-SmallM-Rep4-Alexandra should ideally be scheduled as late as possible on OD 841 to avoid clouds. Observations: ------------- - DarkSky: A: SPhoto-SmallM-Rep4-DarkSky - Gamma Dra: A:*SPhoto-SmallM-Rep4-GammaDra A:*SPhoto-PointS-Rep4-GammaDra - Asteroids: A: SPhoto-SmallM-Rep4-Hygiea A:*SPhoto-SmallM-Rep4-Alexandra - Others: A: SPhoto-SmallM-Rep4-BetaUmi A: SPhoto-SmallM-Rep4-GammaCru Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs #SPIRE (in REDY mode) observations for ODs 843-846 ============================================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- 1) 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. We propose to do this observation in OD 843. Observations: ------------- - No Pointing: A:*SpireEngDumpMemoryGen Justifications: --------------- A: A health monitoring AOR to be added to the SPIRE RCal Plan. 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