HIFI Cycle 81 Calibration delivery, Contingency MC HIFI Delivery note - 21st November 2012 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just delivered the calibration delivery for cycle 83, uploading the tar file containing the delivery of HIFI observations for cycle 83 onto the CVS server. 1. Delivery file, directory: a) OD tar file names: - CYCLE083_HIFI_FULL_1_20121218.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle083 2. Mission Configurations: a) Does this delivery include a new Calibration Mission configuration? Yes b) Does this delivery include a new Astro Mission configuration? No 3. Operations Issues 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? Not a requirement. c) ICC to add anything specific to this OD which HSC & MOC should be aware of: Instructions are in the Readme file. This Mission Configuration needs OBSW 6.5.3. Please acknowledge receipt of the e-mail and the delivery. Best regards, Ian Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE083_HIFI_FULL_1_20121121.tar New MC - MC H107Cal 2. Software used for import [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Thu Nov 22 12:11:28 2012 from herl22.net4.lan HCSS Version: 9.1.0 PHS Version: 6.2.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal: PHS: Using BUILDNUM 534 & PHS: Using JBOSS_HOME /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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY Skip this... 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle083_HIFI_FULL_1.log And re-join here... hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY folder. Next remove in the subfolders all files which were created when you ran the HIFI, SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H102ASTR_P70ASTR_S66ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> ls 2createOBSMODtable4RP.sh* PACS_AOR_C068_70.aor 2createOBSMODtable4RP.sh~* PACS_Duration_PACS_compare.txt CYCLE068_PACS_FULL_1_20120522.tar PACS_Duration_PACS.txt msgPacsCal_PacsRangeSpec_PV.txt PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS_CAL.xml msgPacsEng_ChopperOpenLoop_FullRange.txt PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS.def msgPacsEng_Pacs_EDAC_to_DMC_HK.txt PACS_Readme_C068_70.txt msgPacsLineSpec.txt tmp msgPacsPhoto.txt tmpobsmode msgPacsRangeSpec.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> rm tmp* msg* PACS_Duration_PACS.txt rm: remove regular file `tmp'? y rm: remove regular file `tmpobsmode'? y rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.txt'? y rm: remove regular file `msgPacsEng_ChopperOpenLoop_FullRange.txt'? y rm: remove regular file `msgPacsEng_Pacs_EDAC_to_DMC_HK.txt'? y rm: remove regular file `msgPacsLineSpec.txt'? y rm: remove regular file `msgPacsPhoto.txt'? y rm: remove regular file `msgPacsRangeSpec.txt'? y rm: remove regular file `PACS_Duration_PACS.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt 2createOBSMODtable4RP.sh~* PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS_CAL.xml CYCLE068_PACS_FULL_1_20120522.tar PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS.def PACS_AOR_C068_70.aor PACS_Readme_C068_70.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H103ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> ls CYCLE059_SPIRE_FULL_1_0_20120116.tar SPIRE_harness_duration_summary_20120120_10h57m25s.log SPIRE_AOR_C059_66_CAL.aor SPIRE_harness_duration_summary_20120723_17h58m37s.log SPIRE_AOR_C059_66_ENG.aor SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv92_C059_66_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C059_66.txt SPIRE_Duration.txt Skip this bit... 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI/HIFI_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI/HIFI_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_Cycle83/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle083/CYCLE083_HIFI_FULL_1_20121121.tar U develop/data/observingmodes/rp_cycles/cycle083/CYCLE083_HIFI_FULL_1_20121121.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI/HIFI_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle083/CYCLE083_HIFI_FULL_1_20121121.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI/HIFI_FULL_1> ls CYCLE083_HIFI_FULL_1_20121121.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI/HIFI_FULL_1> tar -xvf CYCLE083_HIFI_FULL_1_20121121.tar duration_cal.sh HIFI_AOR_C083_102.aor HIFI_AOR_C083_107.aor HIFI_DUR_C083_107.txt HIFI_MC_R104_FULL_107_0_CUS_CAL.xml HIFI_MC_R104_FULL_107_0_CUS.def HIFI_Readme_C083_107.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI/HIFI_FULL_1> ls CYCLE083_HIFI_FULL_1_20121121.tar HIFI_AOR_C083_102.aor HIFI_MC_R104_FULL_107_0_CUS_CAL.xml develop/ HIFI_AOR_C083_107.aor HIFI_MC_R104_FULL_107_0_CUS.def duration_cal.sh* HIFI_DUR_C083_107.txt HIFI_Readme_C083_107.txt And re-join here... hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle83/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> ls CYCLE083_HIFI_FULL_1_20121218.tar HIFI_AOR_C083_107.aor HIFI_MC_R105_FULL_107_0_CUS.def duration_cal.sh* HIFI_DUR_C083_107.txt HIFI_Readme_C083_107.txt HIFI_AOR_C083_102.aor HIFI_MC_R105_FULL_107_0_CUS_CAL.xml 6(b) To import the old 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> Dec 19, 2012 4:30:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:30:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:31:00 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Dec 19, 2012 4:31:41 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT PACS IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! Skip this as we have the correct CUS and CAL 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Dec 19, 2011 2:52:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 2:52:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:52:29 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Dec 19, 2011 2:58:27 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 2:58:28 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:58:31 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_MOC13_201103161700 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (Version 70.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cus -m "upload PACS_MC_68ASTR mission configuration as CAL" -import PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS.def -importcaltables PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS_CAL.xml Dec 19, 2011 3:00:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 3:00:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:48 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Dec 19, 2011 3:00:48 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Dec 19, 2011 3:00:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Dec 19, 2011 3:00:54 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT2_2011-11-25A_C055_68_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-11-25A_C055_68_CUS_CAL.xml CONFIRMED!! Re-join here... 6(e) Run the duration script for the PACS instrument model: Open duration script (2createOBSMODtable4RP.sh) and point it to HCSS 9.2.0 If you haven't done it before: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C068_70.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> ls -ls total 11660 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Dec 19 16:32 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Dec 19 16:32 2createOBSMODtable4RP.sh~* 5812 -rw-r--r-- 1 hscphs2 herschel 5939200 May 22 2012 CYCLE068_PACS_FULL_1_20120522.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Dec 19 16:34 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 84 Dec 19 16:33 msgPacsEng_ChopperOpenLoop_FullRange.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Dec 19 16:32 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Dec 19 16:34 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Dec 19 16:34 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Dec 19 16:35 msgPacsRangeSpec.txt 168 -rw-r--r-- 1 hscphs2 herschel 165299 May 22 2012 PACS_AOR_C068_70.aor 4 -rw-r--r-- 1 hscphs2 herschel 2393 May 22 2012 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2393 Dec 19 16:35 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404629 May 22 2012 PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS_CAL.xml 5232 -rw-r--r-- 1 hscphs2 herschel 5342121 May 22 2012 PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8521 May 22 2012 PACS_Readme_C068_70.txt 4 -rw-r--r-- 1 hscphs2 herschel 1480 Dec 19 16:32 tmp 4 -rw-r--r-- 1 hscphs2 herschel 532 Dec 19 16:32 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! Skip from here... 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 P70ASTR as CAL TAKE NOTE : It is very important that you commit the delivery as defined above. Re-join here... Now create the MC in the database hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> missetup -addconfig MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY Dec 19, 2012 4:37:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:37:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:37:08 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Dec 19, 2012 4:37:09 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY" 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> Dec 19, 2012 4:37:33 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:37:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:37:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Dec 19, 2012 4:38:03 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY" Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:38:21 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Dec 19, 2012 4:38:28 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY Dec 19, 2012 4:38:32 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the new 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(a) 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> Dec 19, 2012 4:45:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:45:07 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:45:07 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Dec 19, 2012 4:45:54 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!! Skip from here... 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Nov 22, 2012 10:13:25 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Nov 22, 2012 10:13:26 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:13:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:13:34 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Nov 22, 2012 10:14:09 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Nov 22, 2012 10:14:10 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:14:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:14: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_MOC13_201107041500 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (H107Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> cus -m "upload HIFI MC107Cal mission config" -import HIFI_MC_R104_FULL_107_0_CUS.def -importcaltables HIFI_MC_R104_FULL_107_0_CUS_CAL.xml Nov 22, 2012 10:17:58 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Nov 22, 2012 10:17:59 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:17:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Nov 22, 2012 10:18:10 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:18:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Nov 22, 2012 10:18:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:18:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Nov 22, 2012 10:18:11 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Nov 22, 2012 10:18:15 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R104_FULL_107_0_CUS_CAL.xml" The final line should give the filename: HIFI_MC_R104_FULL_107_0_CUS_CAL.xml CONFIRMED!! Re-join here... 7(e) Run the duration script for the HIFI instrument Run the duration script delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> ./duration_cal.sh HIFI_AOR_C083_107 next AOR file = HIFI_AOR_C083_107 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_Dipscan_CrossTalk_COP Total duration of HifiEng_Chopper_FT2_COP with default parameters = 114 Total duration of HifiEng_Chopper_Response_time_COP with default parameters = 44 Total duration of HifiEng_Chopper_Response_time_COP with default parameters = 44 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> ls -ls total 12168 6072 -rw-r--r-- 1 hscphs2 herschel 6205440 Dec 18 19:10 CYCLE083_HIFI_FULL_1_20121218.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Mar 8 2010 duration_cal.sh* 224 -rw-r--r-- 1 hscphs2 herschel 222663 Dec 18 17:56 HIFI_AOR_C083_102.aor 76 -rw-r--r-- 1 hscphs2 herschel 70780 Dec 18 17:59 HIFI_AOR_C083_107.aor 4 -rw-r--r-- 1 hscphs2 herschel 238 Dec 18 18:19 HIFI_DUR_C083_107.txt 2308 -rw-r--r-- 1 hscphs2 herschel 2351916 Dec 18 18:33 HIFI_MC_R105_FULL_107_0_CUS_CAL.xml 3468 -rw-r--r-- 1 hscphs2 herschel 3541961 Dec 18 18:33 HIFI_MC_R105_FULL_107_0_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 4800 Dec 18 19:00 HIFI_Readme_C083_107.txt 4 -rw-r--r-- 1 hscphs2 herschel 238 Dec 19 16:46 summary_HIFI_AOR_C083_107.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> diff HIFI_DUR_C083_107.txt summary_HIFI_AOR_C083_107.log No differences. Skip from here... 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 H107CAL TAKE NOTE : It is very important that you commit the delivery as defined above. Re-join here... 7(g) Import HIFI into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> Dec 19, 2012 4:47:49 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:47:50 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:47:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:47:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:47:51 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Dec 19, 2012 4:48:06 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY" Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:48:17 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Dec 19, 2012 4:48:31 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY Dec 19, 2012 4:48:37 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 SPIRE instrument Import into the new Mission Configuration 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> Dec 19, 2012 4:49:39 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:49:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:49:40 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Dec 19, 2012 4:50:38 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Dec 19, 2012 4:51:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:51:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:51:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:51:12 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Dec 19, 2012 4:51:37 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:51:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:51:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:51: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_MOC13_201107041500 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 66.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cus -m "upload SPIRE MC_66ASTR mission config" -import SPIRE_MC_ASTR_pv92_C059_66_CUS.def -importcaltables SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml Dec 19, 2012 4:52:37 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 4:52:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Dec 19, 2012 4:52:46 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 4:52:46 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Dec 19, 2012 4:52:48 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv92_C059_66_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_pv92_C059_66_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> ls -ls total 5040 2500 -rw-r--r-- 1 hscphs2 herschel 2549760 Jan 16 2012 CYCLE059_SPIRE_FULL_1_0_20120116.tar 72 -rw-r--r-- 1 hscphs2 herschel 68755 Jan 16 2012 SPIRE_AOR_C059_66_CAL.aor 16 -rw-r--r-- 1 hscphs2 herschel 12651 Jan 16 2012 SPIRE_AOR_C059_66_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2063 Dec 19 16:54 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Jan 16 2012 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5533 Jan 16 2012 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Jan 20 2012 SPIRE_harness_duration_summary_20120120_10h57m25s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Jul 23 17:58 SPIRE_harness_duration_summary_20120723_17h58m37s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Dec 19 16:57 SPIRE_harness_duration_summary_20121219_16h57m55s.log 280 -rw-r--r-- 1 hscphs2 herschel 279962 Jan 16 2012 SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml 2124 -rw-r--r-- 1 hscphs2 herschel 2163872 Jan 16 2012 SPIRE_MC_ASTR_pv92_C059_66_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 7286 Jan 16 2012 SPIRE_Readme_C059_66.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20121219_16h57m55s.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 S66ASTR. 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> Dec 19, 2012 5:01:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 5:01:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 5:01:39 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Dec 19, 2012 5:05:21 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY" Dec 19, 2012 5:05:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 5:05:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 5:05:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 5:05:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 5:05:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 5:05:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 5:05:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 5:05:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 5:05:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 5:05:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 5:05:30 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Dec 19, 2012 5:06:08 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY Dec 19, 2012 5:06:15 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Wed Dec 19 16:19:19 2012 from herl38.net4.lan HCSS Version: 9.2.0 PHS Version: 6.2.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] 18129 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Dec 19, 2012 5:07:36 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2012 5:07:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2012 5:07:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 5:07:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Dec 19, 2012 5:07:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Running CDH.getObsProgrammes() Dec 19, 2012 5:07:37 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Dec 19, 2012 5:07:37 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 27 Dec 19, 2012 5:07:37 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Dec 19, 2012 5:07:37 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY" Dec 19, 2012 5:07:41 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3840 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: Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY Dec 19, 2012 5:09:59 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HifiEng_Fast_LCU_HK_COPGen.prop Dec 19, 2012 5:09:59 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> ls *.prop > & MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18293 Nov 22 15:23 MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> cp MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY.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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt MC_H105ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt 17d16 < HifiEng_Dipscan_CrossTalk_COPGen.prop If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. One new HIFI script. Notify Eva 12. Final Jboss Activities Log into Jboss #2 [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Wed Dec 19 14:41:56 2012 from herl38.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 727 PHS: Astronomers instance 727 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the Operations 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 herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY copied 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_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY/ 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!! #TIME ESTIMATOR VERSION #hcss.phs.timeEstimatorVersion= MC_H102ASTR_P70ASTR_S66ASTR_RP-120713 #hcss.phs.timeEstimatorVersion=MC_H103_P70_S69_CAL-120926 #hcss.phs.timeEstimatorVersion=MC_H107_P70_S69_CAL-121122 #hcss.phs.timeEstimatorVersion=MC_H103ASTR_P70ASTR_S66ASTR_CONTINGENCY-120723 hcss.phs.timeEstimatorVersion=MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY-121122 #MISSION CONFIG #hcss.ccm.mission.config = MC_H102ASTR_P70ASTR_S66ASTR_RP #hcss.ccm.mission.config = MC_H105_P70_S69_CAL #hcss.ccm.mission.config = MC_H107_P70_S69_CAL #hcss.ccm.mission.config = MC_H105ASTR_P70ASTR_S66ASTR_CONTINGENCY hcss.ccm.mission.config = MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY #DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H102ASTR_P70ASTR_S66ASTR_RP #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H105_P70_S69_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H107_P70_S69_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H105ASTR_P70ASTR_S66ASTR_CONTINGENCY hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 24496 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 ========================================================================= 17:28:39,776 INFO [Server] Starting JBoss (MX MicroKernel)... 17:28:39,777 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 17:28:39,779 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 17:28:39,779 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 17:28:39,779 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 17:28:39,780 INFO [Server] Patch URL: null 17:28:39,780 INFO [Server] Server Name: phs-operations 17:28:39,780 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 17:28:39,780 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 17:28:39,780 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 17:28:39,780 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 17:28:39,780 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 17:28:39,781 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 17:28:39,781 INFO [Server] Root Deployment Filename: jboss-service.xml 17:28:39,782 INFO [Server] Starting General Purpose Architecture (GPA)... 17:28:39,958 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 17:28:39,958 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 17:28:39,959 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 17:28:40,108 INFO [Server] Core system initialized 17:28:41,437 INFO [ServiceBindingManager] Initializing store 17:28:41,437 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 17:28:41,701 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.