README CONTENTS The Readme file shall consist of the following fields. 1. Date & Time of delivery 24th September 2010 15:40 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 025 4. Delivery information - names of all files contained in the tar file SPIRE_MC_pv85_C025_60_CUS_CAL.xml SPIRE_MC_pv85_C025_60_CUS.def SPIRE_AOR_C025_60_CAL.aor SPIRE_AOR_C025_60_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C025_60.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_86 (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: 7 ENG: 3 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 2:34:31 ENG: 0:35:38 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: PHS-1537, SPIRE-2842 + Astronomer AOT SxRs: SPIRE-2808 + 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. 1 Ceres, 7 Iris #SPIRE (in REDY mode) observations for OD 527 or OD 531-534 # ============================================================= 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 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. For scheduling it with PACS this time only OD527 is available. If there is 'unused' DTCP time-slot available in OD527 it should be scheduled there. However, if the DTCP is anyway used for science we would prefer to place it somewhere in the nominal science time of the HIFI block OD 531-534. This is closer to the 14 day cycle and after a SPIRE block. Observations: ------------- - No Pointing: A:*SpireEngDumpMemoryGen Justifications: --------------- A: A health monitoring AOR to be added to the SPIRE RCal Plan. #SPIRE-P observations for OD 528-529# ===================================== 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. Observations: ------------- - GammaDra: A: SPhoto-SmallM-Rep4-GammaDra A: SPhoto-PointS-Rep4-GammaDra - DarkSky: A: SPhoto-SmallM-Rep4-DarkSky B: SpirePhoto_Cal_StdLoadCurveGen-DarkSky-PSWE6 - DeltaDra: C: SPhoto-SmallM-Rep4-DeltaDra C: SPhoto-PointS-Rep4-DeltaDra - others: A: SPhoto-SmallM-Rep4-Ceres D: SPhoto-LargeM-Rep4-15x15-Iris Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Covered by Rcal Plan section 4.2.1 Detector load curves C: Cross calibration with PACS D: Covered by Herschel-Planck cross calibration #SPIRE (in REDY mode) observations for OD 530# ============================================== Scheduling instructions (for obs marked with '*'): -------------------------------------------------- This observation should be scheduled for those cycles where no spectrometer day is present (currently odd numbered cycles 21, 23, 25 etc). It should be run approximately 14 days before and after each SPIRE spectrometer day. This AOR could be scheduled in an 'unused' DTCP time-slot when real time science is available, otherwise it should be done during science time. It is best to schedule this on a non-HIFI day. We propose to run this in OD530. This script must be run from SPIRE REDY mode and does not require the instrument to be cold. Observations: ------------- A:*SpireEngSmecScanGen Justifications: --------------- A: A new ENG-AOR for non Spec cycles 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