HIFI Cycle 85 Calibration and MC delivery HIFI Delivery note - 18th January 2012 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just delivered the calibration delivery for cycle 85, uploading the tar file containing the delivery of HIFI observations for cycle 85 onto the CVS server. 1. Delivery file, directory: a) OD tar file names: - CYCLE085_HIFI_FULL_1_20130118.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle085 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) CYCLE085_HIFI_FULL_1_20130118.tar New MC - MC H109Cal 2. Software used for import [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri Jan 18 17:21:45 2013 from herl38.net4.lan HCSS Version: 9.2.0 PHS Version: 6.2.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal: PHS: Using BUILDNUM 534 & PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account 3. What is the Mission Configuration Name going to be?? MC_H109_P70_S68_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle085_HIFI_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_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_H109_P70_S69_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_H109_P70_S69_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H102ASTR_P70ASTR_S66ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_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_H109_P70_S69_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_H109_P70_S69_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_H109_P70_S69_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H103_P70_S69_CAL/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/SPIRE> ls CYCLE077_SPIRE_FULL_1_0_20120924.tar SPIRE_Duration.txt SPIRE_AOR_C077_69_CAL.aor SPIRE_harness_duration_summary_20120926_11h27m43s.log SPIRE_AOR_C077_69_ENG.aor SPIRE_harness_duration_summary_20121205_09h55m56s.log SPIRE_AOR_C077_69_REDYandSTBY.aor SPIRE_MC_pv95_C077_69_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_pv95_C077_69_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C077_69.txt cd 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_Cycle85/HIFI/HIFI_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/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_Cycle85/HIFI/HIFI_FULL_1> hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle085/CYCLE085_HIFI_FULL_1_20130118.tar U develop/data/observingmodes/rp_cycles/cycle085/CYCLE085_HIFI_FULL_1_20130118.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/HIFI/HIFI_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle085/CYCLE085_HIFI_FULL_1_20130118.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/HIFI/HIFI_FULL_1> ls CYCLE085_HIFI_FULL_1_20130118.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/HIFI/HIFI_FULL_1> tar -xvf CYCLE085_HIFI_FULL_1_20130118.tar duration_cal.sh HIFI_AOR_C085_102.aor HIFI_AOR_C085_109.aor HIFI_DUR_C085_109.txt HIFI_MC_R107_FULL_109_0_CUS_CAL.xml HIFI_MC_R107_FULL_109_0_CUS.def HIFI_Readme_C085_109.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/HIFI/HIFI_FULL_1> ls CYCLE085_HIFI_FULL_1_20130118.tar HIFI_AOR_C085_102.aor HIFI_MC_R107_FULL_109_0_CUS_CAL.xml develop/ HIFI_AOR_C085_109.aor HIFI_MC_R107_FULL_109_0_CUS.def duration_cal.sh* HIFI_DUR_C085_109.txt HIFI_Readme_C085_109.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle85/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/HIFI> ls CYCLE085_HIFI_FULL_1_20130118.tar HIFI_AOR_C085_109.aor HIFI_MC_R107_FULL_109_0_CUS.def duration_cal.sh* HIFI_DUR_C085_109.txt HIFI_Readme_C085_109.txt HIFI_AOR_C085_102.aor HIFI_MC_R107_FULL_109_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_H109_P70_S69_CAL/PACS> Jan 18, 2013 5:40:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 5:40:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:40:22 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jan 18, 2013 5:41:22 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_H109_P70_S69_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_H109_P70_S69_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_H109_P70_S69_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_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 9.2.0 If you haven't done it before: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C068_70.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/PACS> ls -ls total 11660 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Jan 18 17:42 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Jan 18 17:42 2createOBSMODtable4RP.sh~* 5812 -rw-r--r-- 1 hscphs2 herschel 5939200 May 22 2012 CYCLE068_PACS_FULL_1_20120522.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Jan 18 17:43 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 84 Jan 18 17:42 msgPacsEng_ChopperOpenLoop_FullRange.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Jan 18 17:42 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Jan 18 17:43 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Jan 18 17:43 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Jan 18 17:45 msgPacsRangeSpec.txt 168 -rw-r--r-- 1 hscphs2 herschel 165299 May 22 2012 PACS_AOR_C068_70.aor 4 -rw-r--r-- 1 hscphs2 herschel 2393 May 22 2012 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2393 Jan 18 17:45 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404629 May 22 2012 PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS_CAL.xml 5232 -rw-r--r-- 1 hscphs2 herschel 5342121 May 22 2012 PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8521 May 22 2012 PACS_Readme_C068_70.txt 4 -rw-r--r-- 1 hscphs2 herschel 1480 Jan 18 17:42 tmp 4 -rw-r--r-- 1 hscphs2 herschel 532 Jan 18 17:42 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_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_H109_P70_S69_CAL/PACS> missetup -addconfig MC_H109_P70_S69_CAL Jan 18, 2013 5:58:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 5:58:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:58:19 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Jan 18, 2013 5:58:27 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H109_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_H109_P70_S69_CAL/PACS> Jan 18, 2013 5:58:48 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 5:58:49 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:58:50 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jan 18, 2013 5:59:23 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H109_P70_S69_CAL" Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 5:59:32 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 18, 2013 5:59:46 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H109_P70_S69_CAL Jan 18, 2013 5:59:54 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_H109_P70_S69_CAL/HIFI> Jan 18, 2013 6:03:52 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:03:53 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:03:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:03:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:03:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:03:54 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jan 18, 2013 6:04:03 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_H109_P70_S69_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Jan 18, 2013 6:04:30 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:04:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:04:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:04:39 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Jan 18, 2013 6:05:04 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:05:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:05:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:05: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 (H107Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/HIFI> cus -m "upload HIFI MC109Cal mission config" -import HIFI_MC_R107_FULL_109_0_CUS.def -importcaltables HIFI_MC_R107_FULL_109_0_CUS_CAL.xml Jan 18, 2013 6:06:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:06:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:06:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:06:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:06:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:06:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:06:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:06:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:06:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:06:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:06:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:06:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:06:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:06:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 18, 2013 6:06:49 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:06:49 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 18, 2013 6:06:53 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R107_FULL_109_0_CUS_CAL.xml" The final line should give the filename: HIFI_MC_R107_FULL_109_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_H109_P70_S69_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C085_109 next AOR file = HIFI_AOR_C085_109 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_LO_FT_IVC_COP -- mode HifiEng_Parameter_Scan_COP -- mode HifiEngSetIntoPrimary -- mode HifiEngSwitchonLO -- mode HifiPointModeDBS -- mode HifiPointModeDBS -- mode HifiPointModeFastDBS -- mode HifiPointModeFSwitch -- mode HifiPointModeFSwitchNoRef -- mode HifiPointModeLoadChop -- mode HifiPointModeLoadChopNoRef -- mode HifiPointModePositionSwitch 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_LO_FT_IVC_COP with default parameters = 227 Total duration of HifiEng_Parameter_Scan_COP with default parameters = 1398 Total duration of HifiEngSetIntoPrimary with default parameters = 6 Total duration of HifiEngSwitchonLO with default parameters = 428 Total duration of HifiPointModeDBS with default parameters = 159 Total duration of HifiPointModeDBS with default parameters = 159 Total duration of HifiPointModeFastDBS with default parameters = 147 Total duration of HifiPointModeFSwitch with default parameters = 182 Total duration of HifiPointModeFSwitchNoRef with default parameters = 158 Total duration of HifiPointModeLoadChop with default parameters = 149 Total duration of HifiPointModeLoadChopNoRef with default parameters = 125 Total duration of HifiPointModePositionSwitch with default parameters = 141 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/HIFI> ls -ls total 12064 6024 -rw-r--r-- 1 hscphs2 herschel 6154240 Jan 18 17:13 CYCLE085_HIFI_FULL_1_20130118.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Mar 8 2010 duration_cal.sh* 148 -rw-r--r-- 1 hscphs2 herschel 146721 Jan 18 17:01 HIFI_AOR_C085_102.aor 64 -rw-r--r-- 1 hscphs2 herschel 58448 Jan 18 14:12 HIFI_AOR_C085_109.aor 4 -rw-r--r-- 1 hscphs2 herschel 1011 Jan 18 14:23 HIFI_DUR_C085_109.txt 2308 -rw-r--r-- 1 hscphs2 herschel 2352848 Jan 18 14:26 HIFI_MC_R107_FULL_109_0_CUS_CAL.xml 3500 -rw-r--r-- 1 hscphs2 herschel 3575096 Jan 18 14:26 HIFI_MC_R107_FULL_109_0_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5678 Jan 18 17:09 HIFI_Readme_C085_109.txt 4 -rw-r--r-- 1 hscphs2 herschel 1011 Jan 18 18:09 summary_HIFI_AOR_C085_109.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/HIFI> diff HIFI_DUR_C085_109.txt summary_HIFI_AOR_C085_109.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 H109CAL 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_H109_P70_S69_CAL/HIFI> Jan 18, 2013 6:10:51 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:10:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:10:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:10:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:10:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:10:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:10:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:10:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:10:53 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jan 18, 2013 6:11:40 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H109_P70_S69_CAL" Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:11:51 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 18, 2013 6:12:04 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H109_P70_S69_CAL Jan 18, 2013 6:12:10 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_H109_P70_S69_CAL/SPIRE> Jan 18, 2013 6:13:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:13:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:13:01 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jan 18, 2013 6:13:10 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Jan 18, 2013 6:14:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:14:18 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:14:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:14:30 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jan 18, 2013 6:14:54 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:14:54 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:14:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:14:58 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 69.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_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 Jan 18, 2013 6:15:46 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:15:47 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:15:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:15:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:15:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:15:55 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 18, 2013 6:15:55 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 18, 2013 6:15:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:15:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:15:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:15:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:15:56 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 18, 2013 6:15:58 PM 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_H109_P70_S69_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H109_P70_S69_CAL/SPIRE> ls -ls total 5424 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 Jan 18 18:16 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 8 -rw-rw-rw- 1 hscphs2 herschel 5604 Dec 5 09:55 SPIRE_harness_duration_summary_20121205_09h55m56s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5604 Jan 18 18:21 SPIRE_harness_duration_summary_20130118_18h21m13s.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_H109_P70_S69_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20130118_18h21m13s.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_H109_P70_S69_CAL/SPIRE> Jan 18, 2013 6:22:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:22:09 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:22:10 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jan 18, 2013 6:23:19 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H109_P70_S69_CAL" Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:23:29 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 18, 2013 6:23:38 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H109_P70_S69_CAL Jan 18, 2013 6:23:49 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H109_P70_S69_CAL" Jan 18, 2013 6:23:52 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_H109_P70_S69_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri Jan 18 17:21:54 2013 from herl38.net4.lan HCSS Version: 9.2.0 PHS Version: 6.2.0 Enable gyro pointing... hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H73_P65_S62_GYRO> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> propHandler & [1] 10528 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Jan 18, 2013 6:27:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 18, 2013 6:27:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Jan 18, 2013 6:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Running CDH.getObsProgrammes() Jan 18, 2013 6:27:30 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Jan 18, 2013 6:27:30 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 24 Jan 18, 2013 6:27:30 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Jan 18, 2013 6:27:30 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H109_P70_S69_CAL" Jan 18, 2013 6:27:34 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3856 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_H109_P70_S69_CAL Jan 18, 2013 6:29:14 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H109_P70_S69_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Jan 18, 2013 6:29:14 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H109_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_H109_P70_S69_CAL> ls *.prop > MC_H109_P70_S69_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H109_P70_S69_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18425 Jan 18 18:35 MC_H109_P70_S69_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H109_P70_S69_CAL> cp MC_H109_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_H109_P70_S69_CAL.txt MC_H107_P70_S69_CAL.txt 34,35d33 < HifiEngIntegrateZerosGen.prop < HifiEngLoDipScanDBSGen.prop If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. Two new HIFI scripts. Notify Eva (off sick long-term) 12. Final Jboss Activities Log into Jboss #2 [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Mon Jan 14 18:41:56 2013 from herl38.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 727 PHS: Astronomers instance 727 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the Operations Jboss : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H109_P70_S69_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_H109_P70_S69_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H109_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_H107_P70_S69_CAL-121219 #hcss.phs.timeEstimatorVersion=MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY-121219 hcss.phs.timeEstimatorVersion=MC_H109_P70_S69_CAL-130118 #MISSION CONFIG #hcss.ccm.mission.config = MC_H102ASTR_P70ASTR_S66ASTR_RP #hcss.ccm.mission.config = MC_H107_P70_S69_CAL #hcss.ccm.mission.config = MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY hcss.ccm.mission.config = MC_H109_P70_S69_CAL #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_H107_P70_S69_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H107ASTR_P70ASTR_S66ASTR_CONTINGENCY hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H109_P70_S69_CAL Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 18197 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 ========================================================================= 18:43:44,136 INFO [Server] Starting JBoss (MX MicroKernel)... 18:43:44,151 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 18:43:44,151 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 18:43:44,152 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 18:43:44,152 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 18:43:44,152 INFO [Server] Patch URL: null 18:43:44,152 INFO [Server] Server Name: phs-operations 18:43:44,152 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 18:43:44,154 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 18:43:44,154 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 18:43:44,154 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 18:43:44,154 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 18:43:44,154 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 18:43:44,154 INFO [Server] Root Deployment Filename: jboss-service.xml 18:43:44,157 INFO [Server] Starting General Purpose Architecture (GPA)... 18:43:44,862 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 18:43:44,862 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 18:43:44,862 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 18:43:45,154 INFO [Server] Core system initialized 18:43:47,230 INFO [ServiceBindingManager] Initializing store 18:43:47,230 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 18:43:47,599 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.