PACS Cycle 43 routine calibration and OT2 ASTR MC delivery 1. Delivery Note PACS Delivery note - 7th June 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#43 tar file onto the CVS server. 1. Delivery file & directory (a) OD tar file name : CYCLE043_PACS_FULL_1_20110607.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle043, 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 two SSOs, one planet: Uranus one asteroid: 1 Ceres 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.65.) * RPPhotFlux 3.2.3A&B, PACS RP Cal Plan, section 6.3 on 1 Ceres calibration of flux non-linearity of photometer * RPPhotFlux 3.2.4A&B, PACS RP Cal Plan, section 6.3 on beta And, alpha Boo, Uranus flux calibration of photometer * RPPhotFlux 3.2.8A, PACS RA Cal Plan, section 6.4 on NGC 6543 photometer flat field * RPPhotFlux 6.3.1A, PACS RA Cal Plan, section 10.6 on Uranus Herschel/Planck cross calibration * RPPhotSpatial 3.1.4D, PACS RP Cal Plan, section 10.2 on 1 Ceres calibration of photometer PSF * RPSpecFlux 4.3.3ABFG, PACS RP Cal Plan, section 6.8 on alpha Boo, R Dor, Uranus monitoring of the spectrometer linearity and absolute flux calibration at key wavelengths * RPSpecFlux 4.3.4A, PACS RP Cal Plan, section 6.7 on HD 161796 monitoring of the absolute flux calibration and reproducibility of the spectrometer * RPSpecFlux 6.1.1A&B, PACS RP Cal Plan, section 10.10 on Uranus and 1 Ceres PACS Phot/Spec cross calibration * RPElecEDAC 8.1.1A, PACS RP Cal Plan, section 7.4 no pointing monitoring of the EDAC addresses of single memory failures Scheduling instructions per OD (from Readme file): PACS Engineering on OD 777 ========================== RPElecEDAC_811A_5476A_10_na_00014 This AOR must be scheduled immediately before the PACS-S orbit epilogue on OD 777. PACS PHOT (to be scheduled on any PACS PHOT OD) =============================================== RPPhotFlux_324A_cPS_5Jy_blu_betaAnd_0003 RPPhotFlux_324B_sPS_070_5Jy_blu_betaAnd_0003 RPPhotFlux_324B_sPS_110_5Jy_blu_betaAnd_0003 RPPhotFlux_324A_cPS_2Jy_grn_betaAnd_0003 RPPhotFlux_324B_sPS_070_2Jy_grn_betaAnd_0003 RPPhotFlux_324B_sPS_110_2Jy_grn_betaAnd_0003 RPPhotFlux_328A_nStdScan_FlatField_blu_NGC6543_0003 RPPhotFlux_328A_nStdScan_FlatField_grn_NGC6543_0003 These blocks shall be scheduled in the indicated sequence. PACS PHOT (to be scheduled on PACS PHOT/SPEC OD 777) ==================================================== RPPhotFlux_324A_cPS_20Jy_blu_alfBoo_0003 RPPhotFlux_324B_sPS_070_20Jy_blu_alfBoo_0003 RPPhotFlux_324B_sPS_110_20Jy_blu_alfBoo_0003 RPPhotFlux_324A_cPS_10Jy_grn_alfBoo_0003 RPPhotFlux_324B_sPS_070_10Jy_grn_alfBoo_0003 RPPhotFlux_324B_sPS_110_10Jy_grn_alfBoo_0003 This block shall be scheduled in the indicated sequence. The observations on alpha Boo 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/SPEC OD 782) ==================================================== RPPhotFlux_323A_cPS_251Jy_blu_c43_Ceres_03 RPPhotFlux_323B_sPS_070_251Jy_blu_c43_Ceres_03 RPPhotFlux_323B_sPS_110_251Jy_blu_c43_Ceres_03 RPPhotSpatial_314D_StdScan045_med_blue_Ceres_0002 RPPhotSpatial_314D_StdScan135_med_blue_Ceres_0002 RPPhotFlux_323A_cPS_144Jy_grn_c43_Ceres_03 RPPhotFlux_323B_sPS_070_144Jy_grn_c43_Ceres_03 RPPhotFlux_323B_sPS_110_144Jy_grn_c43_Ceres_03 RPPhotSpatial_314D_StdScan045_med_grn_Ceres_0002 RPPhotSpatial_314D_StdScan135_med_grn_Ceres_0002 This block shall be scheduled in the indicated sequence. The observations on Ceres 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/SPEC OD 789) ==================================================== RPPhotFlux_324A_cPS_lo1000Jy_blu_Uranus_0003 RPPhotFlux_631A_sPS_070_Planck_lo_blu_Uranus_0002 RPPhotFlux_631A_sPS_110_Planck_lo_blu_Uranus_0002 RPPhotFlux_324A_cPS_lo1000Jy_grn_Uranus_0003 RPPhotFlux_631A_sPS_070_Planck_lo_grn_Uranus_0002 RPPhotFlux_631A_sPS_110_Planck_lo_grn_Uranus_0002 This block shall be scheduled in the indicated sequence. The observations on Uranus 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 SPEC (to be scheduled on any PACS SPEC OD) =============================================== RPSpecFlux_433F_StdRange_B2B_Chop_RDor_0001 RPSpecFlux_433G_StdRange_B2B_UnChop_RDor_0001 RPSpecFlux_433G_StdRange_B2B_UnChop_RDorOff_0001 RPSpecFlux_433F_StdRange_B_A_Chop_RDor_0001 RPSpecFlux_433G_StdRange_B_A_UnChop_RDor_0001 RPSpecFlux_433G_StdRange_B_A_UnChop_RDorOff_0001 This block shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 777) ==================================================== RPSpecFlux_433A_StdRange_AbsFluxA_AlphaBoo_0004 RPSpecFlux_433A_StdRange_AbsFluxB_AlphaBoo_0004 RPSpecFlux_433B_StdRange_UnchopFluxB2A_AlpBoo_2 RPSpecFlux_433B_StdRange_UnchopFluxB2A_AlpBooOff_2 RPSpecFlux_433B_StdRange_UnchopFluxB2B_AlpBoo_2 RPSpecFlux_433B_StdRange_UnchopFluxB2B_AlpBooOff_2 RPSpecFlux_433B_StdRange_UnchopFluxB3A_AlpBoo_2 RPSpecFlux_433B_StdRange_UnchopFluxB3A_AlpBooOff_2 This block shall be scheduled in the indicated sequence. The observations done on alpha Boo 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 782) ==================================================== RPSpecFlux_611A_StdSED_sedb2a_Ceres_0003 RPSpecFlux_611A_StdSED_sedb2b_Ceres_0003 RPSpecFlux_611A_StdSED_sedb3a_Ceres_0003 This block shall be scheduled in the indicated sequence. The observations done on Ceres 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 SPEC OD 783) =============================================== RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0046 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0046 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0046 This block shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 789) ==================================================== RPSpecFlux_433A_StdRange_AbsFluxA_Uranus_0003 RPSpecFlux_433A_StdRange_AbsFluxB_Uranus_0003 RPSpecFlux_433B_StdRange_UnchopFluxB2A_Uranus_02 RPSpecFlux_433B_StdRange_UnchopFluxB2A_UranusOff_02 RPSpecFlux_433B_StdRange_UnchopFluxB2B_Uranus_02 RPSpecFlux_433B_StdRange_UnchopFluxB2B_UranusOff_02 RPSpecFlux_433B_StdRange_UnchopFluxB3A_Uranus_02 RPSpecFlux_433B_StdRange_UnchopFluxB3A_UranusOff_02 RPSpecFlux_611A_StdSED_sedb2a_Uranus_0002 RPSpecFlux_611B_StdSED_nochop_sedb2a_Uranus_01 RPSpecFlux_611B_StdSED_nochop_sedb2a_UranusOff_01 RPSpecFlux_611A_StdSED_sedb2b_Uranus_0002 RPSpecFlux_611B_StdSED_nochop_sedb2b_Uranus_01 RPSpecFlux_611B_StdSED_nochop_sedb2b_UranusOff_01 RPSpecFlux_611A_StdSED_sedb3a_Uranus_0002 RPSpecFlux_611B_StdSED_nochop_sedb3a_Uranus_01 RPSpecFlux_611B_StdSED_nochop_sedb3a_UranusOff_01 This block shall be scheduled in the indicated sequence. The observations done on Uranus 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. 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) CYCLE043_PACS_FULL_1_20110607.tar New MC - MC P67ASTR 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Jun 7 17:38:33 2011 from herl38.net4.lan HCSS Version: 7.0.0 PHS Version: 5.3.2 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_H80ASTR_P67ASTR_S63ASTR_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 SPIRE_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle043_PACS_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_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_H80ASTR_P67ASTR_S63ASTR_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. HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H80ASTR_P66ASTR_S63ASTR_AO/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0043_C042_80_CUS_CAL.xml importall.sh* CYCLE042_HIFI_FULL_2_20110603.tar HIFI_MC_ASTR_A0043_C042_80_CUS.def Summary_durations.txt default-durations.dat HIFI_MC_ASTR_A0043_C042_80.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> rm Summary_durations.txt rm: remove regular file `Summary_durations.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0043_C042_80_CUS_CAL.xml importall.sh* CYCLE042_HIFI_FULL_2_20110603.tar HIFI_MC_ASTR_A0043_C042_80_CUS.def default-durations.dat HIFI_MC_ASTR_A0043_C042_80.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H80ASTR_P66ASTR_S63ASTR_AO/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> ls All_SPIRE_MC_S63ASTR.aor SPIRE_harness_duration_summary_20110523_15h37m04s.log CYCLE042_SPIRE_FULL_1_0_20110523.tar SPIRE_harness_duration_summary_20110606_11h29m16s.log SPIRE_AOR_C042_63_CAL.aor SPIRE_MC_ASTR_pv89_C042_1_CAL.def SPIRE_AOR_C042_63_ENG.aor SPIRE_MC_ASTR_pv89_C042_1_CUS.def SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv89_C042_63_CUS_CAL.xml SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv89_C042_63_CUS.def SPIRE_Duration.txt SPIRE_Readme_C042_63.txt 6(a) Download & Untar the HIFI delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle43/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle43/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_Cycle43/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle043/CYCLE043_PACS_FULL_1_20110607.tar U develop/data/observingmodes/rp_cycles/cycle043/CYCLE043_PACS_FULL_1_20110607.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle43/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle043/CYCLE043_PACS_FULL_1_20110607.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle43/PACS/PACS_FULL_1> ls CYCLE043_PACS_FULL_1_20110607.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle43/PACS/PACS_FULL_1> tar -xvf CYCLE043_PACS_FULL_1_20110607.tar PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS.def PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS_CAL.xml PACS_AOR_C043_67.aor PACS_Duration_PACS_compare.txt PACS_Readme_C043_67.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle43/PACS/PACS_FULL_1> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt CYCLE043_PACS_FULL_1_20110607.tar PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS_CAL.xml develop/ PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS.def PACS_AOR_C043_67.aor PACS_Readme_C043_67.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle43/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C043_67.txt CYCLE043_PACS_FULL_1_20110607.tar PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS_CAL.xml PACS_AOR_C043_67.aor PACS_MC_ASTR_OT2_2011-06-07A_C043_67_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_H80ASTR_P67ASTR_S63ASTR_AO/PACS> Jun 7, 2011 6:08:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:08:44 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:08:44 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jun 7, 2011 6:08:52 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_H80ASTR_P67ASTR_S63ASTR_AO/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Jun 7, 2011 6:10:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:10:07 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:10:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:10:15 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Jun 7, 2011 6:10:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:10:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:10:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:10:41 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 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props Import new Mission Configuration (Version 67.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS> cus -m "upload PACS_MC P67ASTR mission config" -import PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS.def -importcaltables PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS_CAL.xml Jun 7, 2011 6:12:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:12:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:12:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jun 7, 2011 6:13:04 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:13:04 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jun 7, 2011 6:13:10 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT2_2011-06-07A_C043_67_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-06-07A_C043_67_CUS_CAL.xml CONFIRMED!! 6(e) Run the duration script for the PACS instrument model: Point duration script to latest HCSS version... (7.0.0) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C043_67.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/PACS> ls -ls total 11688 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Jun 7 18:14 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Jun 7 18:14 2createOBSMODtable4RP.sh~* 5824 -rw-r--r-- 1 hscphs2 herschel 5949440 Jun 7 15:31 CYCLE043_PACS_FULL_1_20110607.tar 4 -rw-r--r-- 1 hscphs2 herschel 77 Jun 7 18:15 msgPacsCal_PacsPhotoDACSlowScan.txt 4 -rw-r--r-- 1 hscphs2 herschel 74 Jun 7 18:17 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Jun 7 18:14 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Jun 7 18:16 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Jun 7 18:18 msgPacsRangeSpec.txt 208 -rw-r--r-- 1 hscphs2 herschel 206612 Jun 7 15:16 PACS_AOR_C043_67.aor 8 -rw-r--r-- 1 hscphs2 herschel 4245 Jun 7 15:27 PACS_Duration_PACS_compare.txt 8 -rw-r--r-- 1 hscphs2 herschel 4245 Jun 7 18:18 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404163 Jun 7 12:56 PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS_CAL.xml 5200 -rw-r--r-- 1 hscphs2 herschel 5311479 Jun 7 12:56 PACS_MC_ASTR_OT2_2011-06-07A_C043_67_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 11040 Jun 7 15:27 PACS_Readme_C043_67.txt 4 -rw-r--r-- 1 hscphs2 herschel 2099 Jun 7 18:14 tmp 4 -rw-r--r-- 1 hscphs2 herschel 917 Jun 7 18:14 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_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 P67ASTR 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_H80ASTR_P67ASTR_S63ASTR_AO/PACS> missetup -addconfig MC_H80ASTR_P67ASTR_S63ASTR_AO Jun 7, 2011 6:24:25 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:24:26 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:24:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:24:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:24:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:24:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:24:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:24:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:24:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:24:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:24:27 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Jun 7, 2011 6:24:33 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H80ASTR_P67ASTR_S63ASTR_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_H80ASTR_P67ASTR_S63ASTR_AO/PACS> Jun 7, 2011 6:24:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:24:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:24:51 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jun 7, 2011 6:25:06 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H80ASTR_P67ASTR_S63ASTR_AO" Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:25:22 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jun 7, 2011 6:25:29 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H80ASTR_P67ASTR_S63ASTR_AO Jun 7, 2011 6:25:37 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_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> Jun 7, 2011 6:26:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:26:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:26:35 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jun 7, 2011 6:26:45 PM 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_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Jun 7, 2011 6:27:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:27:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:27:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:27:26 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Jun 7, 2011 6:27:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:27:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:27:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:28:03 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!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (H80ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> cus -m "upload HIFI MC H80ASTR mission config" -import HIFI_MC_ASTR_A0043_C042_80_CUS.def -importcaltables HIFI_MC_ASTR_A0043_C042_80_CUS_CAL.xml Jun 7, 2011 6:29:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:29:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:29:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:30:13 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jun 7, 2011 6:30:13 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:30:14 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jun 7, 2011 6:30:19 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0043_C042_80_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_A0043_C042_80_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_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> ls -ls total 6716 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 2010 cus-defdur.sh* 3340 -rw-r--r-- 1 hscphs2 herschel 3409920 Jun 3 12:36 CYCLE042_HIFI_FULL_2_20110603.tar 32 -rw-r--r-- 1 hscphs2 herschel 29834 Jun 3 12:23 default-durations.dat 1416 -rw-r--r-- 1 hscphs2 herschel 1442838 Jun 3 12:23 HIFI_MC_ASTR_A0043_C042_80_CUS_CAL.xml 1884 -rw-r--r-- 1 hscphs2 herschel 1924342 Jun 3 12:23 HIFI_MC_ASTR_A0043_C042_80_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1631 Jun 3 12:32 HIFI_MC_ASTR_A0043_C042_80.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 2010 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29834 Jun 7 18:56 Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_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 H80ASTR 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_H80ASTR_P67ASTR_S63ASTR_AO/HIFI> Jun 7, 2011 6:57:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:57:43 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:57:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:57:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:57:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:57:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:57:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:57:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:57:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:57:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:57:44 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jun 7, 2011 6:58:03 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H80ASTR_P67ASTR_S63ASTR_AO" Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:58:19 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jun 7, 2011 6:58:27 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H80ASTR_P67ASTR_S63ASTR_AO Jun 7, 2011 6:58:48 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H80ASTR_P67ASTR_S63ASTR_AO" Jun 7, 2011 6:58:51 PM 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_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> Jun 7, 2011 6:59:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 6:59:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:59:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 6:59:40 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jun 7, 2011 6:59:46 PM 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_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Jun 7, 2011 7:00:19 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 7:00:20 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:00:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:00:28 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jun 7, 2011 7:00:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 7:00:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:00:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:01:01 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!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 63.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> cus -m "upload SPIRE MC_63ASTR mission config" -import SPIRE_MC_ASTR_pv89_C042_1_CUS.def -importcaltables SPIRE_MC_ASTR_pv89_C042_1_CAL.def Jun 7, 2011 7:01:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 7:01:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 7:01:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:01:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:01:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:01:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jun 7, 2011 7:01:52 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:01:52 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jun 7, 2011 7:01:56 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv89_C042_1_CAL.def" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by SPIRE: SPIRE_MC_ASTR_pv89_C042_1_CAL.def CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> ls -ls total 15236 7592 -rw-r--r-- 1 hscphs2 herschel 7756432 May 17 09:06 All_SPIRE_MC_S63ASTR.aor 2600 -rw-r--r-- 1 hscphs2 herschel 2652160 May 23 14:26 CYCLE042_SPIRE_FULL_1_0_20110523.tar 140 -rw-r--r-- 1 hscphs2 herschel 135192 May 23 13:27 SPIRE_AOR_C042_63_CAL.aor 52 -rw-r--r-- 1 hscphs2 herschel 48434 May 23 13:28 SPIRE_AOR_C042_63_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2063 Jun 7 19:02 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 May 23 13:57 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5534 May 23 14:04 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5534 May 23 15:37 SPIRE_harness_duration_summary_20110523_15h37m04s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5534 Jun 6 11:29 SPIRE_harness_duration_summary_20110606_11h29m16s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5534 Jun 7 19:07 SPIRE_harness_duration_summary_20110607_19h07m55s.log 280 -rw-r--r-- 1 hscphs2 herschel 278985 May 16 18:20 SPIRE_MC_ASTR_pv89_C042_1_CAL.def 2120 -rw-r--r-- 1 hscphs2 herschel 2159201 May 16 18:20 SPIRE_MC_ASTR_pv89_C042_1_CUS.def 280 -rw-r--r-- 1 hscphs2 herschel 278985 May 23 13:57 SPIRE_MC_ASTR_pv89_C042_63_CUS_CAL.xml 2120 -rw-r--r-- 1 hscphs2 herschel 2159201 May 23 13:57 SPIRE_MC_ASTR_pv89_C042_63_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8669 May 23 14:19 SPIRE_Readme_C042_63.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110607_19h07m55s.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 S63ASTR 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_H80ASTR_P67ASTR_S63ASTR_AO/SPIRE> Jun 7, 2011 7:09:25 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 7:09:26 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:09:27 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jun 7, 2011 7:09:43 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H80ASTR_P67ASTR_S63ASTR_AO" Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:09:55 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jun 7, 2011 7:13:22 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H80ASTR_P67ASTR_S63ASTR_AO Jun 7, 2011 7:13:28 PM 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_H80ASTR_P67ASTR_S63ASTR_AO [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Jun 7 18:46:10 2011 from herl36.net4.lan HCSS Version: 7.0.0 PHS Version: 5.3.2 hscphs2@heropl02/home/hscphs2> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> propHandler & [1] 25697 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Jun 7, 2011 7:16:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jun 7, 2011 7:16:11 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jun 7, 2011 7:16:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Running CDH.getObsProgrammes() Jun 7, 2011 7:16:12 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Jun 7, 2011 7:16:12 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 30 Jun 7, 2011 7:16:12 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Jun 7, 2011 7:16:12 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H80ASTR_P67ASTR_S63ASTR_AO" Jun 7, 2011 7:16:16 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3903 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_H80ASTR_P67ASTR_S63ASTR_AO Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H80ASTR_P67ASTR_S63ASTR_AO Example of the last entry in the log: Jun 7, 2011 7:19:10 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H80ASTR_P67ASTR_S63ASTR_AO/HifiSScanProcLoadChopNoRefGen.prop Jun 7, 2011 7:19:10 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H80ASTR_P67ASTR_S63ASTR_AO/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H80ASTR_P67ASTR_S63ASTR_AO> ls *.prop > MC_H80ASTR_P67ASTR_S63ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H80ASTR_P67ASTR_S63ASTR_AO> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 14263 Jun 7 19:19 MC_H80ASTR_P67ASTR_S63ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H80ASTR_P67ASTR_S63ASTR_AO> cp MC_H80ASTR_P67ASTR_S63ASTR_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_H80ASTR_P66ASTR_S63ASTR_AO.txt MC_H80ASTR_P67ASTR_S63ASTR_AO.txt If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. No new script Do not notify Eva & Jose 12. Final Jboss Activities [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Mon Jun 6 12:07:04 2011 from herl38.net4.lan herjbo02.esac.esa.int/home/hsc_phs> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 668 PHS: Astronomers instance 668 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_H80ASTR_P67ASTR_S63ASTR_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_H80ASTR_P67ASTR_S63ASTR_AO> scp *.prop hsc_phs@herjbo02.esac.esa.int:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H80ASTR_P67ASTR_S63ASTR_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_H78ASTR_P66ASTR_S63ASTR_AO_110517 #hcss.phs.timeEstimatorVersion=MC_H80ASTR_P66ASTR_S63ASTR_AO_110606 hcss.phs.timeEstimatorVersion=MC_H80ASTR_P67ASTR_S63ASTR_AO_110607 #hcss.phs.timeEstimatorVersion=MC_H79_P66_S63_CAL-110525 #hcss.phs.timeEstimatorVersion=MC_H73_P65_S62_GYRO-110408 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H78ASTR_P66ASTR_S63ASTR_AO #hcss.ccm.mission.config = MC_H80ASTR_P66ASTR_S63ASTR_AO hcss.ccm.mission.config = MC_H80ASTR_P67ASTR_S63ASTR_AO #hcss.ccm.mission.config = MC_H79_P66_S63_CAL #hcss.ccm.mission.config = MC_H73_P65_S62_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H78ASTR_P66ASTR_S63ASTR_AO #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H80ASTR_P66ASTR_S63ASTR_AO hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H80ASTR_P67ASTR_S63ASTR_AO #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H79_P66_S63_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] 27608 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 ========================================================================= 19:29:53,824 INFO [Server] Starting JBoss (MX MicroKernel)... 19:29:53,825 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 19:29:53,825 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 19:29:53,825 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 19:29:53,825 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 19:29:53,826 INFO [Server] Patch URL: null 19:29:53,826 INFO [Server] Server Name: phs-operations 19:29:53,826 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 19:29:53,826 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 19:29:53,826 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 19:29:53,826 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 19:29:53,827 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 19:29:53,827 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 19:29:53,827 INFO [Server] Root Deployment Filename: jboss-service.xml 19:29:53,828 INFO [Server] Starting General Purpose Architecture (GPA)... 19:29:54,075 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 19:29:54,075 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 19:29:54,075 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 19:29:54,502 INFO [Server] Core system initialized 19:29:55,937 INFO [ServiceBindingManager] Initializing store 19:29:55,937 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 19:29:56,201 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.