PACS Cycle 40 ASTR MC and HSpot 5.3.1 back-end update delivery for GT2 Call closure 1. Delivery Note PACS Delivery note - 28th April 2011 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of the PACS RP calibration cycle#40 tar file onto the CVS server. 1. Delivery file & directory (a) OD tar file name : CYCLE040_PACS_FULL_1_20110428.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle040, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES 2. Mission Configurations (a) Does this delivery include a new Calibration mission configuration? YES (b) Does this delivery include a new ASTR mission configuration? YES 3. Operations Issues (TC,HPSDB,SIAM,Real Time Science) (a) Will any of these delivered observations generate a significant amount of telecommands? NO (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? NO (c) ICC to add anything specific which HSC & MOC should be aware of The delivery contains AORs of four SSOs, three asteroids: 1 Ceres, 3 Juno, 4 Vesta, one planet: Neptune. The delivery contains the following PACS RP calibration blocks: (for an overview, please see PACS Routine Phase Calibration Plan, PICC-MA-PL-002. Section numbers refer to the currently released issue 1.50.) * RPPhotFlux 3.2.1A&B, PACS RP Cal Plan, section 6.2 on gamma Dra monitor absolute flux calibration reproducibility of the photometer * RPPhotFlux 3.2.3A&B, PACS RP Cal Plan, section 6.3 on 1 Ceres, 4 Vesta calibration of flux non-linearity of photometer * RPPhotFlux 3.2.4A, PACS RP Cal Plan, section 6.3 on 3 Juno monitor the photometer linearity and absolute flux calibration for scan map point source mode * RPPhotFlux 6.3.1A, PACS RA Cal Plan, section 10.6 on Neptune, 3 Juno Herschel/Planck cross calibration * RPSpecGeGa 1.2.3A, PACS RP Cal Plan, section 8.2 on dark field check of CRE capacitance ratios * RPSpecWave 4.2.1A, PACS RP Cal Plan, section 6.6 on NGC 5643 spectrometer wavelength calibration * RPSpecFlux 4.3.3A&B, PACS RP Cal Plan, section 6.8 on Neptune monitor the spectrometer linearity and absolute flux calibration at key wavelengths chopped & unchopped * RPSpecFlux 4.3.4A, PACS RP Cal Plan, section 6.7 on HD 161796 monitor absolute flux calibration reproducibility of the spectrometer * RPSpecFlux 6.1.1A&B, PACS RP Cal Plan, section 10.10 on Neptune PACS PHOT/SPEC cross calibration, chopped and unchopped SED scan * RPElecEDAC 8.1.1A, PACS RP Cal Plan, section 7.4 no pointing monitor the EDAC addresses of single memory failures Scheduling instructions per OD (from Readme file): PACS Engineering ================ RPElecEDAC_811A_5476A_10_na_0011 This AOR must be scheduled immediately before the PACS-S orbit epilogue on OD735. PACS PHOT (to be scheduled on any PACS PHOT OD) =============================================== RPPhotFlux_321A_cPS_repro_blu_gamDra_0028 RPPhotFlux_321B_sPS_070_repro_blu_gamDra_0028 RPPhotFlux_321B_sPS_110_repro_blu_gamDra_0028 The block shall be scheduled in the indicated sequence. PACS PHOT (to be scheduled on PACS PHOT/SPEC OD 739) ==================================================== RPPhotFlux_631A_sPS_070_Planck_blu_Neptune_0003 RPPhotFlux_631A_sPS_110_Planck_blu_Neptune_0003 RPPhotFlux_631A_sPS_070_Planck_grn_Neptune_0003 RPPhotFlux_631A_sPS_110_Planck_grn_Neptune_0003 This block shall be scheduled in the indicated sequence. The observations on Neptune 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 PACS PHOT OD 743) =============================================== RPPhotFlux_323A_cPS_211Jy_blu_c40_Vesta_03 RPPhotFlux_323B_sPS_110_211Jy_blu_c40_Vesta_03 RPPhotFlux_323B_sPS_070_211Jy_blu_c40_Vesta_03 RPPhotFlux_323A_cPS_120Jy_grn_c40_Vesta_03 RPPhotFlux_323B_sPS_070_120Jy_grn_c40_Vesta_03 RPPhotFlux_323B_sPS_110_120Jy_grn_c40_Vesta_03 RPPhotFlux_323A_cPS_174Jy_blu_c40_Ceres_03 RPPhotFlux_323B_sPS_110_174Jy_blu_c40_Ceres_03 RPPhotFlux_323B_sPS_070_174Jy_blu_c40_Ceres_03 RPPhotFlux_323A_cPS_95Jy_grn_c40_Ceres_03 RPPhotFlux_323B_sPS_070_100Jy_grn_c40_Ceres_03 RPPhotFlux_323B_sPS_110_100Jy_grn_c40_Ceres_03 These blocks shall be scheduled in the indicated sequence. PACS PHOT (to be scheduled on PACS PHOT/SPEC OD 745) ==================================================== RPPhotFlux_324A_cPS_20Jy_blu_Juno_0003 RPPhotFlux_631A_sPS_070_Planck_blu_Juno_0002 RPPhotFlux_631A_sPS_110_Planck_blu_Juno_0002 RPPhotFlux_324A_cPS_10Jy_grn_Juno_0003 RPPhotFlux_631A_sPS_110_Planck_grn_Juno_0002 RPPhotFlux_631A_sPS_070_Planck_grn_Juno_0002 This block shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on any PACS SPEC OD) =============================================== RPSpecWave_421A_StdLS_NGC6543_A_0017 RPSpecWave_421A_StdLS_NGC6543_B_0017 This block shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS SPEC OD 735) =============================================== RPSpecGeGa_123A_nStdCalBlock_Cf00_60-2_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf08_60-2_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf04_60-2_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf12_60-2_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf00_60-3_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf08_60-3_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf04_60-3_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf12_60-3_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf00_75-2_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf08_75-2_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf04_75-2_DField_0002 RPSpecGeGa_123A_nStdCalBlock_Cf12_75-2_DField_0002 This block shall be scheduled right after the PACS-S orbit prologue and in the indicated sequence. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 739) ==================================================== RPSpecFlux_433A_StdRange_AbsFluxA_Neptune_0003 RPSpecFlux_433A_StdRange_AbsFluxB_Neptune_0003 RPSpecFlux_433B_StdRange_UnchopFluxB2A_Neptune_01 RPSpecFlux_433B_StdRange_UnchopFluxB2A_NeptuneOff_1 RPSpecFlux_433B_StdRange_UnchopFluxB2B_Neptune_01 RPSpecFlux_433B_StdRange_UnchopFluxB2B_NeptuneOff_1 RPSpecFlux_433B_StdRange_UnchopFluxB3A_Neptune_01 RPSpecFlux_433B_StdRange_UnchopFluxB3A_NeptuneOff_1 RPSpecFlux_611A_StdSED_sedb2a_Neptune_0003 RPSpecFlux_611A_StdSED_sedb2b_Neptune_0003 RPSpecFlux_611A_StdSED_sedb3a_Neptune_0003 RPSpecFlux_611B_StdSED_nochop_sedb2a_Neptune_0001 RPSpecFlux_611B_StdSED_nochop_sedb2a_NeptuneOff_01 RPSpecFlux_611B_StdSED_nochop_sedb2b_Neptune_0001 RPSpecFlux_611B_StdSED_nochop_sedb2b_NeptuneOff_01 RPSpecFlux_611B_StdSED_nochop_sedb3a_Neptune_01 RPSpecFlux_611B_StdSED_nochop_sedb3a_NeptuneOff_01 This block shall be scheduled in the indicated sequence. The observations done on Neptune should be the first PACS SPEC observations on that OD, to be scheduled right after the PACS SPEC orbit prologue with the internal calibration sources kept on. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 745) ==================================================== RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0042 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0042 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0042 This block shall be scheduled in the indicated sequence. Please acknowledge the receipt of the e-mail and the delivery. Best regards, Markus. Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE040_PACS_FULL_1_20110428.tar New MCs - MC P66ASTR 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Thu Apr 28 08:47:31 2011 from herl38.net4.lan HCSS Version: 6.1.0 PHS Version: 5.3.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account 3. What is the Mission Configuration Name going to be?? MC_H76ASTR_P66ASTR_S61ASTR_AO 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle33> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle33/HIFI> mkdir PACS_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle040_PACS_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the SPIRE & PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H76ASTR_P66ASTR_S61ASTR_AO folder. Next remove in the SPIRE & HIFI subfolders all files which were created when you ran the SPIRE duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H62ASTR_P58ASTR_S61ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> ls CYCLE028_SPIRE_FULL_1_0_20101108.tar SPIRE_harness_duration_summary_20101109_15h38m18s.log SPIRE_AOR_C028_61_CAL.aor SPIRE_harness_duration_summary_20101123_09h34m04s.log SPIRE_AOR_C028_61_ENG.aor SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv87_C028_61_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C028_61.txt SPIRE_Duration.txt HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H76ASTR_P64ASTR_S61ASTR_RP/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0032_C039_76_CUS_CAL.xml importall.sh* CYCLE039_HIFI_FULL_2_20110413.tar HIFI_MC_ASTR_A0032_C039_76_CUS.def Summary_durations.txt default-durations.dat HIFI_MC_ASTR_A0032_C039_76.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> rm Summary_durations.txt rm: remove regular file `Summary_durations.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0032_C039_76_CUS_CAL.xml importall.sh* CYCLE039_HIFI_FULL_2_20110413.tar HIFI_MC_ASTR_A0032_C039_76_CUS.def default-durations.dat HIFI_MC_ASTR_A0032_C039_76.txt 6(a) Download & Untar the HIFI delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/HIFI/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> cvs login Logging in to :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle040/CYCLE040_PACS_FULL_1_20110428.tar U develop/data/observingmodes/rp_cycles/cycle040/CYCLE040_PACS_FULL_1_20110428.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle040/CYCLE040_PACS_FULL_1_20110428.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/PACS/PACS_FULL_1> ls CYCLE040_PACS_FULL_1_20110428.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/PACS/PACS_FULL_1> tar -xvf CYCLE040_PACS_FULL_1_20110428.tar PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml PACS_AOR_C040_66.aor PACS_Duration_PACS_compare.txt PACS_Readme_C040_66.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/PACS/PACS_FULL_1> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt CYCLE040_PACS_FULL_1_20110428.tar PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml develop/ PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def PACS_AOR_C040_66.aor PACS_Readme_C040_66.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C040_66.txt CYCLE040_PACS_FULL_1_20110428.tar PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml PACS_AOR_C040_66.aor PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def 6(b) To import the new PACS delivery: #CUS #var.hcss.instrument = SPIRE var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> Apr 28, 2011 4:08:01 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 4:08:02 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:08:02 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 28, 2011 4:08:12 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT PACS IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Apr 28, 2011 4:08:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 4:08:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:08:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:08:45 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Apr 28, 2011 4:09:08 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 4:09:09 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:09:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:09:14 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Set GYRO properties and import new Mission Configuration (Version 66.0). setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> cus -m "upload PACS_MC P66ASTR mission config" -import PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def -importcaltables PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml Apr 28, 2011 4:13:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 4:13:43 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 28, 2011 4:14:08 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:14:08 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 28, 2011 4:14:15 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by PACS: PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml CONFIRMED!! 6(e) Run the duration script for the PACS instrument model: Point duration script to latest HCSS version... (6.1.0) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C040_66.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> ls -ls total 11668 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 28 16:17 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 28 16:17 2createOBSMODtable4RP.sh~* 5812 -rw-r--r-- 1 hscphs2 herschel 5939200 Apr 28 15:59 CYCLE040_PACS_FULL_1_20110428.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Apr 28 16:20 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 80 Apr 28 16:20 msgPacsCal_PacsSpecSlewCal35_Flex.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Apr 28 16:17 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Apr 28 16:20 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Apr 28 16:19 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Apr 28 16:20 msgPacsRangeSpec.txt 208 -rw-r--r-- 1 hscphs2 herschel 205638 Apr 28 15:27 PACS_AOR_C040_66.aor 4 -rw-r--r-- 1 hscphs2 herschel 3927 Apr 28 15:39 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 3927 Apr 28 16:20 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404163 Apr 28 15:02 PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml 5200 -rw-r--r-- 1 hscphs2 herschel 5308486 Apr 28 15:02 PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 9415 Apr 28 15:55 PACS_Readme_C040_66.txt 4 -rw-r--r-- 1 hscphs2 herschel 2321 Apr 28 16:17 tmp 4 -rw-r--r-- 1 hscphs2 herschel 989 Apr 28 16:17 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS MC P66ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. Now create the MC in the database hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> missetup -addconfig MC_H76ASTR_P66ASTR_S61ASTR_AO Apr 28, 2011 10:36:43 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 10:36:46 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:36:47 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Apr 28, 2011 10:36:55 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H76ASTR_P66ASTR_S61ASTR_AO" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Add the commited CUS to the new MC hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/PACS> Apr 28, 2011 4:22:43 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 4:22:44 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:22:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:22:45 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 28, 2011 4:23:10 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H76ASTR_P66ASTR_S61ASTR_AO" Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:23:29 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 28, 2011 4:23:39 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H76ASTR_P66ASTR_S61ASTR_AO Apr 28, 2011 4:23:55 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H76ASTR_P66ASTR_S61ASTR_AO" Apr 28, 2011 4:23:57 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(b) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> Apr 28, 2011 10:38:39 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 10:38:41 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:38:41 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 28, 2011 10:39:04 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Apr 28, 2011 10:39:23 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 10:39:24 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:39:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:39:35 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Apr 28, 2011 10:40:13 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 10:40:14 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:40:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 10:40:19 AM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (H76_ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> cus -m "upload HIFI MC H76ASTR mission config" -import HIFI_MC_ASTR_A0032_C039_76_CUS.def -importcaltables HIFI_MC_ASTR_A0032_C039_76_CUS_CAL.xml Apr 6, 2011 11:54:53 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:54:54 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:55:09 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 6, 2011 11:55:09 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 6, 2011 11:55:15 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0031_C040_74_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by HIFI: HIFI_MC_ASTR_A0031_C040_74_CUS_CAL.xml CONFIRMED!! 7(e) Run the duration script for the HIFI instrument Run the duration script delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> ls -ls total 6696 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 2010 cus-defdur.sh* 3328 -rw-r--r-- 1 hscphs2 herschel 3399680 Apr 13 14:37 CYCLE039_HIFI_FULL_2_20110413.tar 32 -rw-r--r-- 1 hscphs2 herschel 29771 Apr 13 14:26 default-durations.dat 1412 -rw-r--r-- 1 hscphs2 herschel 1438965 Apr 13 14:26 HIFI_MC_ASTR_A0032_C039_76_CUS_CAL.xml 1880 -rw-r--r-- 1 hscphs2 herschel 1919002 Apr 13 14:26 HIFI_MC_ASTR_A0032_C039_76_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1229 Apr 13 14:34 HIFI_MC_ASTR_A0032_C039_76.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 2010 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29771 Apr 28 11:22 Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> diff default-durations.dat Summary_durations.txt Perfect! No differences. 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY In the Comment field, refer to HIFI MC H76ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. 7(g) Import HIFI into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/HIFI> Apr 28, 2011 11:24:32 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 11:24:33 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:24:33 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 28, 2011 11:25:02 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H76ASTR_P66ASTR_S61ASTR_AO" Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:25:17 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 28, 2011 11:25:25 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H76ASTR_P66ASTR_S61ASTR_AO Apr 28, 2011 11:25:42 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the Old SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the PACS instrument Import into the new Mission Configuration Reset the OBDB/STPF properties 8(a) Set Instrument Model = SPIRE #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> Apr 28, 2011 11:27:35 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 11:27:36 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:27:36 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:27:37 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 28, 2011 11:28:01 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Apr 28, 2011 11:28:39 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 11:28:40 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:28:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:28:48 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Apr 28, 2011 11:29:08 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 11:29:09 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:29:14 AM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 61.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> cus -m "upload SPIRE MC_61ASTR mission config" -import SPIRE_MC_ASTR_pv87_C028_61_CUS.def -importcaltables SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml Apr 28, 2011 11:30:00 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 11:30:01 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:30:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 28, 2011 11:30:18 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:30:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:30:19 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 28, 2011 11:30:27 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by SPIRE: SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> ls -ls total 5120 2540 -rw-r--r-- 1 hscphs2 herschel 2590720 Nov 8 22:55 CYCLE028_SPIRE_FULL_1_0_20101108.tar 92 -rw-r--r-- 1 hscphs2 herschel 88159 Nov 8 22:01 SPIRE_AOR_C028_61_CAL.aor 60 -rw-r--r-- 1 hscphs2 herschel 56528 Nov 8 22:02 SPIRE_AOR_C028_61_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2023 Apr 28 11:31 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Nov 8 22:47 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5451 Nov 8 22:47 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Nov 9 15:38 SPIRE_harness_duration_summary_20101109_15h38m18s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Nov 23 09:34 SPIRE_harness_duration_summary_20101123_09h34m04s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Apr 28 11:36 SPIRE_harness_duration_summary_20110428_11h36m29s.log 276 -rw-r--r-- 1 hscphs2 herschel 276744 Nov 8 22:48 SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml 2100 -rw-r--r-- 1 hscphs2 herschel 2140168 Nov 8 22:48 SPIRE_MC_ASTR_pv87_C028_61_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8934 Nov 8 22:50 SPIRE_Readme_C028_61.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110428_11h36m29s.log Perfect. No differences! 8(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE SPIRE DELIVERY In the Comment field, refer to SPIRE MC S61ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. 8(g) Import SPIRE model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H76ASTR_P66ASTR_S61ASTR_AO/SPIRE> Apr 28, 2011 11:41:49 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 11:41:50 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 11:41:50 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:41:50 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:41:50 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:41:50 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:41:50 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:41:50 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:41:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:41:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:41:51 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 28, 2011 11:42:18 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H76ASTR_P66ASTR_S61ASTR_AO" Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 11:42:32 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 28, 2011 11:42:41 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H76ASTR_P66ASTR_S61ASTR_AO Apr 28, 2011 11:42:50 AM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. 9.Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophandler to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H76ASTR_P66ASTR_S61ASTR_AO [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Thu Apr 28 16:02:38 2011 from herl38.net4.lan HCSS Version: 6.1.0 PHS Version: 5.3.0 Enable gyro pointing... hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H73_P65_S62_GYRO> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> propHandler & [1] 15509 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Apr 28, 2011 4:25:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 28, 2011 4:25:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 28, 2011 4:25:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Running CDH.getObsProgrammes() Apr 28, 2011 4:25:04 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Apr 28, 2011 4:25:04 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 63 Apr 28, 2011 4:25:04 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Apr 28, 2011 4:25:04 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H76ASTR_P66ASTR_S61ASTR_AO" Apr 28, 2011 4:25:10 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 6386 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration : CONFIRMED!! 10. Export the HSpot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. CONFIRMED!! Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same as the Mission Confifguration: MC_H76ASTR_P66ASTR_S61ASTR_AO Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H76ASTR_P66ASTR_S61ASTR_AO Example of the last entry in the log: Apr 6, 2011 12:40:02 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H76ASTR_P66ASTR_S61ASTR_AO/HifiSScanProcLoadChopNoRefGen.prop Apr 6, 2011 12:40:02 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H76ASTR_P66ASTR_S61ASTR_AO/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H76ASTR_P66ASTR_S61ASTR_AO> ls *.prop > MC_H76ASTR_P66ASTR_S61ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H76ASTR_P66ASTR_S61ASTR_AO> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 14152 Apr 6 12:40 MC_H76ASTR_P66ASTR_S61ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H76ASTR_P66ASTR_S61ASTR_AO> cp MC_H76ASTR_P66ASTR_S61ASTR_AO.txt /home/hscphs2/icchsc/HSpot_files/ Now do a diff between this new txt file and the one generated with the last Mission configuration. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_H76ASTR_P64ASTR_S61ASTR_RP.txt MC_H76ASTR_P66ASTR_S61ASTR_AO.txt 70a71 > PacsCal_PacsLineSpecGyroGen.prop 76a78 > PacsCal_PacsPhotoGyroGen.prop If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. Two new PACS scripts Notify Eva 12. Final Jboss Activities [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Thu Apr 28 15:01:37 2011 from herl28.net4.lan herjbo02.esac.esa.int/home/hsc_phs> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 664 PHS: Astronomers instance 664 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the JBOSS : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion Create a directory which contains the name of the new MC: herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H76ASTR_P66ASTR_S61ASTR_AO Copy HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P48ASTR_S55ASTR_RP> scp *.prop hsc_phs@herjbo02.esac.esa.int:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H76ASTR_P66ASTR_S61ASTR_AO/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit phs-operations.props & Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #MARK TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_H76ASTR_P64ASTR_S61ASTR_RP_110413 hcss.phs.timeEstimatorVersion=MC_H76ASTR_P66ASTR_S61ASTR_AO_110428 #hcss.phs.timeEstimatorVersion=MC_H77_P64_S62_CAL-110427 #hcss.phs.timeEstimatorVersion=MC_H75_P64_S62_CAL-110414 #hcss.phs.timeEstimatorVersion=MC_H73_P65_S62_GYRO-110408 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H76ASTR_P64ASTR_S61ASTR_RP hcss.ccm.mission.config = MC_H76ASTR_P66ASTR_S61ASTR_AO #hcss.ccm.mission.config = MC_H77_P64_S62_CAL #hcss.ccm.mission.config = MC_H75_P64_S62_CAL #hcss.ccm.mission.config = MC_H73_P65_S62_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H76ASTR_P64ASTR_S61ASTR_RP hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H76ASTR_P66ASTR_S61ASTR_AO #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H77_P64_S62_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H75_P64_S62_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H73_P65_S62_GYRO Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 14265 herjbo02.esac.esa.int/home/hsc_phs/.hcss> ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /herschel/software/phs/jboss/jboss JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar ========================================================================= 16:42:42,336 INFO [Server] Starting JBoss (MX MicroKernel)... 16:42:42,337 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 16:42:42,337 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 16:42:42,337 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 16:42:42,338 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 16:42:42,338 INFO [Server] Patch URL: null 16:42:42,338 INFO [Server] Server Name: phs-operations 16:42:42,338 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 16:42:42,338 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 16:42:42,339 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 16:42:42,339 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 16:42:42,339 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 16:42:42,339 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 16:42:42,339 INFO [Server] Root Deployment Filename: jboss-service.xml 16:42:42,340 INFO [Server] Starting General Purpose Architecture (GPA)... 16:42:42,542 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 16:42:42,542 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 16:42:42,543 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 16:42:42,712 INFO [Server] Core system initialized 16:42:44,081 INFO [ServiceBindingManager] Initializing store 16:42:44,081 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 16:42:44,346 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.