HIFI Cycle 62 ASTR MC 1. Delivery Note HIFI Delivery note - 28th February 2012 Dear colleagues, This e-mail is to notify you that HIFI ICC has just uploaded the tar file containing the HIFI ASTR CUS delivery for cycle 62 onto the CVS server. 1. Delivery file, directory & Mission Configuration issues (a) Cycle tar file name : CYCLE062_HIFI_FULL_2_20120227.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle062 (c) SCR covering the delivery: HIFIMC-248 2. Mission Configurations (a) Does this delivery include a new Calibration Mission configuration(s)? NO (b) Does this delivery include a new ASTR mission configurations(s)? YES (c) If the answer to point (b) is YES, then have you copied the cCCB@sciops.esa.int in this delivery email? YES 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? NA (c) ICC to add anything specific to this OD which HSC & MOC should be aware of: Please acknowledge the receipt of this delivery to us. Cheers Volker Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE062_HIFI_FULL_2_20120227.tar New MC - MC H100ASTR 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Feb 28 15:11:03 2012 from herl38.net4.lan HCSS Version: 8.1.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_H100ASTR_P69ASTR_S66ASTR_RP 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/SPIRE> mkdir SPIRE_FULL_1 hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI> mkdir HIFI_FULL_2 This LOG file has been placed in the /logs directory and given the name Cycle062_HIFI_FULL_2.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP> 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_H100ASTR_P69ASTR_S66ASTR_RP folder. Next remove in the SPIRE & PACS 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/delivery/Calibration_Cycle62/PACS/PACS_FULL_1> cp /home/hscphs2/icchsc/mission_config/MC_H98ASTR_P69ASTR_S66ASTR_RP/PACS/* . cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/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_H100ASTR_P69ASTR_S66ASTR_RP/PACS> rm msg* PACS_Duration_PACS.txt tmp* 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 rm: remove regular file `tmp'? y rm: remove regular file `tmpobsmode'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/PACS> ls 2createOBSMODtable4RP.sh* PACS_AOR_C059_69.aor PACS_Readme_C059_69.txt 2createOBSMODtable4RP.sh~* PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS_CAL.xml PACS_Duration_PACS_compare.txt CYCLE059_PACS_FULL_1_20120113.tar PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H98ASTR_P69ASTR_S66ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/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 HIFI delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> cvs login Logging in to :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> cvs co develop/data/observingmodes/rp_cycles/cycle062/CYCLE062_HIFI_FULL_2_20120227.tar U develop/data/observingmodes/rp_cycles/cycle062/CYCLE062_HIFI_FULL_2_20120227.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> cp develop/data/observingmodes/rp_cycles/cycle062/CYCLE062_HIFI_FULL_2_20120227.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> ls CYCLE062_HIFI_FULL_2_20120227.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> tar -xvf CYCLE062_HIFI_FULL_2_20120227.tar HIFI_MC_ASTR_A0055_C062_100.txt HIFI_MC_ASTR_A0055_C062_100_CUS.def HIFI_MC_ASTR_A0055_C062_100_CUS_CAL.xml default-durations.dat cus-defdur.sh importall.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> ls cus-defdur.sh* develop/ HIFI_MC_ASTR_A0054_C059_98.txt CYCLE059_HIFI_FULL_2_20120116.tar HIFI_MC_ASTR_A0054_C059_98_CUS_CAL.xml importall.sh* default-durations.dat HIFI_MC_ASTR_A0054_C059_98_CUS.def hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/HIFI/HIFI_FULL_2> cp * /home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/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(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_H100ASTR_P69ASTR_S66ASTR_RP/PACS> Feb 29, 2012 9:22:07 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 9:22:08 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:22:09 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 29, 2012 9:22:44 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Correct CUS and CAL loaded. Skip this... 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_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_H100ASTR_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_H100ASTR_P69ASTR_S66ASTR_RP/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_H100ASTR_P69ASTR_S66ASTR_RP/PACS> cus -m "upload PACS_MC P69ASTR mission config" -import PACS_MC_ASTR_OT2_2012-01-10A_C059_69_CUS.def -importcaltables PACS_MC_ASTR_OT2_2012-01-10A_C059_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_C059_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_C059_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.1.0) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/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_H100ASTR_P69ASTR_S66ASTR_RP/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/PACS> ls -ls total 11604 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Feb 29 09:24 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Feb 29 09:24 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 Feb 29 09:25 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Feb 29 09:24 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Feb 29 09:26 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Feb 29 09:25 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Feb 29 09:27 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 Feb 29 09:27 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 Feb 29 09:24 tmp 4 -rw-r--r-- 1 hscphs2 herschel 633 Feb 29 09:24 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle62/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_H100ASTR_P69ASTR_S66ASTR_RP/PACS> missetup -addconfig MC_H100ASTR_P69ASTR_S66ASTR_RP Feb 29, 2012 9:31:31 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 9:31:31 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:31:32 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Feb 29, 2012 9:32:00 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H100ASTR_P69ASTR_S66ASTR_RP" 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_H100ASTR_P69ASTR_S66ASTR_RP/PACS> Feb 29, 2012 9:35:22 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 9:35:23 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:35:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:35:24 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 29, 2012 9:36:13 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100ASTR_P69ASTR_S66ASTR_RP" Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:36:27 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 29, 2012 9:36:39 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H100ASTR_P69ASTR_S66ASTR_RP Feb 29, 2012 9:37:01 AM 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(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_H100ASTR_P69ASTR_S66ASTR_RP/HIFI> Jan 20, 2012 10:17:42 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:17:43 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:17:43 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:17:43 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:17:43 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:17:43 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:17:43 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:17:43 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:17:43 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:17:43 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:17:43 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jan 20, 2012 10:18:29 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_H100ASTR_P69ASTR_S66ASTR_RP/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Feb 29, 2012 9:43:41 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 9:43:41 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:43:42 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:43:50 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Feb 29, 2012 9:44:18 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 9:44:19 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:44:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:44:23 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 new Mission Configuration (H98ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/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 Feb 29, 2012 9:47:10 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 9:47:10 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:47:11 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:47:19 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Feb 29, 2012 9:47:19 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 9:47:20 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 29, 2012 9:47:24 AM 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!! 7(e) Run the duration script for the HIFI instrument Run the duration script delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/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 Feb 29 10:10 Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/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 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_H100ASTR_P69ASTR_S66ASTR_RP/HIFI> Feb 29, 2012 10:16:24 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 10:16:25 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:16:25 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Feb 29, 2012 10:17:54 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100ASTR_P69ASTR_S66ASTR_RP" Feb 29, 2012 10:18:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:18:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:18:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:18:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:18:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:18:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:18:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:18:04 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:18:04 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 29, 2012 10:18:23 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H100ASTR_P69ASTR_S66ASTR_RP Feb 29, 2012 10:18: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_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> Feb 29, 2012 10:19:27 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 10:19:28 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 10:19:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:19:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:19:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:19:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:19:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:19:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:19:29 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:19:29 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:19:29 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Feb 29, 2012 10:21:03 AM 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 loaded. Skip from here... 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Jan 20, 2012 10:50:07 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:50:08 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:50:08 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:50:08 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:50:08 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:50:08 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:50:08 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:50:08 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:50:08 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:50:08 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:50:13 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jan 20, 2012 10:51:00 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:51:00 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:51:01 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:51:01 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:51:01 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:51:01 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:51:01 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:51:01 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:51:01 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:51:01 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:51:04 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 66.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> cus -m "upload SPIRE MC_66ASTR mission config" -import SPIRE_MC_ASTR_pv92_C059_66_CUS.def -importcaltables SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml Jan 20, 2012 10:52:26 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Jan 20, 2012 10:52:27 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 20, 2012 10:52:27 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:52:27 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:52:27 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:52:27 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:52:27 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:52:27 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:52:27 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:52:27 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:52:35 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 20, 2012 10:52:35 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 20, 2012 10:52:36 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:52:36 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:52:36 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:52:36 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:52:36 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:52:36 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:52:36 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:52:36 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:52:36 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 20, 2012 10:52:38 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by SPIRE: SPIRE_MC_ASTR_pv89_C042_1_CAL.def CONFIRMED!! Re-join here... 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> ls -ls total 5032 2500 -rw-r--r-- 1 hscphs2 herschel 2549760 Jan 16 17:07 CYCLE059_SPIRE_FULL_1_0_20120116.tar 72 -rw-r--r-- 1 hscphs2 herschel 68755 Jan 16 16:43 SPIRE_AOR_C059_66_CAL.aor 16 -rw-r--r-- 1 hscphs2 herschel 12651 Jan 16 16:43 SPIRE_AOR_C059_66_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2063 Feb 29 10:22 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Jan 16 16:56 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5533 Jan 16 16:56 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Jan 20 10:57 SPIRE_harness_duration_summary_20120120_10h57m25s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5533 Feb 29 10:26 SPIRE_harness_duration_summary_20120229_10h26m13s.log 280 -rw-r--r-- 1 hscphs2 herschel 279962 Jan 16 16:56 SPIRE_MC_ASTR_pv92_C059_66_CUS_CAL.xml 2124 -rw-r--r-- 1 hscphs2 herschel 2163872 Jan 16 16:56 SPIRE_MC_ASTR_pv92_C059_66_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 7286 Jan 16 17:03 SPIRE_Readme_C059_66.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20120229_10h26m13s.log Perfect. No differences! Skip this... 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 S63ASTR 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_H100ASTR_P69ASTR_S66ASTR_RP/SPIRE> Feb 29, 2012 10:28:09 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 10:28:09 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:28:10 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Feb 29, 2012 10:29:00 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100ASTR_P69ASTR_S66ASTR_RP" Feb 29, 2012 10:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:29:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:29:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:29:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:29:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:29:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:29:10 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 29, 2012 10:29:17 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H100ASTR_P69ASTR_S66ASTR_RP Feb 29, 2012 10:29:22 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_H100ASTR_P69ASTR_S66ASTR_RP [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Wed Feb 29 10:20:54 2012 from herl22.net4.lan HCSS Version: 8.1.0 PHS Version: 6.1.1 hscphs2@heropl02/home/hscphs2> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props hscphs2@heropl02/home/hscphs2> propHandler & [1] 12257 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Feb 29, 2012 10:38:38 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Feb 29, 2012 10:38:38 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 29, 2012 10:38:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:38:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 29, 2012 10:38:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:38:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 29, 2012 10:38:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:38:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 29, 2012 10:38:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Feb 29, 2012 10:38:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Running CDH.getObsProgrammes() Feb 29, 2012 10:38:40 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Feb 29, 2012 10:38:40 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 25 Feb 29, 2012 10:38:40 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Feb 29, 2012 10:38:40 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H100ASTR_P69ASTR_S66ASTR_RP" Feb 29, 2012 10:38:43 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3357 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_H100ASTR_P69ASTR_S66ASTR_RP Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H100ASTR_P69ASTR_S66ASTR_RP Example of the last entry in the log: Feb 29, 2012 10:41:11 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H100ASTR_P69ASTR_S66ASTR_RP/HifiSScanProcLoadChopNoRefGen.prop Feb 29, 2012 10:41:11 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H100ASTR_P69ASTR_S66ASTR_RP/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H100ASTR_P69ASTR_S66ASTR_RP> ls *.prop > MC_H100ASTR_P69ASTR_S66ASTR_RP.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H100ASTR_P69ASTR_S66ASTR_RP> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 14263 Feb 29 10:42 MC_H100ASTR_P69ASTR_S66ASTR_RP.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H88ASTR_P67ASTR_S63ASTR_RP> cp MC_H100ASTR_P69ASTR_S66ASTR_RP.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_H98ASTR_P69ASTR_S66ASTR_RP.txt MC_H100ASTR_P69ASTR_S66ASTR_RP.txt If there is a difference inform Eva of the result. If there is NO difference then no need to inform Eva. No new PACS script Do not notify Eva 12. Final Jboss Activities [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Wed Feb 29 09:02:59 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_H100ASTR_P69ASTR_S66ASTR_RP 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_H100ASTR_P69ASTR_S66ASTR_RP/ 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_H98ASTR_P69ASTR_S66ASTR_RP-120120 hcss.phs.timeEstimatorVersion= MC_H100ASTR_P69ASTR_S66ASTR_RP-120229 #hcss.phs.timeEstimatorVersion=MC_H97_P69_S66_CAL-120120 #hcss.phs.timeEstimatorVersion=MC_H99_P69_S66_CAL-120228 #MISSION CONFIG #hcss.ccm.mission.config = MC_H98ASTR_P69ASTR_S66ASTR_RP hcss.ccm.mission.config = MC_H100ASTR_P69ASTR_S66ASTR_RP #hcss.ccm.mission.config = MC_H97_P69_S66_CAL #hcss.ccm.mission.config = MC_H99_P69_S66_CAL #MARK DIRECTORIES #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_H100ASTR_P69ASTR_S66ASTR_RP #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H97_P69_S66_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H99_P69_S66_CAL herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 7207 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 ========================================================================= 11:01:00,711 INFO [Server] Starting JBoss (MX MicroKernel)... 11:01:00,711 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 11:01:00,712 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 11:01:00,712 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 11:01:00,712 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 11:01:00,712 INFO [Server] Patch URL: null 11:01:00,713 INFO [Server] Server Name: phs-operations 11:01:00,713 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 11:01:00,713 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 11:01:00,713 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 11:01:00,713 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 11:01:00,713 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 11:01:00,713 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 11:01:00,713 INFO [Server] Root Deployment Filename: jboss-service.xml 11:01:00,715 INFO [Server] Starting General Purpose Architecture (GPA)... 11:01:00,904 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 11:01:00,904 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 11:01:00,904 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 11:01:01,066 INFO [Server] Core system initialized 11:01:02,407 INFO [ServiceBindingManager] Initializing store 11:01:02,407 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 11:01:02,667 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.