HIFI Cycle 34 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 H67_Cal 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 5.1.0 (Always use the most recent HCSS Software version) PHS SOFTWARE = 5.1.4_PHS (Always use the most recent PHS Software version) Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal_herjbo02 : 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_H67_P60_S61_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 Cycle034_HIFI_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_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_H67_P60_S61_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_H67_P60_S61_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H64ASTR_P60ASTR_S61ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/PACS> ls 2createOBSMODtable4RP.sh* msgPacsRangeSpec.txt 2createOBSMODtable4RP.sh~* PACS_AOR_C030_60.aor CYCLE030_PACS_FULL_1_20101207.tar PACS_Duration_PACS_compare.txt importall.sh* PACS_Duration_PACS.txt ls PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS_CAL.xml msgPacsCal_PacsPhotoDACSlowScan.txt PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS.def msgPacsCal_PacsRangeSpec_PV.txt PACS_Readme_C030_60.txt msgPacsEng_Pacs_EDAC_to_DMC_HK.txt tmp msgPacsLineSpec.txt tmpobsmode msgPacsPhoto.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_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_PacsPhotoDACSlowScan.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 `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_H67_P60_S61_CAL/PACS> ls 2createOBSMODtable4RP.sh* importall.sh* PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS_CAL.xml 2createOBSMODtable4RP.sh~* PACS_AOR_C030_60.aor PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS.def CYCLE030_PACS_FULL_1_20101207.tar PACS_Duration_PACS_compare.txt PACS_Readme_C030_60.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H64ASTR_P60ASTR_S61ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/SPIRE> ls SPIRE_AOR_C028_61_CAL.aor SPIRE_harness_duration_summary_20101123_09h34m04s.log SPIRE_AOR_C028_61_ENG.aor SPIRE_harness_duration_summary_20101209_12h19m27s.log SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv87_C028_61_CUS.def SPIRE_Duration.txt SPIRE_Readme_C028_61.txt SPIRE_harness_duration_summary_20101109_15h38m18s.log 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:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/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 . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> ls CYCLE034_HIFI_FULL_1_20110202.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> tar -xvf CYCLE034_HIFI_FULL_1_20110202.tar duration_cal.sh HIFI_AOR_C034_67.aor HIFI_DUR_C034_67.txt HIFI_MC_R076_FULL_67_0_CUS_CAL.xml HIFI_MC_R076_FULL_67_0_CUS.def HIFI_Readme_C034_67.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> ls CYCLE034_HIFI_FULL_1_20110202.tar HIFI_AOR_C034_67.aor HIFI_MC_R076_FULL_67_0_CUS.def develop/ HIFI_DUR_C034_67.txt HIFI_Readme_C034_67.txt duration_cal.sh* HIFI_MC_R076_FULL_67_0_CUS_CAL.xml hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle34/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/HIFI> ls CYCLE034_HIFI_FULL_1_20110202.tar HIFI_DUR_C034_67.txt HIFI_Readme_C034_67.txt duration_cal.sh* HIFI_MC_R076_FULL_67_0_CUS_CAL.xml HIFI_AOR_C034_67.aor HIFI_MC_R076_FULL_67_0_CUS.def 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_H67_P60_S61_CAL/PACS> Feb 2, 2011 4:43:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 4:43:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 4:43:22 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 4:43:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 4:43:22 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 4:43:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 4:43:23 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 4:43:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 4:43:23 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 2, 2011 4:43:33 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_H67_P60_S61_CAL/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Feb 2, 2011 4:44:37 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 4:44:38 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 4:44:38 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 4:44:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 4:44:38 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 4:44:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 4:44:38 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 4:44:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 4:44:45 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Feb 2, 2011 4:45:04 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 4:45:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 4:45: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 4:45: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 4:45: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 4:45: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 4:45: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 4:45: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 4:45:08 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 60.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/PACS> cus -m "upload PACS_MC_60ASTR mission configuration as Cal" -import PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS.def -importcaltables PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS_CAL.xml Feb 2, 2011 4:46:26 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 4:46:27 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 4:46: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 4:46: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 4:46: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 4:46: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 4:46: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 4:46: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 4:46:48 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Feb 2, 2011 4:46:48 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Feb 2, 2011 4:46:48 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 4:46:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 2, 2011 4:46:48 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 4:46:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 2, 2011 4:46:49 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 4:46:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 2, 2011 4:46:49 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 2, 2011 4:46:54 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT1_2010-12-07C_C030_60_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_2010-10-22A_C027_58_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 5.1.0 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C030_60.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/PACS> ls -ls total 11304 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Dec 9 11:07 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1539 Dec 9 11:07 2createOBSMODtable4RP.sh~* 5632 -rw-r--r-- 1 hscphs2 herschel 5754880 Dec 7 14:50 CYCLE030_PACS_FULL_1_20101207.tar 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 2010 importall.sh* 4 -rw-r--r-- 1 hscphs2 herschel 77 Feb 2 16:48 msgPacsCal_PacsPhotoDACSlowScan.txt 4 -rw-r--r-- 1 hscphs2 herschel 74 Feb 2 16:49 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Feb 2 16:49 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Feb 2 16:49 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Feb 2 16:48 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Feb 2 16:49 msgPacsRangeSpec.txt 144 -rw-r--r-- 1 hscphs2 herschel 142976 Dec 7 14:35 PACS_AOR_C030_60.aor 4 -rw-r--r-- 1 hscphs2 herschel 1824 Dec 7 14:42 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 1824 Feb 2 16:49 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404088 Dec 7 14:24 PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS_CAL.xml 5080 -rw-r--r-- 1 hscphs2 herschel 5186062 Dec 7 14:24 PACS_MC_ASTR_OT1_2010-12-07C_C030_60_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 6230 Dec 7 14:47 PACS_Readme_C030_60.txt 4 -rw-r--r-- 1 hscphs2 herschel 1148 Feb 2 16:48 tmp 4 -rw-r--r-- 1 hscphs2 herschel 458 Feb 2 16:48 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_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 P60ASTR as CAL (rollback from GYRO-test MC) 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_H67_P60_S61_CAL/PACS> missetup -addconfig MC_H67_P60_S61_CAL Feb 2, 2011 5:01:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:01:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:01:03 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:01:03 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:01:03 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:01:03 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:01:03 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:01:03 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:01:04 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Feb 2, 2011 5:01:06 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H67_P60_S61_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_H67_P60_S61_CAL/PACS> Feb 2, 2011 5:01:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:01:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:01:30 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:01:30 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:01:30 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:01:30 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:01:30 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:01:30 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:01:30 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 2, 2011 5:01:48 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P60_S61_CAL" Feb 2, 2011 5:02:00 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:02:00 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:02:00 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:02:00 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:02:00 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:02:00 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:02:00 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 2, 2011 5:02:15 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_H67_P60_S61_CAL/HIFI> Feb 2, 2011 5:04:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:04:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:04:41 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:04:41 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:04:41 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:04:41 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:04:41 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:04:41 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:04:41 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Feb 2, 2011 5:05:02 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_H67_P60_S61_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Feb 2, 2011 5:10:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:10:11 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:10: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:10: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:10: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:10: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:10: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:10: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:10:14 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Feb 2, 2011 5:10:39 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:10:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:10:39 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:10:39 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:10:39 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:10:40 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:10:40 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:10:40 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:10:42 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 (H67Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/HIFI> cus -m "upload HIFI MC67Cal mission config" -import HIFI_MC_R076_FULL_67_0_CUS.def -importcaltables HIFI_MC_R076_FULL_67_0_CUS_CAL.xml Feb 2, 2011 5:14:59 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:15:00 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:15:00 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:15:00 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:15:00 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:15:00 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:15:00 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:15:00 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:15:19 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Feb 2, 2011 5:15:19 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Feb 2, 2011 5:15:19 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:15:19 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:15:19 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:15:19 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:15:19 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:15:19 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:15:19 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 2, 2011 5:15:24 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R076_FULL_67_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_R076_FULL_67_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_H67_P60_S61_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C034_67 next AOR file = HIFI_AOR_C034_67 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- 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 HifiSScanModeDBS with default parameters = 386 Total duration of HifiSScanModeFastDBS with default parameters = 338 Total duration of HifiSScanModeFSwitch with default parameters = 500 Total duration of HifiSScanModeFSwitchNoRef with default parameters = 417 Total duration of HifiSScanModeLoadChop with default parameters = 350 Total duration of HifiSScanModeLoadChopNoRef with default parameters = 285 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/HIFI> ls -ls total 11400 5692 -rw-r--r-- 1 hscphs2 herschel 5816320 Feb 2 10:36 CYCLE034_HIFI_FULL_1_20110202.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Feb 2 10:25 duration_cal.sh* 40 -rw-r--r-- 1 hscphs2 herschel 34893 Feb 1 17:38 HIFI_AOR_C034_67.aor 4 -rw-r--r-- 1 hscphs2 herschel 584 Feb 2 10:29 HIFI_DUR_C034_67.txt 2300 -rw-r--r-- 1 hscphs2 herschel 2344567 Feb 2 10:31 HIFI_MC_R076_FULL_67_0_CUS_CAL.xml 3352 -rw-r--r-- 1 hscphs2 herschel 3423201 Feb 2 10:31 HIFI_MC_R076_FULL_67_0_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 2672 Feb 2 10:34 HIFI_Readme_C034_67.txt 4 -rw-r--r-- 1 hscphs2 herschel 584 Feb 2 17:22 summary_HIFI_AOR_C034_67.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/HIFI> diff HIFI_DUR_C034_67.txt summary_HIFI_AOR_C034_67.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 H67CAL 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_H67_P60_S61_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_H67_P60_S61_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_H67_P60_S61_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_H67_P60_S61_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Feb 2, 2011 5:28:17 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:28:18 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:28:18 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:28:18 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:28:18 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:28:18 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:28:18 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:28:18 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:28:23 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Feb 2, 2011 5:28:45 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:28:46 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 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 Feb 2, 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 Feb 2, 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 Feb 2, 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 Feb 2, 2011 5:28:46 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:28:46 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:28:49 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 61.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/SPIRE> cus -m "upload SPIRE MC_61ASTR mission config as CAL" -import SPIRE_MC_ASTR_pv87_C028_61_CUS.def -importcaltables SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml Feb 2, 2011 5:30:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:30:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:30:22 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:30:22 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:30:22 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:30:22 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:30:22 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:30:23 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:30:34 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Feb 2, 2011 5:30:34 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Feb 2, 2011 5:30:34 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:30:34 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:30:34 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:30:34 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:30:34 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:30:34 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:30:34 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 2, 2011 5:30:37 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by SPIRE: SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/SPIRE> ls -ls total 2588 92 -rw-r--r-- 1 hscphs2 herschel 88159 Nov 8 22:01 SPIRE_AOR_C028_61_CAL.aor 60 -rw-r--r-- 1 hscphs2 herschel 56528 Nov 8 22:02 SPIRE_AOR_C028_61_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2023 Feb 2 17:31 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Nov 8 22:47 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5451 Nov 8 22:47 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Nov 9 15:38 SPIRE_harness_duration_summary_20101109_15h38m18s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Nov 23 09:34 SPIRE_harness_duration_summary_20101123_09h34m04s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Dec 9 12:19 SPIRE_harness_duration_summary_20101209_12h19m27s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Feb 2 17:34 SPIRE_harness_duration_summary_20110202_17h34m51s.log 276 -rw-r--r-- 1 hscphs2 herschel 276744 Nov 8 22:48 SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml 2100 -rw-r--r-- 1 hscphs2 herschel 2140168 Nov 8 22:48 SPIRE_MC_ASTR_pv87_C028_61_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8934 Nov 8 22:50 SPIRE_Readme_C028_61.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P60_S61_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110202_17h34m51s.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 S60ASTR as CAL. 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_H67_P60_S61_CAL/SPIRE> Feb 2, 2011 5:37:16 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:37:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:37:17 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:37:17 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:37:17 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:37:17 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:37:17 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:37:17 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:37:17 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Feb 2, 2011 5:37:32 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P60_S61_CAL" Feb 2, 2011 5:37:41 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:37:41 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:37:41 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:37:41 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:37:42 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:37:42 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:37:42 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 2, 2011 5:38:08 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P60_S61_CAL" Feb 2, 2011 5:38:11 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_H67_P60_S61_CAL Source the PHS Environment for 5.1.4_phs hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v5.1.4_phs hscphs2@heropl02/home/hscphs2/otherSetups> Feb 2, 2011 5:40:30 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 2, 2011 5:40:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 2, 2011 5:40:31 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:40:31 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:40:31 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:40:31 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:40:31 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:40:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Running CDH.getObsProgrammes() Feb 2, 2011 5:40:31 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Feb 2, 2011 5:40:31 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 29 Feb 2, 2011 5:40:31 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Feb 2, 2011 5:40:31 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P60_S61_CAL" Feb 2, 2011 5:40:34 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3075 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_H67_P60_S61_CAL Example of the last entry in the log: Feb 2, 2011 5:43:08 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H67_P60_S61_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Feb 2, 2011 5:43:08 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H67_P60_S61_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P60_S61_CAL> ls *.prop > & MC_H67_P60_S61_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P60_S61_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18097 Feb 2 17:43 MC_H67_P60_S61_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P60_S61_CAL> cp MC_H67_P60_S61_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_H65_P60_S61_CAL.txt MC_H67_P60_S61_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 herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 650 PHS: Astronomers instance 650 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 Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H67_P60_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_H67_P60_S61_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H67_P60_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_H66ASTR_P60ASTR_S61ASTR_RP_110121 hcss.phs.timeEstimatorVersion=MC_H67_P60_S61_CAL-1100202 #hcss.phs.timeEstimatorVersion=MC_H65_P61_S61_GYROTEST-110125 #hcss.ccm.mission.config = MC_H66ASTR_P60ASTR_S61ASTR_RP hcss.ccm.mission.config = MC_H67_P60_S61_CAL #hcss.ccm.mission.config = MC_H65_P61_S61_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H66ASTR_P60ASTR_S61ASTR_RP hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H67_P60_S61_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> startJbossPhsOperations Starting instance phs-operations [1] 19788 [1] + Running kedit phs-operations.props herjbo02.esac.esa.int/home/hsc_phs> ========================================================================= 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:08:39,332 INFO [Server] Starting JBoss (MX MicroKernel)... 18:08:39,332 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 18:08:39,333 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 18:08:39,333 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 18:08:39,333 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 18:08:39,333 INFO [Server] Patch URL: null 18:08:39,333 INFO [Server] Server Name: phs-operations 18:08:39,333 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 18:08:39,333 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 18:08:39,334 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 18:08:39,334 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 18:08:39,334 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 18:08:39,334 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 18:08:39,334 INFO [Server] Root Deployment Filename: jboss-service.xml 18:08:39,335 INFO [Server] Starting General Purpose Architecture (GPA)... 18:08:39,603 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 18:08:39,603 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 18:08:39,603 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 18:08:41,461 INFO [Server] Core system initialized 18:08:43,462 INFO [ServiceBindingManager] Initializing store 18:08:43,462 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 18:08:43,724 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.