SPIRE Cycle 66 Calibration MC delivery 1. Delivery Note SPIRE Delivery note - 23rd April 2012 Dear Colleagues of the HSC MPS Group, This e-mail is to notify you that I have just uploaded the SPIRE Routine Calibration CYCLE066 tar file onto the CVS server. The contents in the tar files are according to the HSC-ICC Interactions Document, and Larry's latest update. 1. Delivery file, directory & Mission Configuration issues (a) Cycle tar file name : CYCLE066_SPIRE_FULL_1_0_20120423.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle066 2. Mission Configurations (a) Does this delivery include a new Calibration Mission configuration(s)? Yes (b) Does this delivery include a new ASTR mission configurations(s)? No (c) If the answer to point (b) is YES, then have you copied the cCCB@sciops.esa.int in this delivery email? N/A 3. Operations Issues (a) Will any of these delivered observations generate a significant amount of Telecommands? Some individual observations generate up to 1000 TC. (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? As agreed in the planning meeting, our 'SpireEngDumpMemory' might go into a Real Time Science period of the DTCP depending on the mission planning, but this is no longer necessary. (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) CYCLE066_SPIRE_FULL_1_0_20120423.tar New MC S67CAL 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Mon Apr 23 17:28:32 2012 from herl38.net4.lan HCSS Version: 8.2.0 PHS Version: 6.1.1 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account 3. What is the Mission Configuration Name going to be?? MC_H100CAL_P69_S68_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/SPIRE> mkdir SPIRE_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle066_SPIRE_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the SPIRE & PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H100_P69_S68_CAL folder. Next remove in the SPIRE & HIFI subfolders all files which were created when you ran the SPIRE duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100CAL_P69_S68_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100CAL_P69_S68_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_H100_P69_S68_CAL/PACS> rm msg* PACS_Duration_PACS.txt rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.txt'? y rm: remove regular file `msgPacsEng_Pacs_EDAC_to_DMC_HK.txt'? y rm: remove regular file `msgPacsLineSpec.txt'? y rm: remove regular file `msgPacsPhoto.txt'? y rm: remove regular file `msgPacsRangeSpec.txt'? y rm: remove regular file `PACS_Duration_PACS.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt tmp 2createOBSMODtable4RP.sh~* PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml tmpobsmode CYCLE059_PACS_FULL_1_20120113.tar PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def PACS_AOR_C059_69.aor PACS_Readme_C059_69.txt HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100CAL_P69_S68_CAL/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100CAL_P69_S68_CAL/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml importall.sh* CYCLE062_HIFI_FULL_2_20120227.tar HIFI_MC_ASTR_A0055_C062_100_CUS.def Summary_durations.txt default-durations.dat HIFI_MC_ASTR_A0055_C062_100.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100CAL_P69_S68_CAL/HIFI> rm Summary_durations.txt rm: remove regular file `Summary_durations.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100CAL_P69_S68_CAL/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml importall.sh* CYCLE062_HIFI_FULL_2_20120227.tar HIFI_MC_ASTR_A0055_C062_100_CUS.def default-durations.dat HIFI_MC_ASTR_A0055_C062_100.txt 6(a) Download & Untar the SPIRE delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/SPIRE/SPIRE_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/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_Cycle66/SPIRE/SPIRE_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle066/CYCLE066_SPIRE_FULL_1_0_20120423.tar U develop/data/observingmodes/rp_cycles/cycle066/CYCLE066_SPIRE_FULL_1_0_20120423.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/SPIRE/SPIRE_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle066/CYCLE066_SPIRE_FULL_1_0_20120423.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/SPIRE/SPIRE_FULL_1> ls CYCLE066_SPIRE_FULL_1_0_20120423.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/SPIRE/SPIRE_FULL_1> tar -xvf CYCLE066_SPIRE_FULL_1_0_20120423.tar SPIRE_MC_pv94_C066_68_CUS_CAL.xml SPIRE_MC_pv94_C066_68_CUS.def SPIRE_AOR_C066_68_CAL.aor SPIRE_AOR_C066_68_ENG.aor SPIRE_AOR_C066_68_REDYandSTBY.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C066_68.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/SPIRE/SPIRE_FULL_1> ls CYCLE066_SPIRE_FULL_1_0_20120423.tar SPIRE_AOR_C066_68_REDYandSTBY.aor SPIRE_MC_pv94_C066_68_CUS.def develop/ SPIRE_CUS_THCP.py SPIRE_Readme_C066_68.txt SPIRE_AOR_C066_68_CAL.aor SPIRE_Duration.txt SPIRE_AOR_C066_68_ENG.aor SPIRE_MC_pv94_C066_68_CUS_CAL.xml hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle66/SPIRE/SPIRE_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/SPIRE/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/SPIRE> ls CYCLE066_SPIRE_FULL_1_0_20120423.tar SPIRE_AOR_C066_68_REDYandSTBY.aor SPIRE_MC_pv94_C066_68_CUS_CAL.xml SPIRE_AOR_C066_68_CAL.aor SPIRE_CUS_THCP.py SPIRE_MC_pv94_C066_68_CUS.def SPIRE_AOR_C066_68_ENG.aor SPIRE_Duration.txt SPIRE_Readme_C066_68.txt 6(b) To import the old PACS delivery: #CUS #var.hcss.instrument = SPIRE var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/PACS> Apr 24, 2012 8:51:10 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 8:51:11 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:51:11 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 24, 2012 8:52:06 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Correct Cal and CUS loaded, so skip from here... 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H98ASTR_P68ASTR_S66ASTR_RP/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Jan 20, 2012 10:00:46 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:00:46 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:00:47 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:00:53 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H98ASTR_P68ASTR_S66ASTR_RP/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Jan 20, 2012 10:01:13 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:01:14 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:01:14 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:01:17 AM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC13 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props Import old Mission Configuration (Version 68.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/PACS> cus -m "upload PACS_MC P69ASTR mission config" -import PACS_MC_ASTR_OT2_2012-01-10A_C065_69_CUS.def -importcaltables PACS_MC_ASTR_OT2_2012-01-10A_C065_69_CUS_CAL.xml Jan 20, 2012 10:08:25 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:08:25 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:08:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 20, 2012 10:08:37 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Jan 20, 2012 10:08:37 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 20, 2012 10:08:43 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT2_2012-01-10A_C065_69_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by PACS: PACS_MC_ASTR_OT2_2012-01-10A_C065_69_CUS_CAL.xml CONFIRMED!! Re-join here... 6(e) Run the duration script for the PACS instrument model: Point duration script to latest HCSS version... (8.2.0) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle65/PACS/PACS_FULL_1> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C059_69.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/PACS> ls -ls total 11604 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 24 08:52 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 24 08:52 2createOBSMODtable4RP.sh~* 5784 -rw-r--r-- 1 hscphs2 herschel 5908480 Jan 13 15:52 CYCLE059_PACS_FULL_1_20120113.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Apr 24 08:54 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Apr 24 08:53 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Apr 24 08:54 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Apr 24 08:53 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Apr 24 08:55 msgPacsRangeSpec.txt 176 -rw-r--r-- 1 hscphs2 herschel 172240 Jan 13 14:57 PACS_AOR_C059_69.aor 4 -rw-r--r-- 1 hscphs2 herschel 2687 Jan 13 15:40 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2687 Apr 24 08:55 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404629 Jan 13 15:07 PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml 5200 -rw-r--r-- 1 hscphs2 herschel 5311479 Jan 13 15:07 PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8547 Jan 13 15:48 PACS_Readme_C059_69.txt 4 -rw-r--r-- 1 hscphs2 herschel 1560 Apr 24 08:53 tmp 4 -rw-r--r-- 1 hscphs2 herschel 633 Apr 24 08:53 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle65/PACS/PACS_FULL_1> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! Skip from here... 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS MC P69ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. Re-join here... Now create the MC in the database hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/PACS> missetup -addconfig MC_H100_P69_S68_CAL Apr 24, 2012 8:58:54 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 8:58:54 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:58:55 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Apr 24, 2012 8:59:02 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H100_P69_S68_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_H100_P69_S68_CAL/PACS> Apr 24, 2012 8:59:25 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 8:59:26 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:59:26 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 24, 2012 8:59:51 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100_P69_S68_CAL" Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 8:59:59 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 24, 2012 9:00:32 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H100_P69_S68_CAL Apr 24, 2012 9:00:39 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(b) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/HIFI> Apr 24, 2012 9:01:39 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:01:40 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:01:40 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 24, 2012 9:03:01 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Apr 24, 2012 9:04:09 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:04:09 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:04:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:04:17 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Apr 24, 2012 9:05:12 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:05:12 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:05:12 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:05:12 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:05:12 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:05:12 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:05:12 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:05:12 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:05:13 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:05:13 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:05:16 AM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC13_20111011030 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (H100ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/HIFI> cus -m "upload HIFI MC H100ASTR mission config" -import HIFI_MC_ASTR_A0055_C062_100_CUS.def -importcaltables HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml Apr 9, 2012 12:07:39 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2012 12:07:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:47 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 9, 2012 12:07:47 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 9, 2012 12:07:48 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 9, 2012 12:07:50 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by HIFI: HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml CONFIRMED!! Re-join here... 7(e) Run the duration script for the HIFI instrument Run the duration script delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/HIFI> ls -ls total 6900 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 2010 cus-defdur.sh* 3428 -rw-r--r-- 1 hscphs2 herschel 3502080 Feb 28 16:41 CYCLE062_HIFI_FULL_2_20120227.tar 32 -rw-r--r-- 1 hscphs2 herschel 29834 Feb 27 10:19 default-durations.dat 1416 -rw-r--r-- 1 hscphs2 herschel 1442078 Feb 27 10:19 HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml 1980 -rw-r--r-- 1 hscphs2 herschel 2020120 Feb 27 10:19 HIFI_MC_ASTR_A0055_C062_100_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1067 Feb 27 10:25 HIFI_MC_ASTR_A0055_C062_100.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 2010 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29834 Apr 24 09:25 Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/HIFI> diff default-durations.dat Summary_durations.txt Perfect! 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 H100ASTR as CAL 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_H100_P69_S68_CAL/HIFI> Apr 24, 2012 9:26:52 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:26:53 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:26:53 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 24, 2012 9:27:57 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100_P69_S68_CAL" Apr 24, 2012 9:28:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:28:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:28:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:28:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:28:05 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:28:05 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:28:05 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:28:05 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:28:05 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 24, 2012 9:28:15 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H100_P69_S68_CAL Apr 24, 2012 9:28:31 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the new SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the PACS instrument Import into the new Mission Configuration 8(a) Set Instrument Model = SPIRE #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> Apr 24, 2012 9:46:37 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:46:38 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:46:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:46:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:46:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:46:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:46:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:46:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:46:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:46:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:46:42 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 24, 2012 9:47:05 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> cus -f -m "clean SPIRE CUS from DB" -deleteall Apr 24, 2012 9:47:32 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:47:32 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:47:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:47:39 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Apr 24, 2012 9:48:06 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:48:07 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:48:07 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:48:07 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:48:07 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:48:07 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:48:07 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:48:07 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:48:08 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:48:08 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:48:11 AM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC13_20111011030 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import new SPIRE Mission Configuration (Version 68.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/SPIRE> cus -m "upload SPIRE MC_68CAL mission config" -import SPIRE_MC_pv94_C066_68_CUS.def -importcaltables SPIRE_MC_pv94_C066_68_CUS_CAL.xml Apr 24, 2012 9:51:17 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:51:17 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:51:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:51:26 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 24, 2012 9:51:26 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 24, 2012 9:51:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:51:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:51:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:51:26 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:51:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:51:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:51:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:51:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:51:27 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 24, 2012 9:51:32 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv94_C066_68_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_pv94_C066_68_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/SPIRE> ls -ls total 5572 2768 -rw-r--r-- 1 hscphs2 herschel 2826240 Apr 23 18:40 CYCLE066_SPIRE_FULL_1_0_20120423.tar 248 -rw-r--r-- 1 hscphs2 herschel 247393 Apr 23 18:27 SPIRE_AOR_C066_68_CAL.aor 44 -rw-r--r-- 1 hscphs2 herschel 40296 Apr 23 18:28 SPIRE_AOR_C066_68_ENG.aor 72 -rw-r--r-- 1 hscphs2 herschel 65891 Apr 23 18:36 SPIRE_AOR_C066_68_REDYandSTBY.aor 4 -rw-r--r-- 1 hscphs2 herschel 2063 Apr 24 09:52 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Apr 23 18:28 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5533 Apr 23 18:34 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Apr 24 09:56 SPIRE_harness_duration_summary_20120424_09h56m15s.log 280 -rw-r--r-- 1 hscphs2 herschel 281472 Apr 23 18:28 SPIRE_MC_pv94_C066_68_CUS_CAL.xml 2124 -rw-r--r-- 1 hscphs2 herschel 2165953 Apr 23 18:28 SPIRE_MC_pv94_C066_68_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 10411 Apr 23 18:35 SPIRE_Readme_C066_68.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100_P69_S68_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20120424_09h56m15s.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 S68CAL 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_H100_P69_S68_CAL/SPIRE> Apr 24, 2012 9:57:54 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 9:57:55 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 9:57:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:57:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:57:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:57:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:57:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:57:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:57:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:57:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:57:56 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 24, 2012 9:59:22 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100_P69_S68_CAL" Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 9:59:38 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 24, 2012 9:59:45 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H100_P69_S68_CAL Apr 24, 2012 10:00:28 AM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. 9.Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophandler to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H100_P69_S68_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Apr 24 08:46:58 2012 from herl38.net4.lan HCSS Version: 8.2.0 PHS Version: 6.1.1 hscphs2@heropl02/home/hscphs2> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> propHandler & [1] 2475 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Apr 24, 2012 10:12:23 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 24, 2012 10:12:24 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 24, 2012 10:12:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 10:12:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 24, 2012 10:12:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 10:12:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 24, 2012 10:12:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 10:12:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 24, 2012 10:12:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 24, 2012 10:12:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Running CDH.getObsProgrammes() Apr 24, 2012 10:12:25 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Apr 24, 2012 10:12:27 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 2339 Apr 24, 2012 10:12:27 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Apr 24, 2012 10:12:27 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100_P69_S68_CAL" hscphs2@heropl02/home/hscphs2> Apr 24, 2012 10:12:56 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 29169 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration : CONFIRMED!! 10. Export the HSpot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. CONFIRMED!! Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same as the Mission Confifguration: MC_H100_P69_S68_CAL Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H100_P69_S68_CAL Example of the last entry in the log: Apr 24, 2012 10:15:47 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H100_P69_S68_CAL/HifiSScanProcLoadChopNoRefGen.prop Apr 24, 2012 10:15:47 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H100_P69_S68_CAL/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H100_P69_S68_CAL> ls *.prop > MC_H100_P69_S68_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H100_P69_S68_CAL> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 14263 Apr 24 10:16 MC_H100_P69_S68_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H88ASTR_P67ASTR_S63ASTR_RP> cp MC_H100_P69_S68_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_H100_P69_S67_CAL.txt MC_H100_P69_S68_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 SPIRE script Do not notify Eva 12. Final Jboss Activities [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Wed Apr 18 11:52:01 2012 from herl28.net4.lan herjbo02.esac.esa.int/home/hsc_phs> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 718 PHS: Astronomers instance 705 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the JBOSS : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H100_P69_S68_CAL Copy HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H88ASTR_P67ASTR_S63ASTR_RP> scp *.prop hsc_phs@herjbo02.esac.esa.int:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H100_P69_S68_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_H100ASTR_P69ASTR_S66ASTR_RP-120229 #hcss.phs.timeEstimatorVersion=MC_H99_P69_S66_CAL-120228 #hcss.phs.timeEstimatorVersion=MC_H100_P69_S67_CAL-120409 hcss.phs.timeEstimatorVersion=MC_H100_P69_S68_CAL-120424 #MISSION CONFIG #hcss.ccm.mission.config = MC_H100ASTR_P69ASTR_S66ASTR_RP #hcss.ccm.mission.config = MC_H99_P69_S66_CAL #hcss.ccm.mission.config = MC_H100_P69_S67_CAL hcss.ccm.mission.config = MC_H100_P69_S68_CAL #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H100ASTR_P69ASTR_S66ASTR_RP #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H99_P69_S66_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H100_P69_S67_CAL hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H100_P69_S68_CAL herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 23442 [1] + Done kedit phs-operations.props 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 ========================================================================= 10:29:44,258 INFO [Server] Starting JBoss (MX MicroKernel)... 10:29:44,262 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 10:29:44,263 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 10:29:44,263 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 10:29:44,263 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 10:29:44,263 INFO [Server] Patch URL: null 10:29:44,263 INFO [Server] Server Name: phs-operations 10:29:44,263 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 10:29:44,264 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 10:29:44,264 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 10:29:44,264 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 10:29:44,264 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 10:29:44,264 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 10:29:44,264 INFO [Server] Root Deployment Filename: jboss-service.xml 10:29:44,266 INFO [Server] Starting General Purpose Architecture (GPA)... 10:29:44,857 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 10:29:44,858 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 10:29:44,858 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 10:29:45,099 INFO [Server] Core system initialized 10:29:47,027 INFO [ServiceBindingManager] Initializing store 10:29:47,027 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 10:29:47,423 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.