HIFI Cycle 72 Calibration delivery HIFI Delivery note - 13th July 2012 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just delivered the calibration delivery for cycle 72, uploading the tar file containing the delivery of HIFI observations for cycle 72 onto the CVS server. 1. Delivery file, directory: a) OD tar file names: - CYCLE072_HIFI_FULL_1_20120713.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle072 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, Migo Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE072_HIFI_FULL_1_20120713.tar New MC - MC H103Cal 2. Software used for import [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri Jul 13 10:59:33 2012 from herl38.net4.lan HCSS Version: 8.3.0 PHS Version: 6.1.1 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_H103_P70_S68_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle72> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle72/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle072_HIFI_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL> 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_H103_P70_S68_CAL 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_H103_P70_S68_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H102ASTR_P70ASTR_S66ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/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_H103_P70_S68_CAL/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_H103_P70_S68_CAL/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_H103_P70_S68_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/SPIRE> ls CYCLE066_SPIRE_FULL_1_0_20120423.tar SPIRE_Duration.txt SPIRE_AOR_C066_68_CAL.aor SPIRE_harness_duration_summary_20120424_09h56m15s.log SPIRE_AOR_C066_68_ENG.aor SPIRE_MC_pv94_C066_68_CUS_CAL.xml SPIRE_AOR_C066_68_REDYandSTBY.aor SPIRE_MC_pv94_C066_68_CUS.def SPIRE_cus_scripts.txt SPIRE_Readme_C066_68.txt SPIRE_CUS_THCP.py 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_Cycle72/HIFI/HIFI_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle72/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_Cycle72/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle072/CYCLE072_HIFI_FULL_1_20120713.tar U develop/data/observingmodes/rp_cycles/cycle072/CYCLE072_HIFI_FULL_1_20120713.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle72/HIFI/HIFI_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle072/CYCLE072_HIFI_FULL_1_20120713.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle72/HIFI/HIFI_FULL_1> tar -xvf CYCLE072_HIFI_FULL_1_20120713.tar duration_cal.sh HIFI_AOR_C072_102.aor HIFI_AOR_C072_103.aor HIFI_DUR_C072_103.txt HIFI_MC_R103_FULL_103_0_CUS_CAL.xml HIFI_MC_R103_FULL_103_0_CUS.def HIFI_Readme_C072_103.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle72/HIFI/HIFI_FULL_1> ls CYCLE072_HIFI_FULL_1_20120713.tar HIFI_AOR_C072_102.aor HIFI_MC_R103_FULL_103_0_CUS_CAL.xml develop/ HIFI_AOR_C072_103.aor HIFI_MC_R103_FULL_103_0_CUS.def duration_cal.sh* HIFI_DUR_C072_103.txt HIFI_Readme_C072_103.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle72/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/HIFI> ls CYCLE072_HIFI_FULL_1_20120713.tar HIFI_AOR_C072_103.aor HIFI_MC_R103_FULL_103_0_CUS.def duration_cal.sh* HIFI_DUR_C072_103.txt HIFI_Readme_C072_103.txt HIFI_AOR_C072_102.aor HIFI_MC_R103_FULL_103_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_H103_P70_S68_CAL/PACS> Jul 13, 2012 3:09:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:09:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:09:23 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jul 13, 2012 3:10:05 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_H103_P70_S68_CAL/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_H103_P70_S68_CAL/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_H103_P70_S68_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/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 8.2.0 If you haven't done it before: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C068_70.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/PACS> ls -ls total 11660 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Jul 13 15:11 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Jul 13 15:11 2createOBSMODtable4RP.sh~* 5812 -rw-r--r-- 1 hscphs2 herschel 5939200 May 22 15:28 CYCLE068_PACS_FULL_1_20120522.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Jul 13 15:14 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 84 Jul 13 15:13 msgPacsEng_ChopperOpenLoop_FullRange.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Jul 13 15:13 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Jul 13 15:14 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Jul 13 15:14 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Jul 13 15:15 msgPacsRangeSpec.txt 168 -rw-r--r-- 1 hscphs2 herschel 165299 May 22 14:09 PACS_AOR_C068_70.aor 4 -rw-r--r-- 1 hscphs2 herschel 2393 May 22 15:23 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2393 Jul 13 15:15 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404629 May 22 14:01 PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS_CAL.xml 5232 -rw-r--r-- 1 hscphs2 herschel 5342121 May 22 14:01 PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8521 May 22 15:14 PACS_Readme_C068_70.txt 4 -rw-r--r-- 1 hscphs2 herschel 1480 Jul 13 15:13 tmp 4 -rw-r--r-- 1 hscphs2 herschel 532 Jul 13 15:13 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/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_H103_P70_S68_CAL/PACS> missetup -addconfig MC_H103_P70_S68_CAL Jul 13, 2012 3:19:36 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:19:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:19:37 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Jul 13, 2012 3:20:02 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H103_P70_S68_CAL" 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_H103_P70_S68_CAL/PACS> Jul 13, 2012 3:20:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:20:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:20:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:20:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:20:59 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jul 13, 2012 3:21:44 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S68_CAL" Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:21:51 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jul 13, 2012 3:22:15 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H103_P70_S68_CAL Jul 13, 2012 3:22:23 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_H103_P70_S68_CAL/HIFI> Jul 13, 2012 3:25:08 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:25:09 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:25:09 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jul 13, 2012 3:25:16 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_H103_P70_S68_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Jul 13, 2012 3:28:37 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:28:38 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:28:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:28:43 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Jul 13, 2012 3:29:04 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:29:05 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:29:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:29:09 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!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (H101Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/HIFI> cus -m "upload HIFI MC103Cal mission config" -import HIFI_MC_R103_FULL_103_0_CUS.def -importcaltables HIFI_MC_R103_FULL_103_0_CUS_CAL.xml Jul 13, 2012 3:32:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:32:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:32:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jul 13, 2012 3:32:51 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:32:51 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jul 13, 2012 3:32:55 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R103_FULL_103_0_CUS_CAL.xml" The final line should give the filename: HIFI_MC_R103_FULL_103_0_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_H103_P70_S68_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C072_103 next AOR file = HIFI_AOR_C072_103 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_Diplexer_calibration_short_COP -- mode HifiEng_Diplexer_Response_time_COP -- mode HifiEng_FPU_FT_IVC_COP -- mode HifiEng_HRS_FT_COP -- mode HifiEng_LO_FT_IVC_COP -- mode HifiEngSetIntoPrimary -- mode HifiEng_WBS_FT_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_Diplexer_calibration_short_COP with default parameters = 542 Total duration of HifiEng_Diplexer_Response_time_COP with default parameters = 85 Total duration of HifiEng_FPU_FT_IVC_COP with default parameters = 65 Total duration of HifiEng_HRS_FT_COP with default parameters = 1101 Total duration of HifiEng_LO_FT_IVC_COP with default parameters = 227 Total duration of HifiEngSetIntoPrimary with default parameters = 6 Total duration of HifiEng_WBS_FT_COP with default parameters = 1388 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/HIFI> ls -ls total 12048 6012 -rw-r--r-- 1 hscphs2 herschel 6144000 Jul 13 11:00 CYCLE072_HIFI_FULL_1_20120713.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Mar 8 2010 duration_cal.sh* 156 -rw-r--r-- 1 hscphs2 herschel 154195 Jul 12 19:27 HIFI_AOR_C072_102.aor 88 -rw-r--r-- 1 hscphs2 herschel 83566 Jul 12 19:35 HIFI_AOR_C072_103.aor 4 -rw-r--r-- 1 hscphs2 herschel 676 Jul 12 10:30 HIFI_DUR_C072_103.txt 2308 -rw-r--r-- 1 hscphs2 herschel 2351907 Jul 12 10:37 HIFI_MC_R103_FULL_103_0_CUS_CAL.xml 3464 -rw-r--r-- 1 hscphs2 herschel 3535373 Jul 12 10:37 HIFI_MC_R103_FULL_103_0_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 6844 Jul 13 10:55 HIFI_Readme_C072_103.txt 4 -rw-r--r-- 1 hscphs2 herschel 676 Jul 13 15:35 summary_HIFI_AOR_C072_103.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/HIFI> diff HIFI_DUR_C072_103.txt summary_HIFI_AOR_C072_103.log 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 H103CAL 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_H103_P70_S68_CAL/HIFI> Jul 13, 2012 3:41:26 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:41:27 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:41:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:41:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:41:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:41:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:41:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:41:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:41:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:41:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:41:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:41:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:41:28 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jul 13, 2012 3:41:54 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S68_CAL" Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:42:04 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jul 13, 2012 3:42:17 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H103_P70_S68_CAL Jul 13, 2012 3:43:48 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_H103_P70_S68_CAL/SPIRE> Jul 13, 2012 3:44:46 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:44:47 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:44:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:44:48 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jul 13, 2012 3:45:46 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! Have right CUS and CAL already. Skip... 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Jul 13, 2012 3:46:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:46:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:46:21 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jul 13, 2012 3:46:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:46:42 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:46:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:46:46 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 68.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/SPIRE> cus -m "upload SPIRE MC_68CAL mission config" -import SPIRE_MC_pv94_C066_68_CUS.def -importcaltables SPIRE_MC_pv94_C066_68_CUS_CAL.xml Jul 13, 2012 3:48:17 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:48:17 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:48:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jul 13, 2012 3:48:26 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:48:26 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jul 13, 2012 3:48:28 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv94_C066_68_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_pv94_C066_68_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/SPIRE> ls -ls total 5580 2768 -rw-r--r-- 1 hscphs2 herschel 2826240 Apr 23 18:40 CYCLE066_SPIRE_FULL_1_0_20120423.tar 248 -rw-r--r-- 1 hscphs2 herschel 247393 Apr 23 18:27 SPIRE_AOR_C066_68_CAL.aor 44 -rw-r--r-- 1 hscphs2 herschel 40296 Apr 23 18:28 SPIRE_AOR_C066_68_ENG.aor 72 -rw-r--r-- 1 hscphs2 herschel 65891 Apr 23 18:36 SPIRE_AOR_C066_68_REDYandSTBY.aor 4 -rw-r--r-- 1 hscphs2 herschel 2063 Jul 13 15:49 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Apr 23 18:28 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5533 Apr 23 18:34 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Apr 24 09:56 SPIRE_harness_duration_summary_20120424_09h56m15s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Jul 13 15:52 SPIRE_harness_duration_summary_20120713_15h52m59s.log 280 -rw-r--r-- 1 hscphs2 herschel 281472 Apr 23 18:28 SPIRE_MC_pv94_C066_68_CUS_CAL.xml 2124 -rw-r--r-- 1 hscphs2 herschel 2165953 Apr 23 18:28 SPIRE_MC_pv94_C066_68_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 10411 Apr 23 18:35 SPIRE_Readme_C066_68.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S68_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20120424_18h47m53s.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 S68Cal. 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_H103_P70_S68_CAL/SPIRE> Jul 13, 2012 3:58:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 3:58:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:58:01 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jul 13, 2012 3:58:16 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S68_CAL" Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 3:58:25 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jul 13, 2012 3:58:53 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H103_P70_S68_CAL Jul 13, 2012 3:58:57 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_H103_P70_S68_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri Jul 13 15:46:04 2012 from herl22.net4.lan HCSS Version: 8.3.0 PHS Version: 6.1.1 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/icchsc/HSpot_files/MC_H103_P70_S68_CAL> propHandler & [1] 19215 [1] + Running propHandler hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S68_CAL> Jul 13, 2012 4:09:04 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jul 13, 2012 4:09:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jul 13, 2012 4:09:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Running CDH.getObsProgrammes() Jul 13, 2012 4:09:05 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Jul 13, 2012 4:09:05 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 22 Jul 13, 2012 4:09:05 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Jul 13, 2012 4:09:05 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S68_CAL" Jul 13, 2012 4:09:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3578 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_H103_P70_S68_CAL Jul 13, 2012 4:10:37 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S68_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Jul 13, 2012 4:10:37 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S68_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S68_CAL> ls *.prop > & MC_H103_P70_S68_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S68_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18293 Jul 13 16:11 MC_H103_P70_S68_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S68_CAL> cp MC_H103_P70_S68_CAL.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_H101_P69_S68_CAL.txt MC_H103_P70_S68_CAL.txt If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. No 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: Fri Jul 13 15:43:22 2012 from herl28.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 718 PHS: Astronomers instance 705 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_H103_P70_S68_CAL 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_H103_P70_S68_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H103_P70_S68_CAL/ 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_H100ASTR_P70ASTR_S66ASTR_RP-120522 #hcss.phs.timeEstimatorVersion= MC_H102ASTR_P70ASTR_S66ASTR_RP-120713 #hcss.phs.timeEstimatorVersion=MC_H101_P69_S68_CAL-120424 hcss.phs.timeEstimatorVersion=MC_H103_P70_S68_CAL-120713 #MISSION CONFIG #hcss.ccm.mission.config = MC_H100ASTR_P70ASTR_S66ASTR_RP #hcss.ccm.mission.config = MC_H102ASTR_P70ASTR_S66ASTR_RP #hcss.ccm.mission.config = MC_H101_P69_S68_CAL hcss.ccm.mission.config = MC_H103_P70_S68_CAL #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H100ASTR_P70ASTR_S66ASTR_RP #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_H101_P69_S68_CAL hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H103_P70_S68_CAL Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 8951 herjbo02.esac.esa.int/home/hsc_phs/.hcss> ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /herschel/software/phs/jboss/jboss JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar ========================================================================= 16:23:38,701 INFO [Server] Starting JBoss (MX MicroKernel)... 16:23:38,702 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 16:23:38,702 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 16:23:38,702 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 16:23:38,702 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 16:23:38,703 INFO [Server] Patch URL: null 16:23:38,703 INFO [Server] Server Name: phs-operations 16:23:38,703 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 16:23:38,703 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 16:23:38,703 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 16:23:38,703 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 16:23:38,703 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 16:23:38,704 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 16:23:38,704 INFO [Server] Root Deployment Filename: jboss-service.xml 16:23:38,705 INFO [Server] Starting General Purpose Architecture (GPA)... 16:23:38,833 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 16:23:38,833 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 16:23:38,833 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 16:23:38,952 INFO [Server] Core system initialized 16:23:40,163 INFO [ServiceBindingManager] Initializing store 16:23:40,163 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 16:23:40,427 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.