README CONTENTS The Readme file shall consist of the following fields. 1. Date & Time of delivery 08th November 2010 22:00 BST 2. ICC individual to be contacted where problems arise with the delivery (1) Michael Pohlen (Cdiff) Note: always copy spire@stfc.ac.uk 3. Cycle for which the data being delivered is applicable. Cycle 028 4. Delivery information - names of all files contained in the tar file SPIRE_MC_pv87_C028_61_CUS_CAL.xml SPIRE_MC_pv87_C028_61_CUS.def SPIRE_AOR_C028_61_CAL.aor SPIRE_AOR_C028_61_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C028_61.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_87 (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 1528 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 1528, HCSS 2.0.1 (b) Number of AOR files delivered in the .aor file CAL: 19 ENG: 11 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 5:54:15 ENG: 4:51:21 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: PhsScr:1563 + Astronomer AOT SxRs: PhsScr:1559, SpireScr:2958 + Expert AOT SxRs: 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. 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. Neptune, Uranus, 3 Juno, 6 Hebe, 173 Ino #SPIRE-S observations for OD 571# ================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- The SPIRE-S day needs to be the first of the two SPIRE days covered with the cooler. The AOR 'SpireEngSmecLedLvdtGen' should be run on the spectrometer day following the SPIRE checksum AOR (SpireEngCheckPMGen) leaving a 15min MOC reaction gap between the two. This AOR must be run from SPIRE REDY mode before any cooler recycle. 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. The isBright dark SpireSpectroPointGn-CR-Rep4-Bright-highBias-DarkSky should be scheduled after the additional dark observation above. 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. Observations: ------------- - No Pointing: A:*SpireEngSmecLedLvdtGen - Neptune: B: SpireSpectroPointGen-CR-Rep4-Neptune C: SpireSpectro_Cal_BsmAngleCalGen-jiggle-SSWD4 C: SpireSpectro_Cal_BsmAngleCalGen-chop-SSWD4 - Uranus: B: SpireSpectroPointGen-CR-Rep4-Uranus D: SpireSpectro_Cal_StdLoadCurveGen-Uranus - DarkSky: E:*SpireSpectroPointGn-CR-Rep4-Bright-highBias-DarkSky D: SpireSpectro_Cal_StdLoadCurveGen-DarkSky C: SpireSpectro_Cal_BsmAngleCalGen-jiggle-SSWD4-Dark C: SpireSpectro_Cal_BsmAngleCalGen-chop-SSWD4-Dark - other: B: SpireSpectroPointGen-CR-Rep4-NGC7027 B: SpireSpectroPointGen-CR-Rep4-AFGL2688 Justifications: --------------- A: A new ENG-AOR for non Spec cycles to be added to the SPIRE RCal Plan. B: Covered by RCal Plan section 4.2.4 AOTs C: Covered by RCal Plan: Monitor the BSM Angle Calibration D: Covered by Rcal Plan section 4.2.1 Detector load curves E: New standard darkSky for isBright setting #SPIRE-P observations for OD 572# ===================================== 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. Please note, there are 3 additional SPIRE-P RC calibration AORs requested for OD573-576 (see below). They can be moved to here, OD572, if that improves the scheduling efficiency. If possible we would like to have the load curve with Pcal On SpirePhoto_Cal_LoadCurvePcalOnGen-DarkSky-PSWE6 scheduled at the end of the SPIRE-P OD. Observations: ------------- - GammaDra: A: SPhoto-SmallM-Rep4-GammaDra A: SPhoto-PointS-Rep4-GammaDra - DarkSky: A: SPhoto-SmallM-Rep4-DarkSky B: SpirePhoto_Cal_StdLoadCurveGen-DarkSky-PSWE6 B:*SpirePhoto_Cal_LoadCurvePcalOnGen-DarkSky-PSWE6 - Uranus: A: SPhoto-SmallM-Rep4-Uranus-bright B: SpirePhoto_Cal_StdLoadCurveGen-Uranus-PSWE6 - other: A: SPhoto-SmallM-Rep4-Neptune 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 OD 573-576# ===================================== 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. Please note, these 3 SPIRE-P RC calibration AORs requested can be moved to OD572 if that improves the scheduling efficiency. Observations: ------------- - BetaPeg: A: SPhoto-SmallM-Rep4-BetaPeg A: SPhoto-PointS-Rep4-BetaPeg - other: A: SPhoto-SmallM-Rep4-Ino Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs #SPIRE-P observations for OD 577-578# ===================================== 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. We would like to have as many of these AORs as possible in the second day, i.e. OD578. Observations: ------------- - mixed: A: SPhoto-SmallM-Rep4-Juno A: SPhoto-SmallM-Rep4-GammaDra - 0001 A: SPhoto-SmallM-Rep4-Neptune - 0001 A: SPhoto-SmallM-Rep4-DarkSky - 0001 B: SPhoto-LargeM-Rep4-15x15-Hebe B: SPhoto-LargeM-Rep4-15x15-Uranus-bright Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Covered by the Herschel-Planck Cross calibration plan #SPIRE (in REDY mode) observations for OD 579 # ============================================================= Scheduling instructions (for obs marked with '*'): -------------------------------------------------- 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 it in OD579 a PACS-S/PACS-P day. 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