SPIRE Cycle 77 Calibration delivery 1. Delivery Note SPIRE Delivery note - 26th September 2012 Dear Colleagues of the HSC MPS Group, This e-mail is to notify you that I have just uploaded the SPIRE Routine Calibration CYCLE077 tar file onto the CVS server. The contents in the tar files are according to the HSC-ICC Interactions Document, and Larry's latest update. 1. Delivery file, directory & Mission Configuration issues (a) Cycle tar file name : CYCLE077_SPIRE_FULL_1_0_20120924.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle077 2. Mission Configurations (a) Does this delivery include a new Calibration Mission configuration(s)? Yes (b) Does this delivery include a new ASTR mission configurations(s)? No (c) If the answer to point (b) is YES, then have you copied the cCCB@sciops.esa.int in this delivery email? N/A 3. Operations Issues (a) Will any of these delivered observations generate a significant amount of Telecommands? Some individual observations generate up to 1000 TC. (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? As agreed in the planning meeting, our 'SpireEngDumpMemory' might go into a Real Time Science period of the DTCP depending on the mission planning. (c) ICC to add anything specific to this OD which HSC & MOC should be aware of. - The daily MTL script SpireEngCheckPM should be replaced by SpireEngCheckPMAndOBSTables. - The procedure run by MOC to perform daily PM checks remains unchanged. Please acknowledge the receipt of this delivery to us. Kind regards, Andreas and Sunil Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE077_SPIRE_FULL_1_0_20120924.tar New MC S69CAL 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Sep 25 11:51:00 2012 from herl22.net4.lan HCSS Version: 9.0.0 PHS Version: 6.1.1 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Mon Apr 9 02:42:19 2012 from ssh.esac.esa.int HCSS Version: 8.1.0 PHS Version: 6.1.1 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account 3. What is the Mission Configuration Name going to be?? MC_H103CAL_P69_S69_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/SPIRE> mkdir SPIRE_FULL_1 hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/HIFI> mkdir HIFI_FULL_2 This LOG file has been placed in the /logs directory and given the name Cycle077_SPIRE_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the HIFI & PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H103_P70_S69_CAL folder. Next remove in the PACS & HIFI subfolders all files which were created when you ran the PACS duration files e.g. tmp, msg, etc etc. PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_AOR_C059_69.aor 2createOBSMODtable4RP.sh~* PACS_Duration_PACS_compare.txt CYCLE059_PACS_FULL_1_20120113.tar PACS_Duration_PACS.txt msgPacsCal_PacsRangeSpec_PV.txt PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml msgPacsEng_Pacs_EDAC_to_DMC_HK.txt PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def msgPacsLineSpec.txt PACS_Readme_C059_69.txt msgPacsPhoto.txt tmp msgPacsRangeSpec.txt tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/PACS> rm msg* PACS_Duration_PACS.txt rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.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_S69_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt tmp 2createOBSMODtable4RP.sh~* PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml tmpobsmode CYCLE059_PACS_FULL_1_20120113.tar PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def PACS_AOR_C059_69.aor PACS_Readme_C059_69.txt HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H103ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_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 summary_HIFI_AOR_C072_103.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/HIFI> rm Summary_durations.txt rm: cannot lstat `Summary_durations.txt': No such file or directory hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_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 summary_HIFI_AOR_C072_103.log 6(a) Download & Untar the SPIRE delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/SPIRE/SPIRE_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/SPIRE/SPIRE_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_Cycle77/SPIRE/SPIRE_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle077/CYCLE077_SPIRE_FULL_1_0_20120924.tar U develop/data/observingmodes/rp_cycles/cycle077/CYCLE077_SPIRE_FULL_1_0_20120924.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/SPIRE/SPIRE_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle077/CYCLE077_SPIRE_FULL_1_0_20120924.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/SPIRE/SPIRE_FULL_1> ls CYCLE077_SPIRE_FULL_1_0_20120924.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/SPIRE/SPIRE_FULL_1> tar -xvf CYCLE077_SPIRE_FULL_1_0_20120924.tar SPIRE_MC_pv95_C077_69_CUS_CAL.xml SPIRE_MC_pv95_C077_69_CUS.def SPIRE_AOR_C077_69_CAL.aor SPIRE_AOR_C077_69_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C077_69.txt SPIRE_AOR_C077_69_REDYandSTBY.aor CYCLE077_SPIRE_FULL_1_0_20120924.tar SPIRE_AOR_C077_69_REDYandSTBY.aor SPIRE_MC_pv95_C077_69_CUS.def develop/ SPIRE_CUS_THCP.py SPIRE_Readme_C077_69.txt SPIRE_AOR_C077_69_CAL.aor SPIRE_Duration.txt SPIRE_AOR_C077_69_ENG.aor SPIRE_MC_pv95_C077_69_CUS_CAL.xml hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/SPIRE/SPIRE_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE> ls CYCLE077_SPIRE_FULL_1_0_20120405.tar SPIRE_AOR_C077_67_CAL_NewMC.aor SPIRE_MC_pv93_C077_67_CUS_CAL.xml SPIRE_AOR_C077_66_CAL.aor SPIRE_CUS_THCP.py SPIRE_MC_pv93_C077_67_CUS.def SPIRE_AOR_C077_66_ENG.aor SPIRE_Duration.txt SPIRE_Readme_C077.txt 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_S69_CAL/PACS> Sep 26, 2012 9:29:08 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 9:29:09 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 9:29:09 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 26, 2012 9:33:29 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Correct Cal and CUS loaded, so skip from here... 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H98ASTR_P68ASTR_S66ASTR_RP/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Jan 20, 2012 10:00:46 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:00:46 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:00:53 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H98ASTR_P68ASTR_S66ASTR_RP/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Jan 20, 2012 10:01:13 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:01:14 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:01:17 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 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props Import old Mission Configuration (Version 68.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/PACS> cus -m "upload PACS_MC P69ASTR mission config" -import PACS_MC_ASTR_OT2_2012-01-10A_C077_69_CUS.def -importcaltables PACS_MC_ASTR_OT2_2012-01-10A_C077_69_CUS_CAL.xml Jan 20, 2012 10:08:25 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:08:25 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:08:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 20, 2012 10:08:37 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 20, 2012 10:08:43 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT2_2012-01-10A_C077_69_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_2012-01-10A_C077_69_CUS_CAL.xml CONFIRMED!! Re-join here... 6(e) Run the duration script for the PACS instrument model: Point duration script to latest HCSS version... (9.0.0) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/PACS/PACS_FULL_1> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C059_69.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/PACS> ls -ls total 11604 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Sep 26 09:34 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Sep 26 09:34 2createOBSMODtable4RP.sh~* 5784 -rw-r--r-- 1 hscphs2 herschel 5908480 Jan 13 2012 CYCLE059_PACS_FULL_1_20120113.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Sep 26 09:35 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Sep 26 09:34 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Sep 26 09:36 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Sep 26 09:35 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Sep 26 09:36 msgPacsRangeSpec.txt 176 -rw-r--r-- 1 hscphs2 herschel 172240 Jan 13 2012 PACS_AOR_C059_69.aor 4 -rw-r--r-- 1 hscphs2 herschel 2687 Jan 13 2012 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2687 Sep 26 09:36 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404629 Jan 13 2012 PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml 5200 -rw-r--r-- 1 hscphs2 herschel 5311479 Jan 13 2012 PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8547 Jan 13 2012 PACS_Readme_C059_69.txt 4 -rw-r--r-- 1 hscphs2 herschel 1560 Sep 26 09:34 tmp 4 -rw-r--r-- 1 hscphs2 herschel 633 Sep 26 09:34 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle77/PACS/PACS_FULL_1> 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 P69ASTR 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_S69_CAL/PACS> missetup -addconfig MC_H103_P70_S69_CAL Sep 26, 2012 10:48:13 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 10:48:14 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 10:48:14 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Sep 26, 2012 10:48:20 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H103_P70_S69_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_S69_CAL/PACS> Sep 26, 2012 10:49:17 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 10:49:18 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 10:49:18 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 26, 2012 10:51:43 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S69_CAL" Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 10:51:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 10:51:52 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 26, 2012 10:51:58 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H103_P70_S69_CAL Sep 26, 2012 10:58:45 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(b) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/HIFI> Sep 26, 2012 11:04:37 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:04:37 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:04:38 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 26, 2012 11:06:59 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! Correct CUS & CAL loaded. Skip... 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Apr 9, 2012 12:04:28 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2012 12:04:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:04:34 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Apr 9, 2012 12:06:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2012 12:06:00 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2012 12:06:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:06:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:06:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:06:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:06:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:06:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:06:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:06:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:06:04 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_20111011030 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (H100ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/HIFI> cus -m "upload HIFI MC H100ASTR mission config" -import HIFI_MC_ASTR_A0055_C062_100_CUS.def -importcaltables HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml Apr 9, 2012 12:07:39 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2012 12:07:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:47 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 9, 2012 12:07:47 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 9, 2012 12:07:50 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by HIFI: HIFI_MC_ASTR_A0055_C062_100_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_H103_P70_S69_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_S69_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 0 -rw-r--r-- 1 hscphs2 herschel 0 Sep 26 11:08 Summary_durations.txt 4 -rw-r--r-- 1 hscphs2 herschel 676 Sep 26 11:10 summary_HIFI_AOR_C072_103.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/HIFI> diff HIFI_DUR_C072_103.txt summary_HIFI_AOR_C072_103.log Perfect! 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 H100ASTR as CAL 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_H103_P70_S69_CAL/HIFI> Sep 26, 2012 11:13:03 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:13:04 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:13:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:13:05 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 26, 2012 11:14:50 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S69_CAL" Sep 26, 2012 11:14:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:14:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:14:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:14:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:14:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:14:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:15:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:15:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:15:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:15:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:15:00 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 26, 2012 11:17:46 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H103_P70_S69_CAL Sep 26, 2012 11:17:51 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the new SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the PACS instrument Import into the new Mission Configuration 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_S69_CAL/SPIRE> Sep 26, 2012 11:18:53 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:18:53 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:18:54 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 26, 2012 11:19:19 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Sep 26, 2012 11:19:41 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:19:42 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:19:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:19:47 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Sep 26, 2012 11:20:48 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:20:49 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:20:49 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:20:52 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_20111011030 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import new SPIRE Mission Configuration (Version 69.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE> cus -m "upload SPIRE MC_69CAL mission config" -import SPIRE_MC_pv95_C077_69_CUS.def -importcaltables SPIRE_MC_pv95_C077_69_CUS_CAL.xml Sep 26, 2012 11:22:51 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:22:51 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:22:52 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 26, 2012 11:22:59 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:22:59 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 26, 2012 11:23:01 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv95_C077_69_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_pv95_C077_69_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_S69_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE> ls -ls total 5408 2688 -rw-r--r-- 1 hscphs2 herschel 2744320 Sep 24 17:14 CYCLE077_SPIRE_FULL_1_0_20120924.tar 188 -rw-r--r-- 1 hscphs2 herschel 185658 Sep 24 16:26 SPIRE_AOR_C077_69_CAL.aor 12 -rw-r--r-- 1 hscphs2 herschel 9480 Sep 24 16:27 SPIRE_AOR_C077_69_ENG.aor 76 -rw-r--r-- 1 hscphs2 herschel 70537 Sep 24 16:56 SPIRE_AOR_C077_69_REDYandSTBY.aor 4 -rw-r--r-- 1 hscphs2 herschel 2091 Sep 26 11:24 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Sep 24 16:50 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5604 Sep 24 16:50 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5604 Sep 26 11:27 SPIRE_harness_duration_summary_20120926_11h27m43s.log 280 -rw-r--r-- 1 hscphs2 herschel 281472 Sep 24 16:50 SPIRE_MC_pv95_C077_69_CUS_CAL.xml 2128 -rw-r--r-- 1 hscphs2 herschel 2167627 Sep 24 16:50 SPIRE_MC_pv95_C077_69_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 10857 Sep 24 16:51 SPIRE_Readme_C077_69.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20120926_11h27m43s.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 S69CAL 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_S69_CAL/SPIRE> Sep 26, 2012 11:30:47 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:30:48 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:30:48 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 26, 2012 11:31:27 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S69_CAL" Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:31:34 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 26, 2012 11:31:40 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H103_P70_S69_CAL Sep 26, 2012 11:31:43 AM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. 9.Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophandler to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H103_P70_S69_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Wed Sep 26 10:47:07 2012 from herl33.net4.lan HCSS Version: 9.0.0 PHS Version: 6.1.1 hscphs2@heropl02/home/hscphs2> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> propHandler & [1] 20309 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Sep 26, 2012 11:44:00 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Sep 26, 2012 11:44:00 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Sep 26, 2012 11:44:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Running CDH.getObsProgrammes() Sep 26, 2012 11:44:01 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Sep 26, 2012 11:44:01 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 36 Sep 26, 2012 11:44:01 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Sep 26, 2012 11:44:01 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H103_P70_S69_CAL" Sep 26, 2012 11:44:04 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3267 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration : CONFIRMED!! 10. Export the HSpot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. CONFIRMED!! Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same as the Mission Confifguration: MC_H103_P70_S69_CAL Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H103_P70_S69_CAL Example of the last entry in the log: Sep 26, 2012 11:46:07 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S69_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Sep 26, 2012 11:46:07 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S69_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_S69_CAL> ls *.prop > MC_H103_P70_S69_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S69_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18329 Sep 26 11:54 MC_H103_P70_S69_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H103_P70_S69_CAL> cp MC_H103_P70_S69_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_H103_P70_S68_CAL.txt MC_H103_P70_S69_CAL.txt 442a443 > SpireEngCheckPMAndOBSTablesGen.prop If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. One new SPIRE script Notify Eva 12. Final Jboss Activities [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Tue Sep 25 16:01:02 2012 from herl28.net4.lan herjbo02.esac.esa.int/home/hsc_phs> 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 JBOSS : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H103_P70_S69_CAL Copy HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H88ASTR_P67ASTR_S63ASTR_RP> scp *.prop hsc_phs@herjbo02.esac.esa.int:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H103_P70_S69_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_H102ASTR_P70ASTR_S66ASTR_RP-120713 hcss.phs.timeEstimatorVersion=MC_H103_P70_S69_CAL-120926 #hcss.phs.timeEstimatorVersion=MC_H103ASTR_P70ASTR_S66ASTR_CONTINGENCY-120723 #MISSION CONFIG #hcss.ccm.mission.config = MC_H102ASTR_P70ASTR_S66ASTR_RP hcss.ccm.mission.config = MC_H103_P70_S69_CAL #hcss.ccm.mission.config = MC_H103ASTR_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_H103_P70_S69_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H103ASTR_P70ASTR_S66ASTR_CONTINGENCY herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 1952 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 ========================================================================= 12:09:21,113 INFO [Server] Starting JBoss (MX MicroKernel)... 12:09:21,114 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 12:09:21,114 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 12:09:21,114 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 12:09:21,114 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 12:09:21,115 INFO [Server] Patch URL: null 12:09:21,115 INFO [Server] Server Name: phs-operations 12:09:21,115 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 12:09:21,115 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 12:09:21,115 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 12:09:21,115 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 12:09:21,115 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 12:09:21,116 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 12:09:21,116 INFO [Server] Root Deployment Filename: jboss-service.xml 12:09:21,117 INFO [Server] Starting General Purpose Architecture (GPA)... 12:09:21,294 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 12:09:21,295 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 12:09:21,295 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 12:09:21,447 INFO [Server] Core system initialized 12:09:22,765 INFO [ServiceBindingManager] Initializing store 12:09:22,765 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 12:09:23,033 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.