README CONTENTS The Readme file shall consist of the following fields. 1. Date & Time of delivery 23rd May 2011 12:30 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 042 4. Delivery information - names of all files contained in the tar file SPIRE_MC_ASTR_pv89_C042_63_CUS_CAL.xml SPIRE_MC_ASTR_pv89_C042_63_CUS.def SPIRE_AOR_C042_63_CAL.aor SPIRE_AOR_C042_63_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C042_63.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_89 (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 5.3.2 PHS 668 MPS 1387, HCSS Track 2.0 (b) Number of AOR files delivered in the .aor file CAL: 19 ENG: 10 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 4.3 hours (04:15:21) ENG: 11.4 hours (11:26:02) 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 PHS-1659, SPIRE-3476 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. Uranus Ceres - Observe in ODs 775-776 (photometer only). Juno - Observe from OD768 onwards (photometer) Palma - Observe in OD 768 or in ODs 775-776 (preferred) #SPIRE-P observations for OD763 and ODs 765-766 =============================================== 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 AORs SPhoto-SmallM-Rep4-Uranus-bright and SPhoto-SmallM-Rep4-DarkSky should be scheduled on the same OD. Observations: ------------- - Uranus: A:*SPhoto-SmallM-Rep4-Uranus-bright B: SpirePhoto_Cal_StdLoadCurveGen-Uranus-PSWE6 - DarkSky: A:*SPhoto-SmallM-Rep4-DarkSky B: SpirePhoto_Cal_StdLoadCurveGen-DarkSky-PSWE6 C: SpirePhoto_Cal_PhaseUpCosine-nomBias Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Covered by Rcal Plan section 4.2.1 Detector Load Curves C: Covered by Rcal Plan section 4.2.2 Phase Ups #SPIRE (in REDY mode) observations for OD 767-769 ============================================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- SpireEngDumpMemoryGen must be run from SPIRE REDY mode and does not require the instrument to be cold.SPIRE_Readme_C042_63.txt 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 during ODs 767-769. Observations: ------------- - No Pointing: A:*SpireEngDumpMemoryGen Justifications: --------------- A: A health monitoring AOR to be added to the SPIRE RCal Plan. #SPIRE-S observations for OD767 =========================================== 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. 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 long dark observation above. Observations: ------------- - No Pointing: A:*SpireEngSmecLedLvdtGen - Dark Sky: B: SpireSpectro_Cal_StdLoadCurveGen-DarkSky C: SpireSpectro_Cal_PhaseUpCosine-nomBias A: SpireSpectroPointGn-CR-Rep4-Bright-highBias-DarkSky - Uranus: B: SpireSpectro_Cal_StdLoadCurveGen-Uranus A: SpireSpectroPointGen-CR-Rep4-Uranus D: SpireSpectroPointGen-CR-Rep4-Uranus-SSWE4-S44_0 D: SpireSpectroPointGen-CR-Rep4-Uranus-SSWE3-S40_0 D: SpireSpectroPointGen-CR-Rep4-Uranus-SSWD3-S37_0 D: SpireSpectroPointGen-CR-Rep4-Uranus-SSWC3-S41_0 D: SpireSpectroPointGen-CR-Rep4-Uranus-SSWC4-S45_0 E: SpireSpectro_Cal_ScannedSmecCrossRaster-SSWF3-S23_0 E: SpireSpectro_Cal_ScannedSmecCrossRaster-SSWB3-S25_0 - Ceres: A: SpireSpectroPointGen-CR-Rep4-Ceres - Others: A: SpireSpectroPointGen-CR-Rep4-AFGL26SPIRE_Readme_C042_63.txt88 A: SpireSpectroPointGen-CR-Rep4-AFGL4106 Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Covered by Rcal Plan section 4.2.1 Detector Load Curves C: Covered by Rcal Plan section 4.2.2 Phase Ups D: Spectrometer beam measurement E: New AORs for spectrometer beam measurement (Cross-raster SMEC scans) #SPIRE-P observations for OD 768 and ODs 775-776 =============================================== 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 SPIRE_Readme_C042_63.txtthe REDY2STBY. 1) The AORs SPhoto-SmallM-Rep4-Uranus-bright - 0001 and SPhoto-SmallM-Rep4-DarkSky - 0001 should be scheduled on the same OD. 2) The AOR SPhoto-SmallM-Rep4-Palma can be scheduled in OD 768 but we would prefer it to be scheduled in OD 775 or 776. 3) The SPhoto-SmallM-Rep4-Ceres should be scheduled in OD 775 or 776, in order to avoid clouds. 4) The AOR SPhoto-SmallM-Rep4-AlphaBoo should be scheduled in OD 775 or 776. 5) The AOR SPhoto-SmallM-Rep4-GammaCru can only be scheduled in OD 776, as it is in warm atitude on all other ODs. Observations: ------------- - Uranus: A:*SPhoto-SmallM-Rep4-Uranus-bright - 0001 - DarkSky: A:*SPhoto-SmallM-Rep4-DarkSky - 0001 - Juno: A: SPhoto-SmallM-Rep4-Juno - Palma: A:*SPhoto-SmallM-Rep4-Palma - Ceres: A:*SPhoto-SmallM-Rep4-Ceres - Others: A:*SPhoto-SmallM-Rep4-AlphaBoo A:*SPhoto-SmallM-Rep4-GammaCru Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs 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