PACS Cycle 38 update ASTR MC and HSpot 5.3 back-end update delivery 1. Delivery Note PACS Delivery note - 6th April 2011 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of the PACS RP calibration cycle#38 tar file onto the CVS server. 1. Delivery file & directory (a) OD tar file name : CYCLE038_PACS_FULL_2_20110406.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle038, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES 2. Mission Configurations (a) Does this delivery include a new Calibration mission configuration? YES, is also replaces our calibration MC #63. (b) Does this delivery include a new ASTR mission configuration? YES 3. Operations Issues (TC,HPSDB,SIAM,Real Time Science) (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? NO (c) ICC to add anything specific which HSC & MOC should be aware of This is only a mission configuration delivery that contains the new PACS astronomer backend for the unchopped spectroscopy bright-line mode to be released with HSPOT 5.3.1. The master SCR is: http://herschel.esac.esa.int/jira/browse/PHS-1633 Please acknowledge the receipt of the e-mail and the delivery. Best regards, Markus. Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE038_PACS_FULL_2_20110406.tar New MCs - MC P64ASTR 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 6 09:13:14 2011 from herl21.net4.lan HCSS Version: 6.0.2 PHS Version: 5.3.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account 3. What is the Mission Configuration Name going to be?? MC_H74ASTR_P64ASTR_S61ASTR_AO 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle33> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle33/HIFI> mkdir PACS_FULL_2 This LOG file has been placed in the /logs directory and given the name Cycle038_PACS_FULL_2.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the SPIRE & PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H74ASTR_P64ASTR_S61ASTR_AO folder. Next remove in the SPIRE & HIFI subfolders all files which were created when you ran the SPIRE duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H62ASTR_P58ASTR_S61ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> ls CYCLE028_SPIRE_FULL_1_0_20101108.tar SPIRE_harness_duration_summary_20101109_15h38m18s.log SPIRE_AOR_C028_61_CAL.aor SPIRE_harness_duration_summary_20101123_09h34m04s.log SPIRE_AOR_C028_61_ENG.aor SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv87_C028_61_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C028_61.txt SPIRE_Duration.txt HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H74ASTR_P60ASTR_S61ASTR_AO/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0031_C038_74_CUS_CAL.xml importall.sh* CYCLE038_HIFI_FULL_2_20110330.tar HIFI_MC_ASTR_A0031_C038_74_CUS.def Summary_durations.txt default-durations.dat HIFI_MC_ASTR_A0031_C038_74.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> rm Summary_durations.txt rm: remove regular file `Summary_durations.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0031_C038_74_CUS_CAL.xml importall.sh* CYCLE038_HIFI_FULL_2_20110330.tar HIFI_MC_ASTR_A0031_C038_74_CUS.def default-durations.dat HIFI_MC_ASTR_A0031_C038_74.txt 6(a) Download & Untar the HIFI delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/HIFI/PACS_FULL_2> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_2> cvs login Logging in to :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_2> cvs co develop/data/observingmodes/rp_cycles/cycle038/CYCLE038_PACS_FULL_2_20110406.tar U develop/data/observingmodes/rp_cycles/cycle038/CYCLE038_PACS_FULL_2_20110406.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_2> cp develop/data/observingmodes/rp_cycles/cycle038/CYCLE038_PACS_FULL_2_20110406.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_2> ls CYCLE038_PACS_FULL_2_20110406.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_2> tar -xvf CYCLE038_PACS_FULL_2_20110406.tar PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def PACS_Readme_C038_64.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_2> ls CYCLE038_PACS_FULL_2_20110406.tar PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml PACS_Readme_C038_64.txt develop/ PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_2> cp * /home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS> ls CYCLE038_PACS_FULL_2_20110406.tar PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml PACS_Readme_C038_64.txt 6(b) To import the new 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_H74ASTR_P64ASTR_S61ASTR_AO/PACS> Apr 6, 2011 11:32:14 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:32:15 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:32:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:32:16 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:32:16 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:32:16 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:32:16 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:32:16 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:32:16 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 6, 2011 11:32:27 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT PACS IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Apr 6, 2011 11:32:50 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:32:51 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:32:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:32:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:32:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:32:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:32:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:32:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:32:59 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Apr 6, 2011 11:33:17 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:33:18 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:33:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:33:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:33:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:33:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:33:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:33:18 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:33:23 AM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (Version 64.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS> cus -m "upload PACS_MC P64ASTR mission config" -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 6, 2011 11:34:31 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:34:32 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:34:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:34:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:34:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:34:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:34:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:34:33 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:34:58 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 6, 2011 11:34:58 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 6, 2011 11:34:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:34:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:34:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:34:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:34:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:34:58 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:34:58 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 6, 2011 11:35:09 AM 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: Add files from P63CAL delivery that will permit sanity checking... hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C038_64.txt CYCLE038_PACS_FULL_2_20110406.tar PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS_CAL.xml PACS_AOR_C038_63.aor PACS_MC_ASTR_OT1_2011-04-06A_C038_64_CUS.def Point duration script to latest HCSS version... (6.0.2) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C038_63.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/PACS> ls -ls total 11264 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 6 11:41 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 6 11:41 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 6 11:43 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 77 Apr 6 11:43 msgPacsCal_Spec_Chopped_Raster.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Apr 6 11:41 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Apr 6 11:43 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Apr 6 11:42 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Apr 6 11:42 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 6 11:43 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 6 11:41 tmp 4 -rw-r--r-- 1 hscphs2 herschel 585 Apr 6 11:41 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/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 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_H74ASTR_P64ASTR_S61ASTR_AO/PACS> missetup -addconfig MC_H74ASTR_P64ASTR_S61ASTR_AO Apr 6, 2011 11:50:19 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:50:19 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:50:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:50:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:50:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:50:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:50:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:50:20 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:50:20 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Apr 6, 2011 11:50:28 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H74ASTR_P64ASTR_S61ASTR_AO" 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_H74ASTR_P64ASTR_S61ASTR_AO/PACS> Apr 6, 2011 11:50:59 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:51:00 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:51:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:51:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:51:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:51:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:51:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:51:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:51:01 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 6, 2011 11:51:15 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H74ASTR_P64ASTR_S61ASTR_AO" Apr 6, 2011 11:51:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:51:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:51:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:51:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:51:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:51:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:51:31 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 6, 2011 11:51:48 AM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H74ASTR_P64ASTR_S61ASTR_AO Apr 6, 2011 11:51:55 AM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(b) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> Apr 6, 2011 11:52:54 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:52:55 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:52:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:52:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:52:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:52:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:52:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:52:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:52:56 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 6, 2011 11:53:03 AM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Apr 6, 2011 11:53:31 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:53:32 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:53:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:53:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:53:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:53:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:53:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:53:32 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:53:39 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Apr 6, 2011 11:54:00 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:54:00 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:54:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:54:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:54:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:54:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:54:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:54:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:54:05 AM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (H74_ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> cus -m "upload HIFI MC H74ASTR mission config" -import HIFI_MC_ASTR_A0031_C038_74_CUS.def -importcaltables HIFI_MC_ASTR_A0031_C038_74_CUS_CAL.xml Apr 6, 2011 11:54:53 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 11:54:54 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:54:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:55:09 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 6, 2011 11:55:09 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 11:55:10 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 6, 2011 11:55:15 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0031_C038_74_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by HIFI: HIFI_MC_ASTR_A0031_C038_74_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_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> ls -ls total 6692 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 2010 cus-defdur.sh* 3328 -rw-r--r-- 1 hscphs2 herschel 3399680 Mar 30 18:04 CYCLE038_HIFI_FULL_2_20110330.tar 32 -rw-r--r-- 1 hscphs2 herschel 29693 Mar 30 16:39 default-durations.dat 1408 -rw-r--r-- 1 hscphs2 herschel 1437567 Mar 30 16:39 HIFI_MC_ASTR_A0031_C038_74_CUS_CAL.xml 1880 -rw-r--r-- 1 hscphs2 herschel 1918485 Mar 30 16:39 HIFI_MC_ASTR_A0031_C038_74_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1366 Mar 30 16:41 HIFI_MC_ASTR_A0031_C038_74.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 2010 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29693 Apr 6 12:20 Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> diff default-durations.dat Summary_durations.txt Perfect! No differences. 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY In the Comment field, refer to HIFI MC H74ASTR 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_H74ASTR_P64ASTR_S61ASTR_AO/HIFI> Apr 6, 2011 12:21:47 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 12:21:48 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 12:21:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:21:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:21:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:21:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:21:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:21:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:21:49 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 6, 2011 12:22:16 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H74ASTR_P64ASTR_S61ASTR_AO" Apr 6, 2011 12:22:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:22:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:22:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:22:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:22:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:22:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:22:29 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 6, 2011 12:22:37 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H74ASTR_P64ASTR_S61ASTR_AO Apr 6, 2011 12:22:56 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H74ASTR_P64ASTR_S61ASTR_AO" Apr 6, 2011 12:22:59 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 Reset the OBDB/STPF properties 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_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> Apr 6, 2011 12:23:51 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 12:23:52 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 12:23:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:23:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:23: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 6, 2011 12:23:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:23:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:23:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:23:53 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 6, 2011 12:24:02 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_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Apr 6, 2011 12:24:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 12:24:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 12:24: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 6, 2011 12:24:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:24: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 6, 2011 12:24:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:24:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:24:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:24:31 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Apr 6, 2011 12:24:49 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 12:24:50 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 12:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:24:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:24:55 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_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> cus -m "upload SPIRE MC_61ASTR mission config" -import SPIRE_MC_ASTR_pv87_C028_61_CUS.def -importcaltables SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml Apr 6, 2011 12:25:36 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 12:25:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 12:25:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:25:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:25:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:25:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:25:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:25:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:25:53 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 6, 2011 12:25:53 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 6, 2011 12:25:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:25:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:25: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 6, 2011 12:25:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:25:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:25:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:25:53 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 6, 2011 12:25:56 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_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> ls -ls total 5120 2540 -rw-r--r-- 1 hscphs2 herschel 2590720 Nov 8 22:55 CYCLE028_SPIRE_FULL_1_0_20101108.tar 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 Apr 6 12:27 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 Apr 6 12:32 SPIRE_harness_duration_summary_20110406_12h32m16s.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_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110406_12h32m16s.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 S61ASTR 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_H74ASTR_P64ASTR_S61ASTR_AO/SPIRE> Apr 6, 2011 12:34:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 12:34:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 12:34:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:34:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:34:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:34:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:34:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:34:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:34:35 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 6, 2011 12:35:21 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H74ASTR_P64ASTR_S61ASTR_AO" Apr 6, 2011 12:35:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:35:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:35:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:35:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:35:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:35:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:35:34 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Apr 6, 2011 12:35:50 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H74ASTR_P64ASTR_S61ASTR_AO Apr 6, 2011 12:35:58 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_H74ASTR_P64ASTR_S61ASTR_AO [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Wed Apr 6 11:14:14 2011 from herl38.net4.lan HCSS Version: 6.0.2 PHS Version: 5.3.0 hscphs2@heropl02/home/hscphs2> propHandler & [1] 15509 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Apr 6, 2011 12:38:01 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Apr 6, 2011 12:38:02 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 6, 2011 12:38: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 6, 2011 12:38:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 6, 2011 12:38: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 6, 2011 12:38:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 6, 2011 12:38:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Apr 6, 2011 12:38:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Running CDH.getObsProgrammes() Apr 6, 2011 12:38:03 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Apr 6, 2011 12:38:03 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 30 Apr 6, 2011 12:38:03 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Apr 6, 2011 12:38:03 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H74ASTR_P64ASTR_S61ASTR_AO" Apr 6, 2011 12:38:07 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3929 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration : CONFIRMED!! 10. Export the HSpot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. CONFIRMED!! Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same as the Mission Confifguration: MC_H74ASTR_P64ASTR_S61ASTR_AO Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H74ASTR_P64ASTR_S61ASTR_AO Example of the last entry in the log: Apr 6, 2011 12:40:02 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H74ASTR_P64ASTR_S61ASTR_AO/HifiSScanProcLoadChopNoRefGen.prop Apr 6, 2011 12:40:02 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H74ASTR_P64ASTR_S61ASTR_AO/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H74ASTR_P64ASTR_S61ASTR_AO> ls *.prop > MC_H74ASTR_P64ASTR_S61ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H74ASTR_P64ASTR_S61ASTR_AO> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 14152 Apr 6 12:40 MC_H74ASTR_P64ASTR_S61ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H74ASTR_P64ASTR_S61ASTR_AO> cp MC_H74ASTR_P64ASTR_S61ASTR_AO.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_H74ASTR_P60ASTR_S61ASTR_AO.txt MC_H74ASTR_P64ASTR_S61ASTR_AO.txt 71a72 > PacsCal_PacsLineSpec_unChopBLGen.prop If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. One new PACS script Notify Eva & Jose 12. Final Jboss Activities [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Wed Apr 6 11:53:44 2011 from herl28.net4.lan herjbo02.esac.esa.int/home/hsc_phs> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 661 PHS: Astronomers instance 659 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the JBOSS : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H74ASTR_P64ASTR_S61ASTR_AO Copy HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P48ASTR_S55ASTR_RP> scp *.prop hsc_phs@herjbo02.esac.esa.int:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H74ASTR_P64ASTR_S61ASTR_AO/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit phs-operations.props & Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #MARK TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_H72ASTR_P60ASTR_S61ASTR_AO_110304 #hcss.phs.timeEstimatorVersion=MC_H74ASTR_P60ASTR_S61ASTR_AO_110331 hcss.phs.timeEstimatorVersion=MC_H74ASTR_P64ASTR_S61ASTR_AO_110406 #hcss.phs.timeEstimatorVersion=MC_H71_P62_S62_CAL-110315-BAD #hcss.phs.timeEstimatorVersion=MC_H73_P63_S62_CAL-1100331 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H72ASTR_P60ASTR_S61ASTR_AO #hcss.ccm.mission.config = MC_H74ASTR_P60ASTR_S61ASTR_AO hcss.ccm.mission.config = MC_H74ASTR_P64ASTR_S61ASTR_AO #hcss.ccm.mission.config = MC_H71_P62_S62_CAL #hcss.ccm.mission.config = MC_H73_P63_S62_CAL #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H72ASTR_P60ASTR_S61ASTR_AO #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H74ASTR_P60ASTR_S61ASTR_AO hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H74ASTR_P64ASTR_S61ASTR_AO #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H71_P62_S62_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H73_P63_S62_CAL Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 17086 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 ========================================================================= 13:34:36,676 INFO [Server] Starting JBoss (MX MicroKernel)... 13:34:36,677 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 13:34:36,677 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 13:34:36,677 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 13:34:36,677 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 13:34:36,678 INFO [Server] Patch URL: null 13:34:36,678 INFO [Server] Server Name: phs-operations 13:34:36,678 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 13:34:36,678 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 13:34:36,678 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 13:34:36,678 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 13:34:36,678 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 13:34:36,678 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 13:34:36,678 INFO [Server] Root Deployment Filename: jboss-service.xml 13:34:36,680 INFO [Server] Starting General Purpose Architecture (GPA)... 13:34:36,913 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 13:34:36,913 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 13:34:36,913 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 13:34:37,123 INFO [Server] Core system initialized 13:34:38,564 INFO [ServiceBindingManager] Initializing store 13:34:38,564 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 13:34:38,833 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.