HIFI Cycle 40 Cal delivery HIFI Delivery note - 26th April 2011 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just delivered the CAL Mission Configuration for cycle 40, uploading the tar file containing the delivery of HIFI observations for cycle 40 onto the CVS server. 1. Delivery file, directory: a) OD tar file names: - CYCLE040_HIFI_FULL_1_20110426.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle040 2. Mission Configurations: a) Does this delivery include a new Calibration Mission configuration? Yes b) Does this delivery include a new Astro Mission configuration? No 3. Operations Issues a) Will any of these delivered observations generate a significant amount of Telecommands? No b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? Not a requirement. c) ICC to add anything specific to this OD which HSC & MOC should be aware of: Instructions are in the Readme file. This Mission Configuration need OBSW 6.5.3. Please acknowledge receipt of the e-mail and the delivery. Best regards, Max Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE040_HIFI_FULL_1_20110426.tar New MC - MC H77Cal 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Wed Apr 27 15:32:16 2011 from herl22.net4.lan HCSS Version: 6.1.0 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 3. What is the Mission Configuration Name going to be?? MC_H77_P64_S62_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle040_HIFI_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_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_H77_P64_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_H77_P64_S62_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H76ASTR_P64ASTR_S61ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS> ls 2createOBSMODtable4RP.sh* msgPacsLineSpec.txt PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml 2createOBSMODtable4RP.sh~* msgPacsPhoto.txt PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def CYCLE038_PACS_FULL_2_20110406.tar msgPacsRangeSpec.txt PACS_Readme_C038_64.txt msgPacsCal_PacsRangeSpec_PV.txt PACS_AOR_C038_63.aor tmp msgPacsCal_Spec_Chopped_Raster.txt PACS_Duration_PACS_compare.txt tmpobsmode msgPacsEng_Pacs_EDAC_to_DMC_HK.txt PACS_Duration_PACS.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS> rm tmp* msg* PACS_Duration_PACS.txt rm: remove regular file `tmp'? y rm: remove regular file `tmpobsmode'? y rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.txt'? y rm: remove regular file `msgPacsCal_Spec_Chopped_Raster.txt'? y rm: remove regular file `msgPacsEng_Pacs_EDAC_to_DMC_HK.txt'? y rm: remove regular file `msgPacsLineSpec.txt'? y rm: remove regular file `msgPacsPhoto.txt'? y rm: remove regular file `msgPacsRangeSpec.txt'? y rm: remove regular file `PACS_Duration_PACS.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt 2createOBSMODtable4RP.sh~* PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml CYCLE038_PACS_FULL_2_20110406.tar PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def PACS_AOR_C038_63.aor PACS_Readme_C038_64.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_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_Cycle40/HIFI> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/HIFI> 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_Cycle40/HIFI> cvs co develop/data/observingmodes/rp_cycles/cycle040/CYCLE040_HIFI_FULL_1_20110426.tar U develop/data/observingmodes/rp_cycles/cycle040/CYCLE040_HIFI_FULL_1_20110426.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/HIFI> cp develop/data/observingmodes/rp_cycles/cycle040/CYCLE040_HIFI_FULL_1_20110426.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/HIFI/HIFI_FULL_1> ls CYCLE040_HIFI_FULL_1_20110426.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/HIFI/HIFI_FULL_1> tar -xvf CYCLE040_HIFI_FULL_1_20110426.tar duration_cal.sh HIFI_AOR_C040_75.aor HIFI_AOR_C040_76.aor HIFI_AOR_C040_77.aor HIFI_DUR_C040_77.txt HIFI_Readme_C040_77.txt HIFI_MC_R083_FULL_77_0_CUS_CAL.xml HIFI_MC_R083_FULL_77_0_CUS.def hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/HIFI/HIFI_FULL_1> ls CYCLE040_HIFI_FULL_1_20110426.tar HIFI_AOR_C040_76.aor HIFI_MC_R083_FULL_77_0_CUS.def develop/ HIFI_AOR_C040_77.aor HIFI_Readme_C040_77.txt duration_cal.sh* HIFI_DUR_C040_77.txt HIFI_AOR_C040_75.aor HIFI_MC_R083_FULL_77_0_CUS_CAL.xml hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle40/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/HIFI/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/HIFI> ls CYCLE040_HIFI_FULL_1_20110426.tar HIFI_AOR_C040_76.aor HIFI_MC_R083_FULL_77_0_CUS_CAL.xml duration_cal.sh* HIFI_AOR_C040_77.aor HIFI_MC_R083_FULL_77_0_CUS.def HIFI_AOR_C040_75.aor HIFI_DUR_C040_77.txt HIFI_Readme_C040_77.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_H77_P64_S62_CAL/PACS> Apr 27, 2011 5:12:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:12:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:12:19 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 27, 2011 5:12:59 PM 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_H77_P64_S62_CAL/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Apr 27, 2011 5:13:24 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:13:24 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:13:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:13:34 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Apr 27, 2011 5:13:41 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:13:42 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:13:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:13:47 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!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (Version 62.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS> cus -m "upload PACS_MC_64ASTR mission configuration as CAL" -import PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def -importcaltables PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml Apr 27, 2011 5:14:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:14:43 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:14:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 27, 2011 5:15:14 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:15:14 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 27, 2011 5:15:31 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT1_2011-04-06A_C038_64_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_OT1_2011-04-06A_C038_64_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.1.0 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C038_63.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/PACS> ls -ls total 11264 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 13 15:52 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 13 15:52 2createOBSMODtable4RP.sh~* 5544 -rw-r--r-- 1 hscphs2 herschel 5662720 Apr 6 10:47 CYCLE038_PACS_FULL_2_20110406.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Apr 27 17:18 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 77 Apr 27 17:18 msgPacsCal_Spec_Chopped_Raster.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Apr 27 17:16 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Apr 27 17:18 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Apr 27 17:18 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Apr 27 17:18 msgPacsRangeSpec.txt 144 -rw-r--r-- 1 hscphs2 herschel 139521 Mar 29 15:17 PACS_AOR_C038_63.aor 4 -rw-r--r-- 1 hscphs2 herschel 2394 Mar 29 15:21 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2394 Apr 27 17:18 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404163 Apr 6 10:39 PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml 5136 -rw-r--r-- 1 hscphs2 herschel 5245792 Apr 6 10:39 PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 2756 Apr 6 10:43 PACS_Readme_C038_64.txt 4 -rw-r--r-- 1 hscphs2 herschel 1437 Apr 27 17:16 tmp 4 -rw-r--r-- 1 hscphs2 herschel 585 Apr 27 17:16 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_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 P64ASTR as CAL 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_H77_P64_S62_CAL/PACS> missetup -addconfig MC_H77_P64_S62_CAL Apr 27, 2011 5:21:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:21:57 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:21:58 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Apr 27, 2011 5:22:25 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H77_P64_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_H77_P64_S62_CAL/PACS> Apr 27, 2011 5:24:03 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:24:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:24:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:24:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:24:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:24:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:24:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:24:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:24:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:24:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:24:05 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 27, 2011 5:24:38 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H77_P64_S62_CAL" Apr 27, 2011 5:24:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:24:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:24:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:24:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:24:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:24:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:24:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:24:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:24:58 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 27, 2011 5:25:05 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H77_P64_S62_CAL Apr 27, 2011 5:25:16 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the new HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(a) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/HIFI> Apr 27, 2011 5:27:27 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:27:28 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:27:28 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 27, 2011 5:27:43 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Apr 27, 2011 5:28:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:28:11 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:28:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:28:22 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Apr 27, 2011 5:28:45 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:28:45 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:28:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:28:51 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 (H77Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/HIFI> cus -m "upload HIFI MC77Cal mission config" -import HIFI_MC_R083_FULL_77_0_CUS.def -importcaltables HIFI_MC_R083_FULL_77_0_CUS_CAL.xml Apr 27, 2011 5:31:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:31:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:31:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 27, 2011 5:31:26 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:31:26 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 27, 2011 5:31:33 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R083_FULL_77_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_R083_FULL_77_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_H77_P64_S62_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C040_77 next AOR file = HIFI_AOR_C040_77 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_Diplexer_calibration_vs_D2_COP -- mode HifiEng_Parameter_Scan_COP -- mode HifiEngSwitchonLO -- mode HifiSScanProcFastDBS 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_Diplexer_calibration_vs_D2_COP with default parameters = 5099 Total duration of HifiEng_Parameter_Scan_COP with default parameters = 921 Total duration of HifiEngSwitchonLO with default parameters = 428 Total duration of HifiSScanProcFastDBS with default parameters = 344 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/HIFI> diff HIFI_DUR_C040_77.txt summary_HIFI_AOR_C040_77.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 H77CAL 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_H77_P64_S62_CAL/HIFI> Apr 27, 2011 5:40:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:40:24 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:40:24 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 27, 2011 5:40:37 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H77_P64_S62_CAL" Apr 27, 2011 5:40:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:40:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:40:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:40:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:40:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:40:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:40:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:40:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:40:53 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 27, 2011 5:41:04 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H77_P64_S62_CAL Apr 27, 2011 5:41:20 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_H77_P64_S62_CAL/SPIRE> Apr 27, 2011 5:42:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:42:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:42:08 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 27, 2011 5:42:43 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_H77_P64_S62_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Apr 27, 2011 5:43:12 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:43:13 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:43:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:43:21 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_S62_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Apr 27, 2011 5:43:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:43:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:43:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:43:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:43:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:43:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:43:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:43:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:43:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:43:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:43:36 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_H77_P64_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 Apr 27, 2011 5:44:30 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:44:31 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:44:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:44:47 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 27, 2011 5:44:47 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:44:48 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 27, 2011 5:44:52 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_H77_P64_S62_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H77_P64_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 Apr 27 17:46 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 Apr 27 17:51 SPIRE_harness_duration_summary_20110427_17h51m21s.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_H77_P64_S62_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110427_17h51m21s.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_H77_P64_S62_CAL/SPIRE> Apr 27, 2011 5:54:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 5:54:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:54:31 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 27, 2011 5:54:47 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H77_P64_S62_CAL" Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 5:55:02 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 27, 2011 5:55:19 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H77_P64_S62_CAL Apr 27, 2011 5:55:26 PM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. 9.Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophandler to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H77_P64_S62_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Wed Apr 27 16:52:22 2011 from herl38.net4.lan HCSS Version: 6.1.0 PHS Version: 5.3.0 hscphs2@heropl02/home/hscphs2> Apr 27, 2011 6:02:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 27, 2011 6:02:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Apr 27, 2011 6:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int Running CDH.getObsProgrammes() Apr 27, 2011 6:02:41 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Apr 27, 2011 6:02:43 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 2153 Apr 27, 2011 6:02:43 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Apr 27, 2011 6:02:43 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H77_P64_S62_CAL" Apr 27, 2011 6:02:47 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 4207 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_H77_P64_S62_CAL Example of the last entry in the log: Apr 27, 2011 6:05:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H77_P64_S62_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Apr 27, 2011 6:05:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H77_P64_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_H77_P64_S62_CAL> ls *.prop > & MC_H77_P64_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H77_P64_S62_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18135 Apr 27 18:05 MC_H77_P64_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H77_P64_S62_CAL> cp MC_H77_P64_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_H75_P64_S62_CAL.txt MC_H77_P64_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: Wed Apr 27 14:48:06 2011 from herl28.net4.lan herjbo02.esac.esa.int/tmp> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 664 PHS: Astronomers instance 664 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the Operations Jboss : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H77_P64_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_H77_P64_S62_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H77_P64_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_H76ASTR_P64ASTR_S61ASTR_RP_110413 hcss.phs.timeEstimatorVersion=MC_H77_P64_S62_CAL-110427 #hcss.phs.timeEstimatorVersion=MC_H73_P65_S62_GYRO-110408 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H76ASTR_P64ASTR_S61ASTR_RP hcss.ccm.mission.config = MC_H77_P64_S62_CAL #hcss.ccm.mission.config = MC_H73_P65_S62_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H76ASTR_P64ASTR_S61ASTR_RP hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H77_P64_S62_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H73_P65_S62_GYRO Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 18522 herjbo02.esac.esa.int/home/hsc_phs/.hcss> ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /herschel/software/phs/jboss/jboss JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar ========================================================================= 18:13:01,256 INFO [Server] Starting JBoss (MX MicroKernel)... 18:13:01,260 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 18:13:01,261 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 18:13:01,261 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 18:13:01,261 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 18:13:01,261 INFO [Server] Patch URL: null 18:13:01,261 INFO [Server] Server Name: phs-operations 18:13:01,261 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 18:13:01,262 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 18:13:01,262 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 18:13:01,262 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 18:13:01,262 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 18:13:01,262 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 18:13:01,262 INFO [Server] Root Deployment Filename: jboss-service.xml 18:13:01,263 INFO [Server] Starting General Purpose Architecture (GPA)... 18:13:01,716 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 18:13:01,716 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 18:13:01,716 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 18:13:01,982 INFO [Server] Core system initialized 18:13:03,869 INFO [ServiceBindingManager] Initializing store 18:13:03,869 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 18:13:04,228 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.