HIFI Cycle 59 Calibration delivery HIFI Delivery note - 16th January 2012 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just delivered the calibration delivery for cycle 59, uploading the tar file containing the delivery of HIFI observations for cycle 59 onto the CVS server. 1. Delivery file, directory: a) OD tar file names: - CYCLE059_HIFI_FULL_1_20120116.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle059 2. Mission Configurations: a) Does this delivery include a new Calibration Mission configuration? Yes b) Does this delivery include a new Astro Mission configuration? No 3. Operations Issues a) Will any of these delivered observations generate a significant amount of Telecommands? No b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? Not a requirement. c) ICC to add anything specific to this OD which HSC & MOC should be aware of: Instructions are in the Readme file. This Mission Configuration needs OBSW 6.5.3. Please acknowledge receipt of the e-mail and the delivery. Best regards, Max Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE059_HIFI_FULL_1_20120116.tar New MC - Use MC H97Cal 2. Software used for import [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri Jan 20 14:34:25 2012 from herl38.net4.lan HCSS Version: 7.3.0 PHS Version: 6.0.1 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal: PHS: Using BUILDNUM 534 & PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account 3. What is the Mission Configuration Name going to be?? MC_H97_P68_S64_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle059_HIFI_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_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_H97_P69_S66_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_H97_P69_S66_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H98ASTR_P69ASTR_S66ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_AOR_C059_69.aor 2createOBSMODtable4RP.sh~* PACS_Duration_PACS_compare.txt CYCLE059_PACS_FULL_1_20120113.tar PACS_Duration_PACS.txt msgPacsCal_PacsRangeSpec_PV.txt PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml msgPacsEng_Pacs_EDAC_to_DMC_HK.txt PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def msgPacsLineSpec.txt PACS_Readme_C059_69.txt msgPacsPhoto.txt tmp msgPacsRangeSpec.txt tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_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_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_H97_P69_S66_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt 2createOBSMODtable4RP.sh~* PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml CYCLE059_PACS_FULL_1_20120113.tar PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def PACS_AOR_C059_69.aor PACS_Readme_C059_69.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H98ASTR_P69ASTR_S66ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> ls CYCLE059_SPIRE_FULL_1_0_20120116.tar SPIRE_Duration.txt SPIRE_AOR_C059_66_CAL.aor SPIRE_harness_duration_summary_20120120_10h57m25s.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 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_Cycle59/HIFI/HIFI_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI/HIFI_FULL_1> cvs login Logging in to :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle059/CYCLE059_HIFI_FULL_1_20120116.tar U develop/data/observingmodes/rp_cycles/cycle059/CYCLE059_HIFI_FULL_1_20120116.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI/HIFI_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle059/CYCLE059_HIFI_FULL_1_20120116.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI/HIFI_FULL_1> ls CYCLE059_HIFI_FULL_1_20120116.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI/HIFI_FULL_1> tar -xvf CYCLE059_HIFI_FULL_1_20120116.tar duration_cal.sh HIFI_AOR_C059_97.aor HIFI_AOR_C059_98.aor HIFI_DUR_C059_97.txt HIFI_MC_R100_FULL_97_0_CUS_CAL.xml HIFI_MC_R100_FULL_97_0_CUS.def HIFI_Readme_C059_97.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI/HIFI_FULL_1> ls CYCLE059_HIFI_FULL_1_20120116.tar HIFI_AOR_C059_97.aor HIFI_MC_R100_FULL_97_0_CUS_CAL.xml ls develop/ HIFI_AOR_C059_98.aor HIFI_MC_R100_FULL_97_0_CUS.def duration_cal.sh* HIFI_DUR_C059_97.txt HIFI_Readme_C059_97.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle59/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/HIFI> ls CYCLE059_HIFI_FULL_1_20120116.tar HIFI_AOR_C059_98.aor HIFI_MC_R100_FULL_97_0_CUS.def duration_cal.sh* HIFI_DUR_C059_97.txt HIFI_Readme_C059_97.txt HIFI_AOR_C059_97.aor HIFI_MC_R100_FULL_97_0_CUS_CAL.xml ls 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_H97_P69_S66_CAL/PACS> Jan 20, 2012 5:48:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 5:48:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:48:56 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jan 20, 2012 5:49:12 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_H97_P69_S66_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_H97_P69_S66_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 69.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_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!! 6(e) Run the duration script for the PACS instrument model: Open duration script (2createOBSMODtable4RP.sh) and point it to HCSS 7.3.0 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C056_68.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/PACS> ls -ls total 11492 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Dec 7 09:17 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Dec 7 09:17 2createOBSMODtable4RP.sh~* 5604 -rw-r--r-- 1 hscphs2 herschel 5724160 Nov 30 11:31 CYCLE055_PACS_FULL_2_20111130.tar 124 -rw-r--r-- 1 hscphs2 herschel 122880 Dec 6 11:48 CYCLE056_PACS_FULL_1_20111206.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Dec 19 15:04 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Dec 19 15:03 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Dec 19 15:04 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Dec 19 15:04 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Dec 19 15:05 msgPacsRangeSpec.txt 112 -rw-r--r-- 1 hscphs2 herschel 107840 Dec 6 10:57 PACS_AOR_C056_68.aor 4 -rw-r--r-- 1 hscphs2 herschel 1948 Dec 6 11:33 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 1948 Dec 19 15:05 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404256 Nov 29 10:01 PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS_CAL.xml 5200 -rw-r--r-- 1 hscphs2 herschel 5311479 Nov 29 10:01 PACS_MC_ASTR_OT2_2011-11-25A_C055_68_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 3329 Nov 30 11:26 PACS_Readme_C055_68.txt 8 -rw-r--r-- 1 hscphs2 herschel 7112 Dec 7 09:21 PACS_Readme_C056_68.txt 8 -rw-r--r-- 1 hscphs2 herschel 7080 Dec 7 09:21 PACS_Readme_C056_68.txt~ 4 -rw-r--r-- 1 hscphs2 herschel 1033 Dec 19 15:03 tmp 4 -rw-r--r-- 1 hscphs2 herschel 433 Dec 19 15:03 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! 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 P68ASTR 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_H97_P69_S66_CAL/PACS> missetup -addconfig MC_H97_P69_S66_CAL Jan 20, 2012 5:50:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 5:50:02 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:50:03 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Jan 20, 2012 5:50:03 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H97_P69_S66_CAL" created in database "hsc_ops_operations_tm_1@herd Add the commited CUS to the new MC hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/PACS> Jan 20, 2012 5:51:31 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 5:51:32 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 5:51:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:51:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:51:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:51:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:51:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:51:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:51:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:51:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:51:33 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jan 20, 2012 5:51:49 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H97_P69_S66_CAL" Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:51:59 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 20, 2012 5:52:08 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H97_P69_S66_CAL Jan 20, 2012 5:52:11 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_H97_P69_S66_CAL/HIFI> Jan 20, 2012 5:53:17 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 5:53:18 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:53:19 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jan 20, 2012 5:53:25 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_H97_P69_S66_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Jan 20, 2012 5:53:48 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 5:53:48 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:53:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:53:54 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Jan 20, 2012 5:54:12 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 5:54:13 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:54:17 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 (H95Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/HIFI> cus -m "upload HIFI MC97Cal mission config" -import HIFI_MC_R100_FULL_97_0_CUS.def -importcaltables HIFI_MC_R100_FULL_97_0_CUS_CAL.xml Jan 20, 2012 5:55:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 5:55:42 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:55:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 20, 2012 5:55:54 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 5:55:54 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 20, 2012 5:55:57 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R100_FULL_97_0_CUS_CAL.xml" The final line should give the filename: HIFI_MC_R100_FULL_97_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_H97_P69_S66_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C059_97 next AOR file = HIFI_AOR_C059_97 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP Total duration of HifiEng_Chopper_FT2_COP with default parameters = 114 Total duration of HifiEng_Chopper_Response_time_COP with default parameters = 44 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/HIFI> ls -ls total 11748 5864 -rw-r--r-- 1 hscphs2 herschel 5990400 Jan 16 19:09 CYCLE059_HIFI_FULL_1_20120116.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Mar 8 2010 duration_cal.sh* 8 -rw-r--r-- 1 hscphs2 herschel 4153 Jan 16 16:27 HIFI_AOR_C059_97.aor 88 -rw-r--r-- 1 hscphs2 herschel 85220 Jan 16 16:28 HIFI_AOR_C059_98.aor 4 -rw-r--r-- 1 hscphs2 herschel 156 Jan 16 17:55 HIFI_DUR_C059_97.txt 2316 -rw-r--r-- 1 hscphs2 herschel 2359311 Jan 16 17:57 HIFI_MC_R100_FULL_97_0_CUS_CAL.xml 3456 -rw-r--r-- 1 hscphs2 herschel 3528559 Jan 16 17:56 HIFI_MC_R100_FULL_97_0_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 2382 Jan 16 18:59 HIFI_Readme_C059_97.txt 0 -rw-r--r-- 1 hscphs2 herschel 0 Jan 20 17:46 ls 4 -rw-r--r-- 1 hscphs2 herschel 156 Jan 20 18:22 summary_HIFI_AOR_C059_97.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/HIFI> diff HIFI_DUR_C059_97.txt summary_HIFI_AOR_C059_97.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 H97CAL 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_H97_P69_S66_CAL/HIFI> Jan 20, 2012 6:27:13 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 6:27:13 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:27:14 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jan 20, 2012 6:27:29 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H97_P69_S66_CAL" Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:27:39 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 20, 2012 6:27:50 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H97_P69_S66_CAL Jan 20, 2012 6:27:57 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the Old SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the PACS instrument Import into the new Mission Configuration 8(a) Set Instrument Model = SPIRE #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> Jan 20, 2012 6:29:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 6:29:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:29:37 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jan 20, 2012 6:29:43 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! Have right CUS and CAL already. Skip... 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Dec 19, 2011 4:21:37 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 4:21:38 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 4:21:38 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 4:21:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 4:21:38 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 4:21:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 4:21:38 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 4:21:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 4:21:38 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 4:21:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 4:21:44 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Dec 19, 2011 4:22:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 4:22:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 4:22:01 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 4:22:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 4:22:01 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 4:22:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 4:22:01 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 4:22:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 4:22:01 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 4:22:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 4:22:04 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC13_201107041500 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 64.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> cus -m "upload SPIRE MC_64CAL mission config" -import SPIRE_MC_pv90_C047_64_CUS.def -importcaltables SPIRE_MC_pv90_C047_64_CUS_CAL.xml Dec 19, 2011 4:24:19 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Dec 19, 2011 4:24:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Dec 19, 2011 4:24:20 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 4:24:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Dec 19, 2011 4:24:20 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 4:24:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Dec 19, 2011 4:24:20 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 4:24:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Dec 19, 2011 4:24:20 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 4:24:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Dec 19, 2011 4:24:28 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Dec 19, 2011 4:24:28 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Dec 19, 2011 4:24: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 4:24: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 4:24: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 4:24: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 4:24: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 4:24: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 4:24: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 4:24: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 4:24:28 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Dec 19, 2011 4:24:30 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv90_C047_64_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_pv90_C047_64_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> ls -ls total 5276 2608 -rw-r--r-- 1 hscphs2 herschel 2662400 Jul 29 13:51 CYCLE047_SPIRE_FULL_1_0_20110729.tar 92 -rw-r--r-- 1 hscphs2 herschel 86445 Jul 29 13:34 SPIRE_AOR_C047_64_CAL.aor 48 -rw-r--r-- 1 hscphs2 herschel 43227 Jul 29 13:34 SPIRE_AOR_C047_64_ENG.aor 72 -rw-r--r-- 1 hscphs2 herschel 65891 Jul 29 13:37 SPIRE_AOR_C047_64_REDYandSTBY.aor 4 -rw-r--r-- 1 hscphs2 herschel 2063 Dec 19 16:25 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Jul 29 13:37 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5533 Jul 29 13:37 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Jul 29 17:09 SPIRE_harness_duration_summary_20110729_17h09m03s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Sep 27 16:33 SPIRE_harness_duration_summary_20110927_16h33m32s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Dec 19 16:29 SPIRE_harness_duration_summary_20111219_16h29m05s.log 280 -rw-r--r-- 1 hscphs2 herschel 279503 Jul 29 13:37 SPIRE_MC_pv90_C047_64_CUS_CAL.xml 2124 -rw-r--r-- 1 hscphs2 herschel 2163008 Jul 29 13:37 SPIRE_MC_pv90_C047_64_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8320 Jul 29 13:45 SPIRE_Readme_C047_64.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20111219_16h29m05s.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 S64Cal. TAKE NOTE : It is very important that you commit the delivery as defined above. Re-join here... 8(g) Import SPIRE model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H97_P69_S66_CAL/SPIRE> Jan 20, 2012 6:30:25 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 6:30:26 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:30:26 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jan 20, 2012 6:30:43 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H97_P69_S66_CAL" Jan 20, 2012 6:30:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:30:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:30:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:30:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:30:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:30:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:30:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:30:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:30:53 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 20, 2012 6:31:02 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H97_P69_S66_CAL Jan 20, 2012 6:31:07 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_H97_P69_S66_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Fri Jan 20 17:17:56 2012 from herm16.net3.lan HCSS Version: 7.3.0 PHS Version: 6.0.1 Enable gyro pointing... hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H73_P65_S62_GYRO> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> propHandler & [1] 8471 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Jan 20, 2012 6:32:08 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 6:32:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 6:32:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Running CDH.getObsProgrammes() Jan 20, 2012 6:32:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Jan 20, 2012 6:32:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 24 Jan 20, 2012 6:32:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Jan 20, 2012 6:32:09 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H97_P69_S66_CAL" Jan 20, 2012 6:32:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3794 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_H97_P69_S66_CAL Jan 20, 2012 6:34:06 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H97_P69_S66_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Jan 20, 2012 6:34:06 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H97_P69_S66_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H97_P69_S66_CAL> ls *.prop > & MC_H97_P69_S66_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H97_P69_S66_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18246 Jan 20 18:34 MC_H97_P69_S66_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H97_P69_S66_CAL> cp MC_H97_P69_S66_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_H95_P68_S64_CAL.txt MC_H97_P69_S66_CAL.txt If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. No new HIFI script. Do not notify Eva 12. Final Jboss Activities Log into Jboss #2 [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Fri Jan 20 17:26:30 2012 from herl38.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 705 PHS: Astronomers instance 705 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the Operations Jboss : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H97_P69_S66_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_H97_P69_S66_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H97_P69_S66_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_H96ASTR_P68ASTR_S63ASTR_RP-111215 #hcss.phs.timeEstimatorVersion= MC_H98ASTR_P69ASTR_S66ASTR_RP-120120 hcss.phs.timeEstimatorVersion=MC_H97_P69_S66_CAL-120120 #MISSION CONFIG #hcss.ccm.mission.config = MC_H96ASTR_P68ASTR_S63ASTR_RP #hcss.ccm.mission.config = MC_H98ASTR_P69ASTR_S66ASTR_RP hcss.ccm.mission.config = MC_H97_P69_S66_CAL #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H96ASTR_P68ASTR_S63ASTR_RP #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H98ASTR_P69ASTR_S66ASTR_RP hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H97_P69_S66_CAL Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 7461 herjbo02.esac.esa.int/home/hsc_phs/.hcss> ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /herschel/software/phs/jboss/jboss JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar ========================================================================= 18:59:08,361 INFO [Server] Starting JBoss (MX MicroKernel)... 18:59:08,361 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 18:59:08,362 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 18:59:08,362 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 18:59:08,362 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 18:59:08,362 INFO [Server] Patch URL: null 18:59:08,362 INFO [Server] Server Name: phs-operations 18:59:08,363 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 18:59:08,363 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 18:59:08,363 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 18:59:08,363 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 18:59:08,363 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 18:59:08,363 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 18:59:08,364 INFO [Server] Root Deployment Filename: jboss-service.xml 18:59:08,365 INFO [Server] Starting General Purpose Architecture (GPA)... 18:59:08,493 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 18:59:08,493 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 18:59:08,493 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 18:59:08,616 INFO [Server] Core system initialized 18:59:09,859 INFO [ServiceBindingManager] Initializing store 18:59:09,860 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 18:59:10,124 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.