HSC-PROC-UPLC-0004 : Standard Mission Config Template 1. Delivery Notes SPIRE Delivery note - 29th July 09 Dear Colleagues of the HSC Ops Group, This e-mail is to notify you that I have just uploaded the SPIRE PV OD0082 tar file (OD0082_SPIRE_FULL_2_20090729.tar) onto the CVS server under develop/data/observingmodes/hscpv/od082. 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 contains a new MC (SPIRE_MC_pv31_FULL_18_0). Please acknowledge the receipt of this delivery to us. All the best, Brian O'Halloran Take Note of the Tar File & the New MC name (for MPS email and for steps below) OD0082_SPIRE_FULL_2_20090729.tar SPIRE_MC_pv31_FULL_18_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: Initializing HCSS_CLASSPATH for a new style build setHcssExtLibs_csh:INFO:Updating existing CLASSPATH setHcssExtLibs_csh:INFO:Loading the OS specific enhancements setHcssExtLibs_csh:INFO:- found OS type linux setHcssExtLibs_csh:INFO:- found 32 bit platform. setHcssExtLibs_csh:INFO:Finished setting up variables for HCSS #129 reference platform v8.4 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_H20_P13_S17_PV SPIRE are delivering a new MC (#18) so the new Mission Configuration name shall be MC_H20_P13_S18_PV 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) Make the directory MC_H20_P13_S18_PV in the /icchsc/mission_config directory. Within this directory create the subdirectories : SPIRE, PACS, HIFI & logs This LOG file should be placed in the /logs directory and given the name MC_H20_P13_S18_PV.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/logs> ls MC_H20_P13_S18_PV.log Make also the delivery directory & subdirectories. If the tar file is called OD0082_SPIRE_FULL_2_20090729.tar Then you create a directory in /home/hscphs2/icchsc/delivery called OD0082. Within this directory you create SPIRE/SPIRE_FULL_2 subdirectories. Also create in this OD0082 directory a log file directory where the BASIC TEMPLATE Log file shall be placed. hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082> ls logs/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082> ls SPIRE SPIRE_FULL_2/ 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_H20_P13_S17_PV then go to that directory and copy across the contents of the SPIRE & PACS subdirectories into the equivalent subdirectories of the MC_H20_P13_S18_PV folder. hscphs2@heropl02/home/hscphs2/icchsc/mission_config> cp MC_H20_P13_S17_PV/HIFI/*.* MC_H20_P13_S18_PV/HIFI/. hscphs2@heropl02/home/hscphs2/icchsc/mission_config> cp MC_H20_P13_S17_PV/PACS/*.* MC_H20_P13_S18_PV/PACS/. Next remove in the HIFI & PACS subfolders all files which were created when you ran the HIFI & PACS duration files e.g. tmp, etc etc. 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/OD0082> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082> cvs co develop/data/observingmodes/hscpv/od082/OD0082_SPIRE_FULL_2_20090729.tar U develop/data/observingmodes/hscpv/od082/OD0082_SPIRE_FULL_2_20090729.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082> cd SPIRE/SPIRE_FULL_2/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082/SPIRE/SPIRE_FULL_2> cp ../../develop/data/observingmodes/hscpv/od082/OD0082_SPIRE_FULL_2_20090729.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082/SPIRE/SPIRE_FULL_2> ls OD0082_SPIRE_FULL_2_20090729.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0082/SPIRE/SPIRE_FULL_2> tar -xvf OD0082_SPIRE_FULL_2_20090729.tar SPIRE_MC_pv31_FULL_18_0_CUS.def SPIRE_MC_pv31_FULL_18_0_CUS_CAL.xml SPIRE_SSF_OD0082_2_0.ssf SPIRE_POS_OD0082_2_0.pos SPIRE_ICP_OD0082_2_0.icp SPIRE_AOR_OD0082_2_0.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_OD0082_2_0.txt TAKE NOTE : The above steps are to be copied into the SPIRE BASIC TEMPLATE LOG FILE for OD82 MC directory hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV> cp ../../delivery/OD0082/SPIRE/SPIRE_FULL_2/*.* SPIRE/. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/SPIRE> ls OD0082_SPIRE_FULL_2_20090729.tar SPIRE_MC_pv31_FULL_18_0_CUS_CAL.xml SPIRE_AOR_OD0082_2_0.aor SPIRE_MC_pv31_FULL_18_0_CUS.def SPIRE_CUS_THCP.py SPIRE_POS_OD0082_2_0.pos SPIRE_Duration.txt SPIRE_Readme_OD0082_2_0.txt SPIRE_ICP_OD0082_2_0.icp SPIRE_SSF_OD0082_2_0.ssf 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 HIFI hscphs2@heropl02/home/hscphs2> cusgui& [3] 18445 [3] Running cusgui hscphs2@heropl02/home/hscphs2> Jul 29, 2009 6:15:33 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:15:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:15:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:15:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:15:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jul 29, 2009 6:15:45 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> cus -f -m "clean SPIRE CUS from DB" -deleteall Jul 29, 2009 6:16:59 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:17:00 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:17:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:17:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:17:07 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jul 29, 2009 6:17:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:17:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:17:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:17:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:17:44 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables 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_18 Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/SPIRE> cus -m "upload SPIRE_MC_18 mission config" -import SPIRE_MC_pv31_FULL_18_0_CUS.def -importcaltables SPIRE_MC_pv31_FULL_18_0_CUS_CAL.xml Jul 29, 2009 6:20:16 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:20:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:20:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:20:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:20:29 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jul 29, 2009 6:20:29 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jul 29, 2009 6:20:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:20:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:20:31 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv31_FULL_18_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. 6(e) GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. OK Proceed to the Next Step. 6(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_18 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 The command to be run is : missetup -addconfig MC_H20_P13_S17_PV hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/SPIRE> missetup -addconfig MC_H20_P13_S18_PV Jul 29, 2009 6:30:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:30:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:30:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:30:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:30:35 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Jul 29, 2009 6:30:35 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H20_P13_S18_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 SPIRE MODEL TO THE NEW MISSION CONFIGURATION MC_H20_P13_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/mission_config/MC_H20_P13_S18_PV/SPIRE> Jul 29, 2009 6:32:05 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H20_P13_S18_PV" Jul 29, 2009 6:32:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:32:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int 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 HIFI Instrument model into the MC a.Set Instrument Model = HIFI b.Check with CUSGUI c.Run the duration script for the SPIRE instrument d.Import into the new Mission Configuration 7(a) Set Instrument Model = 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 7(b) Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/SPIRE> cusgui& [2] 19554 [1] + Running cusgui [2] - Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/SPIRE> Jul 29, 2009 6:36:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:36:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:36:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:36:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:36:35 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jul 29, 2009 6:36:46 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI. 7(c) Run the duration script for the HIFI instrument Run the duration script for OD 81 delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/HIFI> cp HIFI_AOR_OD0081_1_0.aor HIFI_AOR_OD0081.aor hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/HIFI> duration.sh 0081 next OD = 0081 -- mode HifiEng_diplexerscan_M1_COP -- mode HifiEngSetIntoPrimary -- mode HifiEngSetIntoStandby_I -- mode HifiEngSetIntoStandby_II -- mode HifiEng_Stab_COP -- mode HifiEngSwitchonLO -- mode HifiPointModeDBS -- mode HifiPointModeFastDBS -- mode HifiPointModeFSwitch -- mode HifiPointModeFSwitchNoRef -- mode HifiPointModeLoadChop -- mode HifiPointModeLoadChopNoRef -- mode HifiPointModePositionSwitch -- mode HifiMappingModeDBSCross -- mode HifiMappingModeDBSRaster -- mode HifiMappingModeFastDBSCross -- mode HifiMappingModeFastDBSRaster -- mode HifiMappingModeFSwitchOTF -- mode HifiMappingModeFSwitchOTFNoRef -- mode HifiMappingModeLoadChopOTF -- mode HifiMappingModeLoadChopOTFNoRef -- mode HifiMappingModeOTF Duration of HifiEng_diplexerscan_M1_COP with default parameters = 1073 Duration of HifiEngSetIntoPrimary with default parameters = 6 Duration of HifiEngSetIntoStandby_I with default parameters = 10 Duration of HifiEngSetIntoStandby_II with default parameters = 23 Duration of HifiEng_Stab_COP with default parameters = 1296 Duration of HifiEngSwitchonLO with default parameters = 384 Duration of HifiPointModeDBS with default parameters = 67 Duration of HifiPointModeFastDBS with default parameters = 55 Duration of HifiPointModeFSwitch with default parameters = 45 Duration of HifiPointModeFSwitchNoRef with default parameters = 20 Duration of HifiPointModeLoadChop with default parameters = 45 Duration of HifiPointModeLoadChopNoRef with default parameters = 20 Duration of HifiPointModePositionSwitch with default parameters = 37 Duration of HifiMappingModeDBSCross with default parameters = 537 Duration of HifiMappingModeDBSRaster with default parameters = 176 Duration of HifiMappingModeFastDBSCross with default parameters = 465 Duration of HifiMappingModeFastDBSRaster with default parameters = 152 Duration of HifiMappingModeFSwitchOTF with default parameters = 109 Duration of HifiMappingModeFSwitchOTFNoRef with default parameters = 26 Duration of HifiMappingModeLoadChopOTF with default parameters = 109 Duration of HifiMappingModeLoadChopOTFNoRef with default parameters = 26 Duration of HifiMappingModeOTF with default parameters = 75 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/HIFI> diff summary_OD0081.log HIFI_DUR_OD0081_1_0.txt 1d0 < No Differences found. This confirms the Instrument model contents is consistent with the HIFI last Mission Configuration. 7(d) Import into the new Mission Configuration OPENED CUSGUI FOR THE HIFI DELIVERY ADDED SPIRE MODEL TO THE NEW MISSION CONFIG - MC_H20_P13_S18_PV hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/HIFI> cusgui& [1] 19980 [1] + Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/HIFI> Jul 29, 2009 6:42:33 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:42:34 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:42:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jul 29, 2009 6:43:17 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H20_P13_S18_PV" Jul 29, 2009 6:43:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:43:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int TAKE NOTE : When HIFI is added to the Mission Configuration, it logged in the Cusgui terminal log (as can be seen above) ================== 8. Steps to Import the OLD PACS Instrument model into the MC a.Set Instrument Model = PACS & OBDB/STPF properties b.Check with CUSGUI c.Run the duration script for the PACS instrument d.Import into the new Mission Configuration e.Reset the OBDB/STPF properties 8(a) Set Instrument Model = PACS & OBDB/STPF properties Set Instrument model = PACS #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_H20_P13_S18_PV/PACS> Jul 29, 2009 6:45:49 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:45:49 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:45:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:45:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:45:50 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument TAKE NOTE : Instrument MUST be PACS in the above terminal Log in order to proceed. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S17_PV/PACS> ls 2createOBSMODtable.csh* PACS_DUR_OD0078_compare_1_0.txt PACS_POS_OD0078_1_0.pos MC_H19_P13_S17_PV.txt PACS_ICP_OD0078_1_0.icp PACS_Readme_OD0078_1_0.txt OD0078_PACS_FULL_1_090724.tar PACS_MC_CoP_PV_2009-07-24B_FULL_13_0_CUS_CAL.xml PACS_SSF_OD0078_1_0.ssf PACS_AOR_OD0078_1_0.aor PACS_MC_CoP_PV_2009-07-24B_FULL_13_0_CUS.def 8(c) Run the duration script for the PACS instrument Run the duration script of OD78 against the PACS Instrument Model in my session : hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/PACS> 2createOBSMODtable.csh PACS_POS_OD0078_1_0.pos /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/PACS 78 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/PACS> diff PACS_DUR_OD78.txt PACS_DUR_OD0078_compare_1_0.txt No Differences 8(d) Import into the new Mission Configuration Imported PACS model into the new mission config hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/PACS> Jul 29, 2009 6:49:46 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 6:49:47 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 6:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:49:47 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jul 29, 2009 6:50:13 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H20_P13_S18_PV" Jul 29, 2009 6:50:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:50:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 6:51:20 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H20_P13_S18_PV" Jul 29, 2009 6:51:24 PM herschel.cus.gui.CusEditor exit INFO: Quitting. 8(e) Reset the OBDB/STPF properties Comment back in the OBDB & STPF files in the .hcss properties file #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 ==================== 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_H20_P13_S18_PV hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/PACS> propHandler & [1] 20619 [1] + Running propHandler hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H20_P13_S18_PV/PACS> Jul 29, 2009 7:04:58 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 29, 2009 7:04:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 29, 2009 7:04:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 29, 2009 7:04:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Running CDH.getObsProgrammes() Jul 29, 2009 7:04:59 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Jul 29, 2009 7:04:59 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 25 Jul 29, 2009 7:04:59 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Jul 29, 2009 7:04:59 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H20_P13_S18_PV" Jul 29, 2009 7:05:04 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 4659 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_P13_S18_PV Exported all the HSpot files to this folder : /home/hscphs2/icchsc/HSpot_files/MC_H20_P13_S18_PV/ Example of the last entry in the log : Jul 29, 2009 7:08:02 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H20_P13_S18_PV/HifiManCmd_HIFI_Rescue_to_switched_offGen.prop 11. Do the Check for a new cus script for Eva Do the following : >cd /home/hscphs2/icchsc/HSpot_files/MC_H20_P13_S18_PV hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H20_P13_S18_PV> ls *.prop > & MC_H20_P13_S18_PV.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H20_P13_S18_PV> diff MC_H20_P13_S18_PV.txt ../MC_H20_P13_S17_PV/MC_H20_P13_S17_PV.txt 137a138 > MC_H20_P13_S17_PV.txt Now do a diff between this new txt file and the one generated with the last Mission configuration. If there is a difference inform Eva & Larry of the result. If there is NO difference then no need to inform Eva or Larry. 12. Final Jboss Activities Log into Jboss #2 [rlorente@herl21 ~]$ ssh -X hsc_phs@herjbo02 Source the correct Environment : herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02 PHS: Using BUILDNUM 534 PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 Stop the Test Jboss : 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_H20_P13_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_H20_P13_S17_PV> scp *.* hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H20_P13_S17_PV/ 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_H20_P13_S18_PV_090729 #LARRY & MARK MISSION CONFIG hcss.ccm.mission.config = MC_H20_P13_S18_PV #LARRY & MARK DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H20_P13_S18_PV Finally Restart the Test Jboss. > startJbossTest LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.