README CONTENTS The Readme file shall consist of the following fields. 1. Date & Time of delivery 15th July 2010 17:40 GMT 2. ICC individual to be contacted where problems arise with the delivery (1) Tanya Lim (RAL) (2) Michael Pohlen (Cardiff) Note: always copy spire@stfc.ac.uk 3. Cycle for which the data being delivered is applicable. Cycle 020 4. Delivery information - names of all files contained in the tar file SPIRE_MC_pv83_C020_57_CUS_CAL.xml SPIRE_MC_pv83_C020_57_CUS.def SPIRE_CUS_THCP.py SPIRE_Duration_57.txt SPIRE_Readme_C020_57.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_83 (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 1387 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 1387, HCSS 2.0.1 (b) Number of AOR files delivered in the .aor file CAL:6 ENG:3 (c) Overall Time Estimation calculated by HSpot - In Hours, Minutes & Seconds CAL: 1:17:44 ENG: 1:08:20 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-1492 SPIRE-2692 Astronomer AOT SxRs SPIRE-2672 Expert AOT SxRs SPIRE-2589 SPIRE-2654 SPIRE-2669 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. 2 Pallas #SPIRE-P observations for OD 458-459# ===================================== 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: ------------- A: SPhoto-SmallM-Rep4-Pallas B: SPhoto-SmallM-Rep4-AlphaTau A: SPhoto-SmallM-Rep4-GammaDra Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs B: Covered by SPIRE-PACS cross calibration #SPIRE (in REDY mode) observations for OD 460# ============================================== Scheduling instructions (for obs marked with '*'): -------------------------------------------------- This AOR should be scheduled about bi-weekly (14+-3 days) in an 'unused' DTCP time-slot when real time science is available. As suggested at planning meeting #50 this could be in the DTCP RTSW of a 2nd or 3rd non-cooler recycling PACS photometry OD. So we suggest OD 460.In case it should be done during science time. Observations: ------------- - No Pointing: A:*SpireEngDumpMemoryGen Justifications: --------------- A: A health monitoring AOR to be added to the SPIRE RCal Plan. #SPIRE (in REDY mode) observations for OD 462# ============================================== Scheduling instructions (for obs marked with '*'): -------------------------------------------------- Must be done when SPIRE is in REDY mode AND when the SPIRE cooler has run out. We suggest 462 for this. Observations: ------------- - No Pointing: A:*SpireSpectro_Cal_JfetVssTestCGen A:*SpirePhoto_Cal_JfetVssTestCGen Justifications: --------------- A: Covered by section 4.3.2 of the SPIRE routine calibration plan. #SPIRE-P observations for OD 464-467# ===================================== 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: ------------- A: SPhoto-SmallM-Rep4-GammaDra - 0001 A: SPhoto-SmallM-Rep4-Pallas - 0001 Justifications: --------------- A: Covered by RCal Plan section 4.2.4 AOTs #SPIRE-S observations for OD 466# ================================ Scheduling instructions (for obs marked with '*'): -------------------------------------------------- For the spectrometer day (here assumed to be OD466), you will need to schedule a dark observation from our RC_spec_darks.aor (delivered on Fri Jul 9 2010). This should be done at least 2h after the REDY2STBY and be of equal number (or more) of scans to the longest science observation (in time) in the day. Please note that the delivery of darks does not yet include SOF2 darks so SOF2 observations should not be scheduled until this delivery is updated. The 'Rep4-CRL618' should be done within the first 45min after the REDY2STBY if this does not incurr a significant slewing overhead. 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: ------------- A:*SpireSpectroPointGen-CR-Rep4-CRL618 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 see SPIRE_Duration_57.txt