HIFI Cycle 37 Cal delivery HIFI Delivery note - 2nd February 2011 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just uploaded the tar file containing the delivery of HIFI observations for cycle 334 onto the CVS server. 1. Delivery file, directory: a) OD tar file names: - CYCLE34_HIFI_FULL_1_20110202.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle034 2. Mission Configurations: a) Does this delivery include a new Calibration Mission configuration? Yes b) Does this delivery include a new Astro Mission configuration? No 3. Operations Issues a) Will any of these delivered observations generate a significant amount of Telecommands? No b) Do you wish to have these calibrations observations scheduled in the Real Time Science period of the DTCP? Not a requirement. c) ICC to add anything specific to this OD which HSC & MOC should be aware of: Instructions are in the Readme file. One important note is that two of the calibration AORs should be scheduled as early as possible, therefore during the first HIFI OD in that cycle. Please acknowledge receipt of the e-mail and the delivery. Best regards, Christophe Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE034_HIFI_FULL_1_20110202.tar (note wrong name in delivery note) (Note: Name given in delivery note is incorrect - checked on CVS server) New MC - MC H71_Cal 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 Mar 14 23:31:20 2011 from ssh.esac.esa.int HCSS Version: 6.0.2 PHS Version: 5.3.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal: PHS: Using BUILDNUM 534 & PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account Source the Environment before you proceed to step 3. hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v5.1.0 TAKE NOTE : If there is a newer HCSS software version in the otherSetups directory then source that new version. 3. What is the Mission Configuration Name going to be?? MC_H71_P62_S62_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle037_HIFI_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H71_P62_S62_CAL folder. Next remove in the subfolders all files which were created when you ran the HIFI, SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_AOR_C035_62.aor 2createOBSMODtable4RP.sh~* PACS_Duration_PACS_compare.txt CYCLE035_PACS_FULL_1_20110217.tar PACS_Duration_PACS.txt msgPacsCal_PacsLineSpec_unChopBL.txt PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml msgPacsCal_PacsRangeSpec_PV.txt PACS_MC_OT1_2011-02-17A_C035_62_CUS.def msgPacsEng_Pacs_EDAC_to_DMC_HK.txt PACS_Readme_C035_62.txt msgPacsPhoto.txt tmp msgPacsRangeSpec.txt tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> rm tmp* msg* PACS_Duration_PACS.txt rm: remove regular empty file `tmp'? y rm: remove regular empty file `tmpobsmode'? y rm: remove regular file `msgPacsCal_PacsLineSpec_unChopBL.txt'? y rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.txt'? y rm: remove regular file `msgPacsEng_Pacs_EDAC_to_DMC_HK.txt'? y rm: remove regular file `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_H71_P62_S62_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt 2createOBSMODtable4RP.sh~* PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml CYCLE035_PACS_FULL_1_20110217.tar PACS_MC_OT1_2011-02-17A_C035_62_CUS.def PACS_AOR_C035_62.aor PACS_Readme_C035_62.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> ls CYCLE035_SPIRE_FULL_1_0_20110214.tar SPIRE_harness_duration_summary_20110215_10h07m26s.log SPIRE_AOR_C035_62_CAL.aor SPIRE_harness_duration_summary_20110228_10h07m16s.log SPIRE_AOR_C035_62_ENG.aor SPIRE_harness_duration_summary_20110314_17h32m22s.log SPIRE_cus_scripts.txt SPIRE_MC_pv88_C035_62_CUS_CAL.xml SPIRE_CUS_THCP.py SPIRE_MC_pv88_C035_62_CUS.def SPIRE_Duration.txt SPIRE_Readme_C035_62.txt 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> setenv CVSROOT :pserver:dgalan@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS CVF down for migration to ESAC (new setenv above - tarball received by e-mail) Skip this... hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle37/HIFI/HIFI_FULL_1> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle034/CYCLE034_HIFI_FULL_1_20110202.tar U develop/data/observingmodes/rp_cycles/cycle034/CYCLE034_HIFI_FULL_1_20110202.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle034/CYCLE033_HIFI_FULL_1_20110120.tar U develop/data/observingmodes/rp_cycles/cycle034/CYCLE033_HIFI_FULL_1_20110120.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle034/CYCLE034_HIFI_FULL_1_20110202.tar . Re-join... hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle37/HIFI/HIFI_FULL_1> ls CYCLE037_HIFI_FULL_1_20110315.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle37/HIFI/HIFI_FULL_1> tar -xvf CYCLE037_HIFI_FULL_1_20110315.tar duration_cal.sh HIFI_AOR_C037_71.aor HIFI_DUR_C037_71.txt HIFI_MC_R079_FULL_71_0_CUS_CAL.xml HIFI_MC_R079_FULL_71_0_CUS.def HIFI_Readme_C037_71.txt HIFI_AOR_C037_72.aor hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle37/HIFI/HIFI_FULL_1> ls CYCLE037_HIFI_FULL_1_20110315.tar HIFI_AOR_C037_72.aor HIFI_MC_R079_FULL_71_0_CUS.def duration_cal.sh* HIFI_DUR_C037_71.txt HIFI_Readme_C037_71.txt HIFI_AOR_C037_71.aor HIFI_MC_R079_FULL_71_0_CUS_CAL.xml hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle37/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/HIFI/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/HIFI> ls CYCLE037_HIFI_FULL_1_20110315.tar HIFI_AOR_C037_72.aor HIFI_MC_R079_FULL_71_0_CUS.def duration_cal.sh* HIFI_DUR_C037_71.txt HIFI_Readme_C037_71.txt HIFI_AOR_C037_71.aor HIFI_MC_R079_FULL_71_0_CUS_CAL.xml 6(b) To import the old PACS delivery: #CUS #var.hcss.instrument = SPIRE var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> Mar 15, 2011 10:06:16 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 10:06:17 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 10:06:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:06:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:06:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:06:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:06:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:06:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:06:17 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Mar 15, 2011 10:06:33 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT PACS IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Mar 15, 2011 10:06:55 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 10:06:56 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 10:06:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:06:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:06:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:06:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:06:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:06:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:07:06 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Mar 15, 2011 10:07:53 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 10:07:54 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 10:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:07:59 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_MOC9_201003161700 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (Version 60.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> cus -m "upload PACS_MC_62CAL mission configuration" -import PACS_MC_OT1_2011-02-17A_C035_62_CUS.def -importcaltables PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml Mar 15, 2011 10:09:34 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 10:09:35 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 10:09:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:09:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:09:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:09:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:09:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:09:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:10:00 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Mar 15, 2011 10:10:00 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Mar 15, 2011 10:10:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:10:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:10:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:10:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:10:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:10:00 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:10:00 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 15, 2011 10:10:10 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_OT1_2011-02-17A_C035_62_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_OT1_2011-02-17A_C035_62_CUS_CAL.xml CONFIRMED!! 6(e) Run the duration script for the PACS instrument model: Open duration script (2createOBSMODtable4RP.sh) and point it to HCSS 6.0.0 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C035_62.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> ls -ls total 11436 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Mar 7 11:44 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Mar 7 11:44 2createOBSMODtable4RP.sh~* 5704 -rw-r--r-- 1 hscphs2 herschel 5826560 Feb 17 18:27 CYCLE035_PACS_FULL_1_20110217.tar 4 -rw-r--r-- 1 hscphs2 herschel 79 Mar 15 10:15 msgPacsCal_PacsLineSpec_unChopBL.txt 4 -rw-r--r-- 1 hscphs2 herschel 74 Mar 15 10:14 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Mar 15 10:13 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Mar 15 10:14 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Mar 15 10:14 msgPacsRangeSpec.txt 152 -rw-r--r-- 1 hscphs2 herschel 151189 Feb 17 18:07 PACS_AOR_C035_62.aor 4 -rw-r--r-- 1 hscphs2 herschel 1784 Feb 17 18:12 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 1784 Mar 15 10:15 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404163 Feb 17 12:01 PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml 5136 -rw-r--r-- 1 hscphs2 herschel 5245450 Feb 17 12:01 PACS_MC_OT1_2011-02-17A_C035_62_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 6819 Feb 17 18:24 PACS_Readme_C035_62.txt 4 -rw-r--r-- 1 hscphs2 herschel 1282 Mar 15 10:13 tmp 4 -rw-r--r-- 1 hscphs2 herschel 514 Mar 15 10:13 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS MC P62CAL TAKE NOTE : It is very important that you commit the delivery as defined above. Now create the MC in the database hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/PACS> missetup -addconfig MC_H71_P62_S62_CAL Mar 15, 2011 10:53:39 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 10:53:40 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 10:53:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:53:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:53:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:53:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:53:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:53:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:53:41 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Mar 15, 2011 10:54:09 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H71_P62_S62_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_H71_P62_S62_CAL/PACS> Mar 15, 2011 10:55:18 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 10:55:19 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 10:55:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:55:19 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:55:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:55:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:55:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:55:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:55:20 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Mar 15, 2011 10:55:35 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H71_P62_S62_CAL" Mar 15, 2011 10:55:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:55:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 10:55:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:55:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 10:55:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:55:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 10:55:59 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 15, 2011 10:56:05 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H71_P62_S62_CAL Mar 15, 2011 10:56:26 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(a) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle37/HIFI/HIFI_FULL_1> Mar 15, 2011 11:55:54 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 11:55:55 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 11:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 11:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 11:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 11:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 11:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 11:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 11:55:56 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Mar 15, 2011 11:56:07 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_H71_P62_S62_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Mar 15, 2011 12:06:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 12:06:41 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 12:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:06:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:06:54 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Mar 15, 2011 12:07:12 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 12:07:13 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 12:07:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:07:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:07:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:07:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:07:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:07:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:07:19 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (H71Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/HIFI> cus -m "upload HIFI MC71Cal mission config" -import HIFI_MC_R079_FULL_71_0_CUS.def -importcaltables HIFI_MC_R079_FULL_71_0_CUS_CAL.xml Mar 15, 2011 12:09:58 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 12:09:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 12:09:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:09:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:10:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:10:24 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Mar 15, 2011 12:10:24 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Mar 15, 2011 12:10:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:10:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:10:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:10:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:10:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:10:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:10:25 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 15, 2011 12:10:37 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R079_FULL_71_0_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_R079_FULL_71_0_CUS_CAL.xml CONFIRMED!! 7(e) Run the duration script for the HIFI instrument Run the duration script delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C037_71 next AOR file = HIFI_AOR_C037_71 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_Parameter_Scan_COP -- mode HifiEngSwitchonLO -- mode HifiPointModeDBS -- mode HifiPointModeFastDBS -- mode HifiPointModeFSwitch -- mode HifiPointModeFSwitchNoRef -- mode HifiPointModeLoadChop -- mode HifiPointModeLoadChopNoRef -- mode HifiPointModePositionSwitch -- mode HifiSScanModeDBS -- mode HifiSScanModeFastDBS -- mode HifiSScanModeFSwitch -- mode HifiSScanModeFSwitchNoRef -- mode HifiSScanModeLoadChop -- mode HifiSScanModeLoadChopNoRef Total duration of HifiEng_Chopper_FT2_COP with default parameters = 114 Total duration of HifiEng_Chopper_Response_time_COP with default parameters = 44 Total duration of HifiEng_Parameter_Scan_COP with default parameters = 770 Total duration of HifiEngSwitchonLO with default parameters = 405 Total duration of HifiPointModeDBS with default parameters = 159 Total duration of HifiPointModeFastDBS with default parameters = 147 Total duration of HifiPointModeFSwitch with default parameters = 182 Total duration of HifiPointModeFSwitchNoRef with default parameters = 158 Total duration of HifiPointModeLoadChop with default parameters = 149 Total duration of HifiPointModeLoadChopNoRef with default parameters = 125 Total duration of HifiPointModePositionSwitch with default parameters = 141 Total duration of HifiSScanModeDBS with default parameters = 392 Total duration of HifiSScanModeFastDBS with default parameters = 344 Total duration of HifiSScanModeFSwitch with default parameters = 510 Total duration of HifiSScanModeFSwitchNoRef with default parameters = 425 Total duration of HifiSScanModeLoadChop with default parameters = 360 Total duration of HifiSScanModeLoadChopNoRef with default parameters = 293 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/HIFI> diff HIFI_DUR_C037_71.txt summary_HIFI_AOR_C037_71.log No differences. 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY In the Comment field, refer to HIFI MC H71CAL 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_H71_P62_S62_CAL/HIFI> Feb 2, 2011 5:25:04 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:25:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:25:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 5:25:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 5:25:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 5:25:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 5:25:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 5:25:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 5:25:05 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Feb 2, 2011 5:25:16 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H71_P62_S62_CAL" Feb 2, 2011 5:25:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 5:25:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 5:25:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 5:25:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 5:25:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 5:25:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 5:25:27 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 2, 2011 5:26:19 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the Old SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the PACS instrument Import into the new Mission Configuration 8(a) Set Instrument Model = SPIRE #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> Feb 2, 2011 5:27:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:27:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:27:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 5:27:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 5:27:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 5:27:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 5:27:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 5:27:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 5:27:11 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Feb 2, 2011 5:27:46 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Mar 15, 2011 12:20:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 12:20:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 12:20:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:20:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:20:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:20:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:20:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:20:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:20:59 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Mar 15, 2011 12:21:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 12:21:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 12:21:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:21:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:21:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:21:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:21:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:21:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:21:44 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 62.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> cus -m "upload SPIRE MC_62Cal mission config" -import SPIRE_MC_pv88_C035_62_CUS.def -importcaltables SPIRE_MC_pv88_C035_62_CUS_CAL.xml Mar 15, 2011 12:23:30 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 12:23:31 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 12:23:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:23:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:23:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:23:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:23:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:23:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:23:49 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Mar 15, 2011 12:23:49 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Mar 15, 2011 12:23:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:23:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:23:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:23:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:23:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:23:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:23:50 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 15, 2011 12:24:03 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv88_C035_62_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_pv88_C035_62_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> ls -ls total 4924 2440 -rw-r--r-- 1 hscphs2 herschel 2488320 Feb 14 17:40 CYCLE035_SPIRE_FULL_1_0_20110214.tar 44 -rw-r--r-- 1 hscphs2 herschel 38179 Feb 14 17:28 SPIRE_AOR_C035_62_CAL.aor 8 -rw-r--r-- 1 hscphs2 herschel 6401 Feb 14 17:29 SPIRE_AOR_C035_62_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2023 Mar 15 12:24 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Feb 14 17:35 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5451 Feb 14 17:35 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Feb 15 10:07 SPIRE_harness_duration_summary_20110215_10h07m26s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Feb 28 10:07 SPIRE_harness_duration_summary_20110228_10h07m16s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Mar 14 17:32 SPIRE_harness_duration_summary_20110314_17h32m22s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Mar 15 12:29 SPIRE_harness_duration_summary_20110315_12h29m51s.log 276 -rw-r--r-- 1 hscphs2 herschel 278093 Feb 14 17:35 SPIRE_MC_pv88_C035_62_CUS_CAL.xml 2100 -rw-r--r-- 1 hscphs2 herschel 2140684 Feb 14 17:35 SPIRE_MC_pv88_C035_62_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5618 Feb 14 17:37 SPIRE_Readme_C035_62.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H71_P62_S62_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110315_12h29m51s.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 S62Cal. 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_H71_P62_S62_CAL/SPIRE> Mar 15, 2011 12:32:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 12:32:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 12:32:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:32:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:32:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:32:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:32:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:32:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:32:06 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Mar 15, 2011 12:32:20 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H71_P62_S62_CAL" Mar 15, 2011 12:32:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:32:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 12:32:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:32:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 12:32:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:32:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 12:32:34 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 15, 2011 12:32:48 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H71_P62_S62_CAL Mar 15, 2011 12:33:55 PM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. Date: Tue, 15 Mar 2011 12:31:00 +0100 [12:31:00 CET] From: Christophe Risacher Add c.risacher@sron.nl to my Address Book Netherlands To: mkidger@sciops.esa.intAdd mkidger@sciops.esa.int to my Address Book Cc: hscops@sciops.esa.intAdd hscops@sciops.esa.int to my Address Book, michael.olberg@chalmers.seAdd michael.olberg@chalmers.se to my Address Book, pmorris@ipac.caltech.eduAdd pmorris@ipac.caltech.edu to my Address Book, ossk@ph1.uni-koeln.deAdd ossk@ph1.uni-koeln.de to my Address Book, David.Teyssier@sciops.esa.intAdd David.Teyssier@sciops.esa.int to my Address Book, hifimps@sciops.esa.intAdd hifimps@sciops.esa.int to my Address Book, Russell Shipman Add russ@sron.nl to my Address Book Subject: Urgent: canceling HIFI MC 71 !! Hi Mark, We just discovered a very subtle hidden bug in the MC H71, just delivered, which can potentially corrupt the OBSW and all subsequent observations. It is something not noticed at first, but when running long enough a buffer gets overfloaded and corrupts the commanding. (HIFI-4005). Sorry we did not notice this earlier, but subsequent testing this morning showed the failure. (all appeared nominal at first). Please therefore, do not create a new MC H71. I will send you shortly enough the revised delivery, only containing the observations in A and C) in the readme file, which should be run with the previous MC H67. Sorry for the additional problems, Christophe ========================================================== Date: Tue, 15 Mar 2011 12:58:22 +0100 [12:58:22 CET] From: Christophe Risacher Add C.Risacher@sron.nl to my Address Book Netherlands To: mkidger@sciops.esa.intAdd mkidger@sciops.esa.int to my Address Book Cc: michael.olberg@chalmers.seAdd michael.olberg@chalmers.se to my Address Book, pmorris@ipac.caltech.eduAdd pmorris@ipac.caltech.edu to my Address Book, ossk@ph1.uni-koeln.deAdd ossk@ph1.uni-koeln.de to my Address Book, David.Teyssier@sciops.esa.intAdd David.Teyssier@sciops.esa.int to my Address Book, hifimps@sciops.esa.intAdd hifimps@sciops.esa.int to my Address Book, hscops@sciops.esa.intAdd hscops@sciops.esa.int to my Address Book, Russell Shipman Add russ@sron.nl to my Address Book Subject: Re: Urgent: canceling HIFI MC 71 !! Hi Mark, Okay, actually scheduling tests C) under H67 won't work. After discussing with David, the proposal is the following: 1) Complete the H71 preparation. 2) set to rejected all AORs under B in the readme file + the first one under C) ( HifiEngSwitchonLO_7b_SHORT). 3) Don't prepare the H72 AORs, those are cancelled (as B is cancelled). 4) Therefore the delivery should only include 2+11 AORs under H71. (Those are immune against the problem identified earlier). 5) No other AOR (eng or cal) should be used against H71. For the transition modes, ICU checks, always use the ASTR H72. 6) For the next weeks, until H73 is delivered in 2 weeks, nothing else than those 13 AORs should be using H71. If this sounds acceptable, this would be the way to go, Cheers, Christophe ============================================ 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_H71_P62_S62_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Mar 15 12:24:09 2011 from herl21.net4.lan HCSS Version: 6.0.2 PHS Version: 5.3.0 hscphs2@heropl02/home/hscphs2> Mar 15, 2011 2:15:45 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 15, 2011 2:15:45 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 15, 2011 2:15:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 2:15:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 15, 2011 2:15:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 2:15:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 15, 2011 2:15:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 15, 2011 2:15:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Running CDH.getObsProgrammes() Mar 15, 2011 2:15:46 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Mar 15, 2011 2:15:46 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 31 Mar 15, 2011 2:15:46 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Mar 15, 2011 2:15:46 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H71_P62_S62_CAL" Mar 15, 2011 2:15:51 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 4235 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration : CONFIRMED!! 10. Export the Hspot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. CONFIRMED!! Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same as the Mission Confifguration: Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H71_P62_S62_CAL Example of the last entry in the log: Mar 15, 2011 2:18:48 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H71_P62_S62_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Mar 15, 2011 2:18:48 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H71_P62_S62_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H71_P62_S62_CAL> ls *.prop > & MC_H71_P62_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H71_P62_S62_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18135 Mar 15 14:19 MC_H71_P62_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H71_P62_S62_CAL> cp MC_H71_P62_S62_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_H67_P62_S62_CAL.txt MC_H71_P62_S62_CAL.txt If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. No new HIFI script. Do not notify Eva & Jose 12. Final Jboss Activities Log into Jboss #2 [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Mon Mar 14 17:41:41 2011 from herl38.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 661 PHS: Astronomers instance 659 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the Test Jboss : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H71_P62_S62_CAL copied HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H71_P62_S62_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H71_P62_S62_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!! #MARK TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_H72ASTR_P60ASTR_S61ASTR_AO_110304 hcss.phs.timeEstimatorVersion=MC_H71_P62_S62_CAL-110315-BAD #hcss.phs.timeEstimatorVersion=MC_H67_P62_S62_CAL-1100218 #hcss.phs.timeEstimatorVersion=MC_H65_P61_S61_GYROTEST-110125 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H72ASTR_P60ASTR_S61ASTR_AO hcss.ccm.mission.config = MC_H71_P62_S62_CAL #hcss.ccm.mission.config = MC_H67_P62_S62_CAL #hcss.ccm.mission.config = MC_H65_P61_S61_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H72ASTR_P60ASTR_S61ASTR_AO hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H71_P62_S62_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H67_P62_S62_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H65_P61_S61_GYRO Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 11226 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 ========================================================================= 14:34:29,804 INFO [Server] Starting JBoss (MX MicroKernel)... 14:34:29,805 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 14:34:29,805 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 14:34:29,805 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 14:34:29,805 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 14:34:29,806 INFO [Server] Patch URL: null 14:34:29,806 INFO [Server] Server Name: phs-operations 14:34:29,806 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 14:34:29,808 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 14:34:29,808 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 14:34:29,808 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 14:34:29,808 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 14:34:29,809 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 14:34:29,809 INFO [Server] Root Deployment Filename: jboss-service.xml 14:34:29,810 INFO [Server] Starting General Purpose Architecture (GPA)... 14:34:30,035 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 14:34:30,035 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 14:34:30,035 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 14:34:30,354 INFO [Server] Core system initialized 14:34:31,778 INFO [ServiceBindingManager] Initializing store 14:34:31,778 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 14:34:32,046 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.