HSC-PROC-UPLC-0004 : Standard Mission Config Template 1. Delivery Notes (a) SPIRE Delivery Note 4th August 09 Dear Colleagues of the HSC Ops Group, This e-mail is to notify you that I have just uploaded the SPIRE PV OD0086 tar file (OD0086_SPIRE_FULL_1_20090804.tar) onto the CVS server under develop/data/observingmodes/hscpv/od086. CVS version for these files = number (rev.) 1.1. The contents in the tar files are according to the HSC-ICC Interactions Document, and Larry's latest update. Please note, this delivery (not) contains a new MC. SPIRE_MC_pv32_FULL_19_0_CUS.def SPIRE_MC_pv32_FULL_19_0_CUS_CAL.xml Please see the extra info in section 10 in the readme. Please acknowledge the receipt of this delivery to us. Best regards, Sarah -- Take Note of the Tar File & the New MC name (for MPS email and for steps below) OD0086_SPIRE_FULL_1_20090804.tar new Mission Configuration (Version 14.0) 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 1.0.3 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 If the Environment has not yet been sourced then source it!! hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_1.0.3 setHcssExtLibs_csh:INFO:Variable HCSS_DIR set to [/herschel/software/hcss/hcss_1.0.3/hcss-apps] setHcssExtLibs_csh:INFO:Start setting up variables for HCSS #129 reference platform v8.4 setHcssExtLibs_csh:INFO:Your environment was already setup for HCSS_129 setHcssExtLibs_csh:INFO:Note that you can use the flag 'overwrite' to force this setup setHcssExtLibs_csh:WARNING:NO CHANGES made to your environment ... exit 0 3. What is the New Mission Configuration Name going to be?? Go to the mission_config directory and do an ls -ltr to see what is the last Mission Configuration generated. Take note also of the last email sent to the MPS group which contains the name and confirm it is the same name. Last Mission Config = MC_H21_P13_S18_PV SPIRE are delivering a new MC (#19) so the new Mission Configuration name shall be MC_H21_P14_S19_PV 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) Make the directory MC_H21_P14_S19_PV in the /icchsc/mission_config directory. Within this directory create the subdirectories : SPIRE, PACS, HIFI & logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV> ls HIFI/ logs/ PACS/ SPIRE/ This LOG file should be placed in the /logs directory and given the name MC_H21_P14_S18_PV.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV> ls HIFI/ logs/ PACS/ SPIRE/ Make also the delivery directory & subdirectories. If the tar file is called OD0086_SPIRE_FULL_1_20090804.tar Then you create a directory in /home/hscphs2/icchsc/delivery called OD0084. Within this directory you create SPIRE/SPIRE_FULL_1 subdirectories. Also create in this OD0086 directory a log file directory where the BASIC TEMPLATE Log file shall be placed. hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086> ls logs/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086> mkdir SPIRE/SPIRE_FULL_1 hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086> ls logs/ PACS/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086> ls SPIRE SPIRE_FULL_1/ 5. Copy across the contents of the HIFI & PACS ICC directories from a previous mission_config subdirectory. Remove any "tmp" files created the last time you ran the duration scripts on those files. As the last Mission Configuration was called MC_H21_P14_S18_PV then go to that directory and copy across the contents of the SPIRE & HIFI subdirectories into the equivalent subdirectories of the MC_H20_P14_S18_PV folder. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S18_PV/HIFI> cp *.* /home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/HIFI/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S18_PV/PACS> cp *.* /home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS/ Next remove in the PACS & HIFI subfolders all files which were created when you ran the HIFI & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. OK 6.Steps to Import the new SPIRE Instrument model into a new MC a.Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) b.Set the Instrument Model & check with CUSGUI c.Clean the CUS & Cal tables from the instrument model d.Import the new Instrument Cus & Cal into the DB e.GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. f.If Durations are OK then COMMIT the Delivery with CUSGUI g.Create the new Mission Configuration name in the DB h.Import the New HIFI Instrument Model into the Mission Configuration. 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/HIFI/HIFI_FULL_3> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/HIFI/HIFI_FULL_3> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/HIFI/HIFI_FULL_3> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/SPIRE/SPIRE_FULL_1> cvs co develop/data/observingmodes/hscpv/od086/OD0086_SPIRE_FULL_1_20090804.tar U develop/data/observingmodes/hscpv/od086/OD0086_SPIRE_FULL_1_20090804.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086> cd SPIRE/SPIRE_FULL_1/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/SPIRE/SPIRE_FULL_1> cp ../../develop/data/observingmodes/hscpv/od086/OD0086_SPIRE_FULL_1_090804.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/SPIRE/SPIRE_FULL_1> ls develop/ OD0086_SPIRE_FULL_1_20090804.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/SPIRE/SPIRE_FULL_1> tar -xvf OD0086_SPIRE_FULL_1_20090804.tar SPIRE_MC_pv32_FULL_19_0_CUS.def SPIRE_MC_pv32_FULL_19_0_CUS_CAL.xml SPIRE_SSF_OD0086_1_0.ssf SPIRE_POS_OD0086_1_0.pos SPIRE_ICP_OD0086_1_0.icp SPIRE_AOR_OD0086_1_0.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_OD0086_1_0.txt TAKE NOTE : The above steps are to be copied into the SPIRE BASIC TEMPLATE LOG FILE for OD86 OK MC directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/SPIRE/SPIRE_FULL_1> cp *.* /home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE> ls OD0086_SPIRE_FULL_1_20090804.tar SPIRE_Duration.txt SPIRE_MC_pv32_FULL_19_0_CUS.def SPIRE_SSF_OD0086_1_0.ssf SPIRE_AOR_OD0086_1_0.aor SPIRE_ICP_OD0086_1_0.icp SPIRE_POS_OD0086_1_0.pos SPIRE_CUS_THCP.py SPIRE_MC_pv32_FULL_19_0_CUS_CAL.xml SPIRE_Readme_OD0086_1_0.txt 6(b) Set the Instrument Model & check with CUSGUI Set instrument = SPIRE hscphs2@heropl02/home/hscphs2/.hcss> vi Uplink_Coord.props #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Opened CUSGUI with SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE> Aug 4, 2009 4:25:01 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:25:02 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:25:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:25:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:25:02 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Aug 4, 2009 4:25:19 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be SPIRE 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Aug 4, 2009 4:26:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:26:41 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:26:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:26:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:26:50 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted [1] + Running nedit MC_H20_P14_S18_PV.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE> cus -f -m "clean SPIRE CUS from DB" -caldeleteall Aug 4, 2009 4:26:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:26:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:26:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:26:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:27:01 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 OK TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_FM1_M_903062241 OK 6(d) Import the new Instrument CUS & Cal tables into the DB Import SPIRE_FULL_19 Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE> cus -m "upload SPIRE_MC_19 mission config" -import SPIRE_MC_pv32_FULL_19_0_CUS.def -importcaltables SPIRE_MC_pv32_FULL_19_0_CUS_CAL.xml Aug 4, 2009 7:10:20 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 7:10:21 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 7:10:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:10:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:10:36 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Aug 4, 2009 7:10:36 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Aug 4, 2009 7:10:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:10:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:10:38 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv32_FULL_19_0_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by SPIRE. OK 6(e) GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. OK At this point, you should have open a log file for the OD86 Import for HIFI i.e. OD86_HIFI_FULL_3.log which is located in /icchsc/delivery/OD0084/logs directory. Go to that Log file, update it with some of the information now contained in this LOG file. Run the duration scripts in that LOG file i.e. running them against the files located in the Delivery directory. When this is successful, then you MUST come back to this step of the Procedure. Note that the Templates send you back to here also!!! If No Differences found then proceed to the Next Step. 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 SPIRE_MC_19 TAKE NOTE : It is very important that you commit the delivery as defined above. OK 6(g) Create the new Mission Configuration name in the DB hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS> missetup -addconfig MC_H21_P14_S19_PV Aug 4, 2009 4:09:17 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:09:18 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:09:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:09:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:09:18 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Aug 4, 2009 4:09:18 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H21_P14_S19_PV" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" TAKE NOTE : Confirm the correct Mission Config Name has been created as shown in the last line above. OK 6(h) Import the New SPIRE Instrument Model into the Mission Configuration. ADDED HIFI MODEL TO THE NEW MISSION CONFIGURATION MC_H21_P14_S18_PV Run CUSGUI >cusgui& Select "ADD Instrument Model to a Mission Configuration" and select the correct Mission Config. [1] + Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0086/SPIRE/SPIRE_FULL_1> Aug 4, 2009 7:19:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 7:19:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 7:19:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:19:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:19:22 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Aug 4, 2009 7:19:35 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P14_S19_PV" Aug 4, 2009 7:19:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:19:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:21:55 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P14_S19_PV" Aug 4, 2009 7:21:59 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : If you have selected the correct Mission Configuration then you can confirm this in the cusgui log as shown above. THIS ENDS THE IMPORT OF THE NEW SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. ================== 7. Steps to Import the OLD PACS Instrument model into the MC a.Set Instrument Model = PACS b.Check with CUSGUI c.Run the duration script for the PACS instrument d.Import into the new Mission Configuration 7(a) Set Instrument Model = PACS hscphs2@heropl02/home/hscphs2/.hcss> vi Uplink_Coord.props #Comment out next two for PACS only #hcss.mps.obdb_file = OBDB_4_0_B004_20090325.csv #hcss.mps.stpf_file = STPF_00002_20090324.csv #CUS #var.hcss.instrument = SPIRE var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT 7(b) Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS> Aug 4, 2009 4:05:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:05:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:05:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:05:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:05:22 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Aug 4, 2009 4:05:49 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be PACS if you want to work with the PACS instrument model. 7(c) Run the duration script for the PACS instrument Run the duration script for OD 84 delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS> 2createOBSMODtable.csh PACS_POS_OD0084_1_0.pos /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS/PACS_FULL_1 84 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS> diff PACS_DUR_OD0084_compare_1_0.txt PACS_DUR_OD84.txt No Differences found. This confirms the Instrument model contents is consistent with the PACS last Mission Configuration. 7(d) Import into the new Mission Configuration OPENED CUSGUI FOR THE PACS DELIVERY ADDED PACS MODEL TO THE NEW MISSION CONFIG - MC_H21_P14_S19_PV hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/PACS> Aug 4, 2009 4:10:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:10:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:10:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:10:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:10:11 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Aug 4, 2009 4:10:34 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P14_S19_PV" Aug 4, 2009 4:10:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:10:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:11:03 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : When PACS is added to the Mission Configuration, it logged in the Cusgui terminal log (as can be seen above) ================== 8. Steps to Import the OLD HIFI Instrument model into the MC 8(a) Set Instrument Model = HIFI #Comment out next two for PACS only hcss.mps.obdb_file = OBDB_4_0_B004_20090325.csv hcss.mps.stpf_file = STPF_00002_20090324.csv #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT 8(b) Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/HIFI> Aug 4, 2009 4:13:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:13:21 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:13:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:13:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:13:21 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument TAKE NOTE : Instrument MUST be HIFI in the above terminal Log in order to proceed. 8(c) Run the duration script for the HIFI instrument Run the duration script of OD86 against the HIFI Instrument Model in my session : hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/HIFI> duration.sh 0086 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/HIFI> diff HIFI_DUR_OD0086_3_0.txt summary_OD0086.log 0a1 > No Differences 8(d) Import into the new Mission Configuration Imported HIFI model into the new mission config hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/HIFI> Aug 4, 2009 4:13:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 4:13:21 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 4:13:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:13:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:13:21 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Aug 4, 2009 4:13:50 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P14_S19_PV" Aug 4, 2009 4:14:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:14:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 4:14:37 PM herschel.cus.gui.CusEditor exit INFO: Quitting. ==================== 9. Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophander to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H21_P14_S19_PV hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE> propHandler & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P14_S19_PV/SPIRE> Aug 4, 2009 7:23:48 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 4, 2009 7:23:49 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 4, 2009 7:23:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 4, 2009 7:23:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Running CDH.getObsProgrammes() Aug 4, 2009 7:23:49 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Aug 4, 2009 7:23:49 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 25 Aug 4, 2009 7:23:49 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Aug 4, 2009 7:23:49 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P14_S19_PV" Aug 4, 2009 7:23:56 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 7035 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration. 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. OK Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same name as the Mission Configuration i.e. MC_H20_P14_S19_PV Exported all the HSpot files to this folder : /home/hscphs2/icchsc/HSpot_files/MC_H21_P14_S19_PV/ Example of the last entry in the log : Aug 4, 2009 7:26:20 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P14_S19_PV/HifiSScanModeFastDBSGen.prop Aug 4, 2009 7:26:20 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P14_S19_PV/HifiManCmd_HIFI_Rescue_to_switched_offGen.prop 11. Do the Check for a new cus script for Eva Do the following : hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P14_S19_PV> ls *.prop >& MC_H21_P14_S19_PV.txt 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_H21_P14_S18_PV.txt MC_H21_P14_S19_PV.txt If there is a difference inform Eva & Larry of the result. If there is NO difference then no need to inform Eva or Larry. Done 12. Final Jboss Activities Log into Jboss #2 [2] + Running propHandler hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0084/PACS/PACS_FULL_1> ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Fri Jul 31 15:09:34 2009 from herl39.net4.lan herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02 PHS: Using BUILDNUM 578 PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 herjbo02.esac.esa.int/home/hsc_phs> stopJbossTest set old=/home/hsc_phs chdir /usr/local/software/jboss/jboss-3.2.6_0_6_5/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1199 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> mkdir fileHolder_ops_MC_H21_P14_S18_PV/ 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. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P14_S19_PV> scp *.* hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H21_P14_S19_PV/ hsc_phs@herjbo02's password: Next Update the properties file : herjbo02.esac.esa.int/home/hsc_phs/.hcss> vi HCSS_PHS_TEST_herjbo02_0_6_6.props Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #LARRY & MARK TIME ESTIMATOR hcss.phs.timeEstimatorVersion=LARRY/MARK-USE-ONLY-PV_MC_H21_P14_S19_PV_090804 #LARRY & MARK MISSION CONFIG hcss.ccm.mission.config = MC_H21_P14_S19_PV #LARRY & MARK DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H21_P14_S19_PV Finally Restart the Test Jboss. > startJbossTest LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.