SPIRE Cycle 100 Calibration delivery 1. Delivery Note SPIRE Delivery note - 17th May 2013 Dear Colleagues of the HSC MPS Group, This e-mail is to notify you that I have just uploaded the CYCLE100 tar file onto the CVS server. This file contains the AORs for SPIRE Post-Helium Tests B and C. The contents in the tar files are according to the HSC-ICC Interactions Document, and Larry's latest update. 1. Delivery file, directory & Mission Configuration issues (a) Cycle tar file name : CYCLE100_SPIRE_FULL_1_0_20130517.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle100 2. Mission Configurations (a) Does this delivery include a new Calibration Mission configuration(s)? Yes (b) Does this delivery include a new ASTR mission configurations(s)? No (c) If the answer to point (b) is YES, then have you copied the cCCB@sciops.esa.int in this delivery email? N/A 3. Operations Issues (a) Will any of these delivered observations generate a significant amount of Telecommands? Some individual observations generate up to 1000 TC. (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? No (c) ICC to add anything specific to this OD which HSC & MOC should be aware of. N/A Please acknowledge the receipt of this delivery to us. Kind regards, Sunil Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE100_SPIRE_FULL_1_0_20130517.tar New MC S70CAL 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri May 17 15:34:47 2013 from herl38.net4.lan HCSS Version: 10.1.0 PHS Version: 6.3.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account 3. What is the Mission Configuration Name going to be?? MC_H111CAL_P70_S70_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle88> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle88/SPIRE> mkdir SPIRE_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle100_SPIRE_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_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_H111_P70_S70_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_H111_P70_S70_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_H111_P70_S70_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_H111_P70_S70_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 HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/HIFI> ls CYCLE100_SPIRE_FULL_1_0_20130517.tar HIFI_AOR_C100_111.aor HIFI_MC_R110_FULL_111_0_CUS.def duration_cal.sh* HIFI_DUR_C100_111.txt HIFI_Readme_C100_111.txt HIFI_AOR_C100_102.aor HIFI_MC_R110_FULL_111_0_CUS_CAL.xml summary_HIFI_AOR_C100_111.log 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_Cycle100/SPIRE/SPIRE_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle100/SPIRE/SPIRE_FULL_1> cvs login Logging in to :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle100/SPIRE/SPIRE_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle100/CYCLE100_SPIRE_FULL_1_0_20130517.tar U develop/data/observingmodes/rp_cycles/cycle100/CYCLE100_SPIRE_FULL_1_0_20130517.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle100/SPIRE/SPIRE_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle100/CYCLE100_SPIRE_FULL_1_0_20130517.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle100/SPIRE/SPIRE_FULL_1> ls CYCLE100_SPIRE_FULL_1_0_20130517.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle100/SPIRE/SPIRE_FULL_1> tar -xvf CYCLE100_SPIRE_FULL_1_0_20130517.tar SPIRE_MC_pv96_C100_70_CUS_CAL.xml SPIRE_MC_pv96_C100_70_CUS.def SPIRE_AOR_C100_66_CAL.aor SPIRE_AOR_C100_70_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C100_70.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle100/SPIRE/SPIRE_FULL_1> ls CYCLE100_SPIRE_FULL_1_0_20130517.tar SPIRE_AOR_C100_70_ENG.aor SPIRE_MC_pv96_C100_70_CUS_CAL.xml develop/ SPIRE_CUS_THCP.py SPIRE_MC_pv96_C100_70_CUS.def SPIRE_AOR_C100_66_CAL.aor SPIRE_Duration.txt SPIRE_Readme_C100_70.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle100/SPIRE/SPIRE_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/SPIRE/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/SPIRE> ls CYCLE100_SPIRE_FULL_1_0_20130517.tar SPIRE_CUS_THCP.py SPIRE_MC_pv96_C100_70_CUS.def SPIRE_AOR_C100_66_CAL.aor SPIRE_Duration.txt SPIRE_Readme_C100_70.txt SPIRE_AOR_C100_70_ENG.aor SPIRE_MC_pv96_C100_70_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_H111_P70_S70_CAL/PACS> May 17, 2013 3:57:51 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 3:57:52 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 3:57:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 3:57:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 3:57:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 3:57:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 3:57:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 3:57:53 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument May 17, 2013 3:58:02 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_H111_P70_S70_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_H111_P70_S70_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_H111_P70_S70_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_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 10.1.0 If you haven't done it before: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C068_70.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/PACS> ls -ls total 11660 4 -rwxr-xr-- 1 hscphs2 herschel 1539 May 17 16:01 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 May 17 16:01 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 May 17 16:03 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 84 May 17 16:02 msgPacsEng_ChopperOpenLoop_FullRange.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 May 17 16:02 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 May 17 16:03 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 May 17 16:03 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 May 17 16:04 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 May 17 16:04 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 May 17 16:02 tmp 4 -rw-r--r-- 1 hscphs2 herschel 532 May 17 16:02 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_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_H111_P70_S70_CAL/PACS> missetup -addconfig MC_H111_P70_S70_CAL May 17, 2013 4:05:33 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:05:34 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:05:34 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" May 17, 2013 4:05:45 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H111_P70_S70_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_H111_P70_S70_CAL/PACS> May 17, 2013 4:06:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:06:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:06:11 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument May 17, 2013 4:06:33 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H111_P70_S70_CAL" May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:06:42 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry May 17, 2013 4:06:52 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H111_P70_S70_CAL May 17, 2013 4:07:07 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_H111_P70_S70_CAL/HIFI> May 17, 2013 4:08:39 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:08:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:08:40 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument May 17, 2013 4:08:49 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_H111_P70_S70_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall May 17, 2013 4:09:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:09:38 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:09:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:09:46 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall May 17, 2013 4:10:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:10:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:10:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:10:27 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 (H111Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/HIFI> cus -m "upload HIFI MC111Cal mission config" -import HIFI_MC_R110_FULL_111_0_CUS.def -importcaltables HIFI_MC_R110_FULL_111_0_CUS_CAL.xml May 17, 2013 4:11:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:11:24 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:11:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:11:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:11:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:11:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:11:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported May 17, 2013 4:11:36 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:11:36 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry May 17, 2013 4:11:44 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R110_FULL_111_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_H111_P70_S70_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C087_111 next AOR file = HIFI_AOR_C087_111 -- 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 -- mode HifiSScanModeDBS -- mode HifiSScanModeFastDBS -- mode HifiSScanModeFSwitch -- mode HifiSScanModeFSwitchNoRef -- mode HifiSScanModeLoadChop -- mode HifiSScanModeLoadChopNoRef 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 Total duration of HifiSScanModeDBS with default parameters = 386 Total duration of HifiSScanModeFastDBS with default parameters = 338 Total duration of HifiSScanModeFSwitch with default parameters = 500 Total duration of HifiSScanModeFSwitchNoRef with default parameters = 417 Total duration of HifiSScanModeLoadChop with default parameters = 350 Total duration of HifiSScanModeLoadChopNoRef with default parameters = 285 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/HIFI> ls -ls total 12784 6388 -rw-r--r-- 1 hscphs2 herschel 6522880 Feb 13 18:37 CYCLE087_HIFI_FULL_1_20130213.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Mar 8 2010 duration_cal.sh* 420 -rw-r--r-- 1 hscphs2 herschel 425261 Feb 13 15:52 HIFI_AOR_C087_102.aor 140 -rw-r--r-- 1 hscphs2 herschel 137561 Feb 13 17:42 HIFI_AOR_C087_111.aor 4 -rw-r--r-- 1 hscphs2 herschel 971 Feb 13 17:56 HIFI_DUR_C087_111.txt 2308 -rw-r--r-- 1 hscphs2 herschel 2353551 Feb 13 17:58 HIFI_MC_R110_FULL_111_0_CUS_CAL.xml 3504 -rw-r--r-- 1 hscphs2 herschel 3577564 Feb 13 17:58 HIFI_MC_R110_FULL_111_0_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 9738 Feb 13 18:29 HIFI_Readme_C087_111.txt 4 -rw-r--r-- 1 hscphs2 herschel 971 May 17 16:13 summary_HIFI_AOR_C087_111.log 0 -rw-r--r-- 1 hscphs2 herschel 1 May 17 16:12 summary_HIFI_AOR_C100_111.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/HIFI> diff HIFI_DUR_C087_111.txt summary_HIFI_AOR_C087_111.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 H111CAL 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_H111_P70_S70_CAL/HIFI> May 17, 2013 4:16:25 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:16:26 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:16:26 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument May 17, 2013 4:17:29 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H111_P70_S70_CAL" May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:17:40 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry May 17, 2013 4:18:07 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H111_P70_S70_CAL May 17, 2013 4:18:19 PM herschel.cus.gui.CusEditor exit INFO: Quitting. INFO: Quitting. Steps to Import the New SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the 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_H111_P70_S70_CAL/SPIRE> May 17, 2013 4:19:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:19:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:19:20 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument May 17, 2013 4:19:26 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_H111_P70_S70_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall May 17, 2013 4:19:54 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:19:54 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:19:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:20:00 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall May 17, 2013 4:20:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:20:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:20:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:20:27 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 70.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/SPIRE> cus -m "upload SPIRE MC_70CAL mission config" -import SPIRE_MC_pv96_C100_70_CUS.def -importcaltables SPIRE_MC_pv96_C100_70_CUS_CAL.xml May 17, 2013 4:21:54 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:21:54 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:21:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported May 17, 2013 4:22:03 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:22:03 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry May 17, 2013 4:22:07 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv96_C100_70_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_pv96_C100_70_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/SPIRE> python SPIRE_CUS_THCP.py 2488 -rw-r--r-- 1 hscphs2 herschel 2539520 May 17 15:11 CYCLE100_SPIRE_FULL_1_0_20130517.tar 4 -rw-r--r-- 1 hscphs2 herschel 2133 May 17 14:57 SPIRE_AOR_C100_66_CAL.aor 56 -rw-r--r-- 1 hscphs2 herschel 50213 May 17 14:57 SPIRE_AOR_C100_70_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2137 May 17 16:22 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 May 17 15:02 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5740 May 17 15:02 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5740 May 17 16:26 SPIRE_harness_duration_summary_20130517_16h26m42s.log 284 -rw-r--r-- 1 hscphs2 herschel 283226 May 17 15:02 SPIRE_MC_pv96_C100_70_CUS_CAL.xml 2144 -rw-r--r-- 1 hscphs2 herschel 2184505 May 17 15:02 SPIRE_MC_pv96_C100_70_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5307 May 17 15:05 SPIRE_Readme_C100_70.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H111_P70_S70_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20130517_16h26m42s.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 S70CAL 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_H111_P70_S70_CAL/SPIRE> May 17, 2013 4:29:26 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:29:27 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:29:27 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument May 17, 2013 4:31:15 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H111_P70_S70_CAL" May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:31:23 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry May 17, 2013 4:31:46 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H111_P70_S70_CAL May 17, 2013 4:31:53 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_H111_P70_S70_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri May 17 15:34:54 2013 from herl38.net4.lan HCSS Version: 10.1.0 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] 21321 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> May 17, 2013 4:34:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties May 17, 2013 4:34:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n6@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int May 17, 2013 4:34:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n7@herdb02.esac.esa.int Running CDH.getObsProgrammes() May 17, 2013 4:34:08 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... May 17, 2013 4:34:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 180 May 17, 2013 4:34:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... May 17, 2013 4:34:09 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H111_P70_S70_CAL" May 17, 2013 4:34:12 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3594 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_H111_P70_S70_CAL May 17, 2013 4:36:53 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H111_P70_S70_CAL/HifiEng_Fast_LCU_HK_COPGen.prop May 17, 2013 4:36:53 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H111_P70_S70_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H111_P70_S70_CAL> ls *.prop > MC_H111_P70_S70_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H111_P70_S70_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18532 May 17 16:39 MC_H111_P70_S70_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H111_P70_S70_CAL> cp MC_H111_P70_S70_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_H111_P70_S70_CAL.txt MC_H111_P70_S69_CAL.txt 451,452d450 < SpireEngEepromNominalGen.prop < SpireEngEepromRedundantGen.prop If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. Two new SPIRE scripts. No need to notify Eva (CAL only) 12. Final Jboss Activities Log into Jboss #2 [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Tue May 14 15:51:52 2013 from herl28.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 737 PHS: Astronomers instance 737 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_H111_P70_S70_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_H111_P70_S70_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H111_P70_S70_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_H111_P70_S70_CAL-130517 #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_S70_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_S70_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] 9623 herjbo02.esac.esa.int/home/hsc_phs/.hcss> ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /herschel/software/phs/jboss/jboss JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar ========================================================================= 16:46:21,475 INFO [Server] Starting JBoss (MX MicroKernel)... 16:46:21,477 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 16:46:21,477 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 16:46:21,477 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 16:46:21,477 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 16:46:21,478 INFO [Server] Patch URL: null 16:46:21,478 INFO [Server] Server Name: phs-operations 16:46:21,478 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 16:46:21,478 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 16:46:21,479 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 16:46:21,479 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 16:46:21,479 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 16:46:21,479 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 16:46:21,479 INFO [Server] Root Deployment Filename: jboss-service.xml 16:46:21,481 INFO [Server] Starting General Purpose Architecture (GPA)... 16:46:22,032 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 16:46:22,032 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 16:46:22,033 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 16:46:22,259 INFO [Server] Core system initialized 16:46:24,095 INFO [ServiceBindingManager] Initializing store 16:46:24,095 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 16:46:24,475 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.