(1) Date & Time of delivery: 17 Feb 2011, 18:30 CET (2) ICC individual to be contacted when problems arise with the delivery: (1) M. Nielbock (2) Z. Balog (3) V. Doublier-Pritchard (4) U. Klaas (3) Time range for which the data being delivered is applicable Cycle 35 (4) Names of all files contained in the TAR file: PACS_MC_OT1_2011-02-17A_C035_62_CUS.def PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml PACS_AOR_C035_62.aor PACS_Duration_PACS_compare.txt PACS_Readme_C035_62.txt 2createOBSMODtable4RP.sh (5) CUS script & Calibration files ICC internal configuration control issues: (a) Version and name of ICC mission configuration from which files were exported: Version 62 of delivered Mission Configurations OT1_2011-02-17A provided by: PACS_MC_OT1_2011-02-17A_C035_62_CUS.def PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml (b) Name of the CVS Tag related to this delivery (if relevant) (c) Name of the ICC Database containing this delivery verification@pacs-up1.mpe.mpg.de (d) HCSS version used when working with these files HCSS CIB Track 5.0 (6) AOR File issues: (a) HSpot, PHS & MPS versions used PACS Expert HSPOT Version 5.2.2 PHS Version 5.2.2 (Build 650) based on HCSS 5.0, Build 1760 MPS based on HCSS 5.0, Build 1760 (b) Number of AORs delivered in all delivered .aor files 26 (c) Overall Time Estimation calculated by HSpot for all delivered AORs 06h33m03s (7) Spacecraft Database issues: (a) ICC MIB version applicable to these CUS & Calibration files merged: CDMS 3.10 ACMS 4.1 PACS MIB version 9.4 HIFI MIB version 11.12 SPIRE MIB version FM 4.0.02 RMS (Support MTL provided by ESOC) (b) HPSDB version that contains this MIB HPSDB_MOC_HERSCH_CCS_issueMOC5_200910261200.zip (c) OBSM software version on the instrument applicable to this MIB DPU V9.04 (SUM 3.4 available) SPU HLSW V13.96 (SUM 13.96 available) DMC V6.034 (SUM available V4.8) (8) Go-ahead of the ICC CCB (if applicable): MC endorsed by PACS ICC CCB on 15 and 17 February 2011 (9) SXRs applicable to the updates of the scripts delivered in this release: PACS-3428 affecting astronomer mission configuration: none (10) Additional notes e.g. messages for mission planning, etc.: (a) Default avoidance settings can be used. (b) Number of SSOs contained in this delivery: one asteroid 4 Vesta (c) BURST mode is NOT requested. (e) Gyro propagation is not requested. (f) AOR distribution according to ODs and PACS sub-instruments: PACS Engineering (to be scheduled on PACS OD 665) ================================================= RPElecEDAC_811A_5476A_0_na_0007 This AOR must be scheduled immediately before the final orbit epilogue of this OD. PACS Engineering (to be scheduled on PACS OD 678) ================================================= RPElecEDAC_811A_5476A_10_na_0006 This AOR must be scheduled immediately before the final orbit epilogue of this OD. PACS PHOT (to be scheduled on PACS PHOT/SPEC OD 677) ==================================================== RPPhotFlux_323A_cPS_106Jy_blu_c35_Vesta_03 RPPhotFlux_323B_sPS_070_106Jy_blu_c35_Vesta_03 RPPhotFlux_323B_sPS_110_106Jy_blu_c35_Vesta_03 RPPhotSpatial_314C_StdScan045_med_blu_Vesta_0001 RPPhotSpatial_314C_StdScan135_med_blu_Vesta_0001 RPPhotSpatial_314C_StdScan045_med_grn_Vesta_0001 RPPhotSpatial_314C_StdScan135_med_grn_Vesta_0001 These blocks shall be scheduled in the indicated sequence. They should be the last PACS PHOT observations on that OD, to be scheduled right before the PACS SPEC observations on the same target. The PACS PHOT observations should finish with a photometer orbit epilogue with the internal calibration sources kept on. PACS PHOT (to be scheduled on any PACS PHOT OD) =============================================== RPPhotFlux_324A_cPS_2Jy_grn_gamDra_0003 RPPhotFlux_324B_sPS_070_2Jy_grn_gamDra_0003 RPPhotFlux_324B_sPS_110_2Jy_grn_gamDra_0003 These blocks shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS SPEC OD 665) =============================================== RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0034 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0034 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0034 RPSpecAOTVal_525D_nStdLSnCBrigh_A_2x2_NGC6543_1 RPSpecAOTVal_525D_nStdLSnCBrigh_B_2x2_NGC6543_1 RPSpecAOTVal_525B_nStdLSnCFaint_OICII_2x2_NGC6946_1 RPSpecAOTVal_525C_nStdLSnCBrigh_OICII_2x2_NGC6946_1 RPSpecAOTVal_525B_nStdLSnCFaint_OICII_2x2_NGC6946_2 RPSpecAOTVal_525C_nStdLSnCBrigh_OICII_2x2_NGC6946_2 The blocks shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 677) ==================================================== RPSpecFlux_433A_StdRange_AbsFluxA_Vesta_0002 RPSpecFlux_433A_StdRange_AbsFluxB_Vesta_0002 RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0035 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0035 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0035 These blocks shall be scheduled in the indicated sequence. The observations done on Vesta should be the first PACS SPEC observations on that OD, to be scheduled right after the PACS PHOT observations on the same target. The PACS SPEC observations should begin with a spectrometer orbit prologue with the internal calibration sources kept on. (11) CusCmdscript output file: (a) Name of CusCmd Script 2createOBSMODEtable4RP.sh Syntax to run this script: 2createOBSMODEtable4RP.sh NOTE! Please check that the appdir variable in the script reflects the latest HCSS installation. (b) Expected durations when this is run: contained in PACS_Duration_PACS_compare.txt