HIFI Cycle 87 CONTINGENCY MC 1. Delivery Note HIFI Delivery note - 20th February 2013 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just delivered the CONTINGENCY ASTR MC H113 calibration delivery for cycle 87, uploading the tar file containing the delivery of HIFI observations for cycle 87 onto the CVS server. This is the ASTR MC for the CONTINGENCY of the failure of the HIFI WBS COMB. 1. Delivery file, directory: a) OD tar file names: - CYCLE087_HIFI_FULL_2_20130219.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle087 2. Mission Configurations: a) Does this delivery include a new Calibration Mission configuration? No -- only CONTINGENCY b) Does this delivery include a new Astro Mission configuration? No -- only CONTINGENCY 3. Operations Issues a) Will any of these delivered observations generate a significant amount of Telecommands? No b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? Not a requirement. c) ICC to add anything specific to this OD which HSC & MOC should be aware of: Instructions are in the Readme file. This Mission Configuration needs OBSW 6.5.3. Please acknowledge receipt of the e-mail and the delivery. Best regards, Ian Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE087_HIFI_FULL_2_20130219.tar New MC - MC H113CONTINGENCY 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 Feb 19 08:27:42 2013 from herl38.net4.lan HCSS Version: 10.0.1 PHS Version: 6.3.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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle87> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI> mkdir HIFI_FULL_2 This LOG file has been placed in the /logs directory and given the name Cycle087_HIFI_FULL_2.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY folder. Next remove in the subfolders all files which were created when you ran the HIFI, SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H102ASTR_P70ASTR_S66ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> rm tmp* msg* PACS_Duration_PACS.txt rm: remove regular file `tmp'? y rm: remove regular file `tmpobsmode'? y rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.txt'? y rm: remove regular file `msgPacsEng_ChopperOpenLoop_FullRange.txt'? y rm: remove regular file `msgPacsEng_Pacs_EDAC_to_DMC_HK.txt'? y rm: remove regular file `msgPacsLineSpec.txt'? y rm: remove regular file `msgPacsPhoto.txt'? y rm: remove regular file `msgPacsRangeSpec.txt'? y rm: remove regular file `PACS_Duration_PACS.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt 2createOBSMODtable4RP.sh~* PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS_CAL.xml CYCLE068_PACS_FULL_1_20120522.tar PACS_MC_ASTR_OT2_2012-05-21A_C068_70_CUS.def PACS_AOR_C068_70.aor PACS_Readme_C068_70.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H103ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> ls CYCLE059_SPIRE_FULL_1_0_20120116.tar SPIRE_harness_duration_summary_20120120_10h57m25s.log SPIRE_AOR_C059_66_CAL.aor SPIRE_harness_duration_summary_20120723_17h58m37s.log SPIRE_AOR_C059_66_ENG.aor SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv92_C059_66_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C059_66.txt SPIRE_Duration.txt 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_Cycle87/HIFI/HIFI_FULL_2> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI/HIFI_FULL_2> 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_Cycle87/HIFI/HIFI_FULL_2> cvs co develop/data/observingmodes/rp_cycles/cycle087/CYCLE087_HIFI_FULL_2_20130219.tar U develop/data/observingmodes/rp_cycles/cycle087/CYCLE087_HIFI_FULL_2_20130219.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI/HIFI_FULL_2> cp develop/data/observingmodes/rp_cycles/cycle087/CYCLE087_HIFI_FULL_2_20130219.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI/HIFI_FULL_2> ls CYCLE087_HIFI_FULL_2_20130219.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI/HIFI_FULL_2> tar -xvf CYCLE087_HIFI_FULL_2_20130219.tar duration_cal.sh HIFI_AOR_C087_113.aor HIFI_DUR_C087_113.txt HIFI_MC_R109_FULL_113_0_CUS_CAL.xml HIFI_MC_R109_FULL_113_0_CUS.def HIFI_Readme_C087_113.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI/HIFI_FULL_2> ls CYCLE087_HIFI_FULL_2_20130219.tar HIFI_AOR_C087_113.aor HIFI_MC_R109_FULL_113_0_CUS.def develop/ HIFI_DUR_C087_113.txt HIFI_Readme_C087_113.txt duration_cal.sh* HIFI_MC_R109_FULL_113_0_CUS_CAL.xml hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> cp /home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI/HIFI_FULL_2/* . cp: omitting directory `/home/hscphs2/icchsc/delivery/Calibration_Cycle87/HIFI/HIFI_FULL_2/develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> ls CYCLE087_HIFI_FULL_2_20130118.tar HIFI_AOR_C087_109.aor HIFI_MC_R107_FULL_109_0_CUS.def duration_cal.sh* HIFI_DUR_C087_109.txt HIFI_Readme_C087_109.txt HIFI_AOR_C087_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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> Feb 20, 2013 3:19:32 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:19:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:19:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:19:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 20, 2013 3:20:43 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Dec 19, 2011 2:52:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 2:52:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:52:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:52:29 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Dec 19, 2011 2:58:27 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 2:58:28 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:58:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 2:58:31 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC13_201103161700 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (Version 70.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> cus -m "upload PACS_MC_68ASTR mission configuration as CAL" -import PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS.def -importcaltables PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS_CAL.xml Dec 19, 2011 3:00:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 3:00:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:48 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Dec 19, 2011 3:00:48 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Dec 19, 2011 3:00:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 3:00:49 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Dec 19, 2011 3:00:54 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by PACS: PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS_CAL.xml CONFIRMED!! Re-join here... 6(e) Run the duration script for the PACS instrument model: Open duration script (2createOBSMODtable4RP.sh) and point it to HCSS 10.0.1 If you haven't done it before: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C068_70.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> ls -ls total 11660 4 -rwxr-xr-- 1 hscphs2 herschel 1539 Feb 20 15:22 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Feb 20 15:22 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 Feb 20 15:26 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 84 Feb 20 15:24 msgPacsEng_ChopperOpenLoop_FullRange.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Feb 20 15:24 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Feb 20 15:26 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Feb 20 15:25 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Feb 20 15:27 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 Feb 20 15:27 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 Feb 20 15:24 tmp 4 -rw-r--r-- 1 hscphs2 herschel 532 Feb 20 15:24 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! Skip from here... 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS MC P70ASTR as CAL TAKE NOTE : It is very important that you commit the delivery as defined above. Re-join here... Now create the MC in the database hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> missetup -addconfig MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY Feb 20, 2013 3:30:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:30:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:30:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:30:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:30:17 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Feb 20, 2013 3:30:19 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Add the commited CUS to the new MC hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/PACS> Feb 20, 2013 3:33:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:33:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:33:36 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 20, 2013 3:34:11 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY" Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:34:20 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 20, 2013 3:34:28 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY Feb 20, 2013 3:34:33 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> Feb 20, 2013 3:38:58 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:38:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:38:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:38:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:38:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:38:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:39:00 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Feb 20, 2013 3:39:45 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Feb 20, 2013 3:45:25 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:45:25 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:45:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:45:34 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Feb 20, 2013 3:49:16 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:49:17 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:49:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:49:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:49:22 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> cus -m "upload HIFI MC113Cal mission config" -import HIFI_MC_R109_FULL_113_0_CUS.def -importcaltables HIFI_MC_R109_FULL_113_0_CUS_CAL.xml Feb 20, 2013 3:52:32 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:52:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:52:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Feb 20, 2013 3:52:44 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:52:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:52:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:52:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:52:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:52:45 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 20, 2013 3:52:48 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R109_FULL_113_0_CUS_CAL.xml" The final line should give the filename: HIFI_MC_R109_FULL_113_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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> ./duration_cal.sh HIFI_AOR_C087_113 next AOR file = HIFI_AOR_C087_113 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_Dipscan_calibration_COP -- mode HifiEng_Dipscan_CrossTalk_COP -- mode HifiEng_Dipscan_CrossTalk_Detune_COP -- mode HifiEng_HRS_FT_COP -- mode HifiEng_LO_FT_IVC_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_Dipscan_calibration_COP with default parameters = 3937 Total duration of HifiEng_Dipscan_CrossTalk_COP with default parameters = 395 Total duration of HifiEng_Dipscan_CrossTalk_Detune_COP with default parameters = 394 Total duration of HifiEng_HRS_FT_COP with default parameters = 1101 Total duration of HifiEng_LO_FT_IVC_COP with default parameters = 227 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> ls -ls total 11840 5912 -rw-r--r-- 1 hscphs2 herschel 6041600 Feb 19 18:29 CYCLE087_HIFI_FULL_2_20130219.tar 4 -rwxr-xr-- 1 hscphs2 herschel 2697 Mar 8 2010 duration_cal.sh* 100 -rw-r--r-- 1 hscphs2 herschel 98300 Feb 12 16:33 HIFI_AOR_C087_113.aor 4 -rw-r--r-- 1 hscphs2 herschel 543 Feb 12 16:55 HIFI_DUR_C087_113.txt 2308 -rw-r--r-- 1 hscphs2 herschel 2353551 Feb 12 16:57 HIFI_MC_R109_FULL_113_0_CUS_CAL.xml 3504 -rw-r--r-- 1 hscphs2 herschel 3577564 Feb 12 16:57 HIFI_MC_R109_FULL_113_0_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 2398 Feb 19 18:25 HIFI_Readme_C087_113.txt 4 -rw-r--r-- 1 hscphs2 herschel 543 Feb 20 15:54 summary_HIFI_AOR_C087_113.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> diff HIFI_DUR_C087_113.txt summary_HIFI_AOR_C087_113.log No differences. Skip from here... 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY In the Comment field, refer to HIFI MC H113CAL 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HIFI> Feb 20, 2013 3:56:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 3:56:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:56:57 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Feb 20, 2013 3:57:51 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY" Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:58:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 3:58:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:58:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 3:58:10 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 20, 2013 3:59:05 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> Feb 20, 2013 4:04:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 4:04:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:04:51 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Feb 20, 2013 4:05:02 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Feb 20, 2013 4:09:59 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 4:10:00 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:10:06 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Feb 20, 2013 4:11:14 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 4:11:14 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:11:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:11:18 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC13_201107041500 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 66.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> cus -m "upload SPIRE MC_66ASTR mission config" -import SPIRE_MC_ASTR_pv92_C059_66_CUS.def -importcaltables SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml Feb 20, 2013 4:13:46 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 4:13:47 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Feb 20, 2013 4:13:55 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:13:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:13:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:13:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:13:56 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 20, 2013 4:13:57 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by SPIRE: SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> ls -ls total 5040 2500 -rw-r--r-- 1 hscphs2 herschel 2549760 Jan 16 2012 CYCLE059_SPIRE_FULL_1_0_20120116.tar 72 -rw-r--r-- 1 hscphs2 herschel 68755 Jan 16 2012 SPIRE_AOR_C059_66_CAL.aor 16 -rw-r--r-- 1 hscphs2 herschel 12651 Jan 16 2012 SPIRE_AOR_C059_66_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2063 Feb 20 16:14 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Jan 16 2012 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5533 Jan 16 2012 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Jan 20 2012 SPIRE_harness_duration_summary_20120120_10h57m25s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Jul 23 2012 SPIRE_harness_duration_summary_20120723_17h58m37s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Feb 20 16:18 SPIRE_harness_duration_summary_20130220_16h18m36s.log 280 -rw-r--r-- 1 hscphs2 herschel 279962 Jan 16 2012 SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml 2124 -rw-r--r-- 1 hscphs2 herschel 2163872 Jan 16 2012 SPIRE_MC_ASTR_pv92_C059_66_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 7286 Jan 16 2012 SPIRE_Readme_C059_66.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20130220_16h18m36s.log Perfect. No differences! 8(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE SPIRE DELIVERY In the Comment field, refer to SPIRE MC S66ASTR. TAKE NOTE : It is very important that you commit the delivery as defined above. 8(g) Import SPIRE model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/SPIRE> Feb 20, 2013 4:33:56 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY" Feb 20, 2013 4:34:12 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY" Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:34:21 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 20, 2013 4:34:38 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY Feb 20, 2013 4:34:41 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Wed Feb 20 14:49:21 2013 from herl38.net4.lan HCSS Version: 10.0.1 PHS Version: 6.3.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] 25954 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Feb 20, 2013 4:49:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 20, 2013 4:49:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Feb 20, 2013 4:49:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Running CDH.getObsProgrammes() Feb 20, 2013 4:49:57 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Feb 20, 2013 4:49:57 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 27 Feb 20, 2013 4:49:57 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Feb 20, 2013 4:49:57 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY" Feb 20, 2013 4:50:01 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 4029 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY Feb 20, 2013 4:53:58 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HifiEng_Fast_LCU_HK_COPGen.prop Feb 20, 2013 4:53:58 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> ls *.prop > & MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18434 Feb 20 16:55 MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> cp MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt /home/hscphs2/icchsc/HSpot_files/ Now do a diff between this new txt file and the one generated with the last Mission configuration. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt MC_H109ASTR_P70ASTR_S66ASTR_CONTINGENCY.txt 18d17 < HifiEng_Dipscan_CrossTalk_Detune_COPGen.prop If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. One new HIFI script. Notify Eva 12. Final Jboss Activities Log into Jboss #2 [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Tue Feb 19 15:10:16 2013 from herl33.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 735 PHS: Astronomers instance 735 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_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY copied HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit phs-operations.props & Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #TIME ESTIMATOR VERSION #hcss.phs.timeEstimatorVersion= MC_H102ASTR_P70ASTR_S66ASTR_RP-120713 #hcss.phs.timeEstimatorVersion=MC_H111_P70_S69_CAL-130214 #hcss.phs.timeEstimatorVersion=MC_H109ASTR_P70ASTR_S66ASTR_CONTINGENCY-130121 hcss.phs.timeEstimatorVersion=MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY-130220 #MISSION CONFIG #hcss.ccm.mission.config = MC_H102ASTR_P70ASTR_S66ASTR_RP #hcss.ccm.mission.config = MC_H111_P70_S69_CAL #hcss.ccm.mission.config = MC_H109ASTR_P70ASTR_S66ASTR_CONTINGENCY hcss.ccm.mission.config = MC_H113ASTR_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_H111_P70_S69_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H109ASTR_P70ASTR_S66ASTR_CONTINGENCY hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H113ASTR_P70ASTR_S66ASTR_CONTINGENCY Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 16379 herjbo02.esac.esa.int/home/hsc_phs/.hcss> ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /herschel/software/phs/jboss/jboss JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar ========================================================================= 17:08:11,421 INFO [Server] Starting JBoss (MX MicroKernel)... 17:08:11,428 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 17:08:11,428 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 17:08:11,428 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 17:08:11,429 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 17:08:11,429 INFO [Server] Patch URL: null 17:08:11,429 INFO [Server] Server Name: phs-operations 17:08:11,429 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 17:08:11,431 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 17:08:11,431 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 17:08:11,431 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 17:08:11,431 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 17:08:11,432 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 17:08:11,432 INFO [Server] Root Deployment Filename: jboss-service.xml 17:08:11,434 INFO [Server] Starting General Purpose Architecture (GPA)... 17:08:11,985 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 17:08:11,985 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 17:08:11,986 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 17:08:12,270 INFO [Server] Core system initialized 17:08:14,444 INFO [ServiceBindingManager] Initializing store 17:08:14,445 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 17:08:14,877 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.