1. Delivery note from SPIRE: 16th August 09 Dear Colleagues of the HSC Ops Group, This e-mail is to notify you that I have just uploaded the SPIRE PV OD0098 tar file (OD0098_SPIRE_FULL_1_20090816.tar) onto the CVS server under develop/data/observingmodes/hscpv/od098. 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_pv36_FULL_21_0_CUS.def SPIRE_MC_pv36_FULL_21_0_CUS_CAL.xml Please acknowledge the receipt of this delivery to us. Best regards, Sarah TAKE NOTE : Tar file Name OD0098_SPIRE_FULL_1_20090816.tar & MC Name 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 1.1.0 ------ ASSUMED TO BE OK - not checked --------------- 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 When Jboss checked later in the procedure I obtained: PHS: Using BUILDNUM 578 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_v1.1.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_P15_S20_PV/ SPIRE are delivering a new MC, so the new Mission Configuration name shall be MC_H21_P15_S21_PV 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) Make the directory MC_H21_P15_S20_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_P15_S21_PV> ls HIFI/ logs/ PACS/ SPIRE/ This LOG file has been placed in the /logs directory and given the name MC_H21_P15_S21_PV.log. Make also the delivery directory & subdirectories. If the tar file is called OD0098_SPIRE_FULL_1_20090816.tar Then you create a directory in /home/hscphs2/icchsc/delivery called OD0098. Within this directory you create SPIRE/SPIRE_FULL_1 subdirectories. Also create in this OD0098 directory a log file directory where the BASIC TEMPLATE Log file shall be placed. hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098> ls logs/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098> cd SPIRE hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE> ls SPIRE_FULL_1/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE> cd ../logs hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/logs> ls OD94_SPIRE_FULL_1.log 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_P15_S19_PV/ then go to that directory and copy across the contents of the HIFI & SPIRE subdirectories into the equivalent subdirectories of the MC_H21_P15_S20_PV folder. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV> cp ../MC_H21_P15_S20_PV/PACS/* PACS/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV> cp ../MC_H21_P15_S20_PV/HIFI/* HIFI/ Next remove in the HIFI & PACS subfolders all files which were created when you ran the HIFI & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/HIFI> ls duration.sh* HIFI_POS_OD0086_3_0.pos HIFI_AOR_OD0086_3_0.aor HIFI_Readme_OD0086_3_0.txt HIFI_AOR_OD86.aor HIFI_SSF_OD0086_3_0.ssf HIFI_DUR_OD0086_3_0.txt OD0086_HIFI_FULL_3_20090802.tar HIFI_ICP_OD0086_3_0.icp summary_OD86.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/HIFI> rm summary_OD86.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/HIFI> ls duration.sh* HIFI_POS_OD0086_3_0.pos HIFI_AOR_OD0086_3_0.aor HIFI_Readme_OD0086_3_0.txt HIFI_AOR_OD86.aor HIFI_SSF_OD0086_3_0.ssf HIFI_DUR_OD0086_3_0.txt OD0086_HIFI_FULL_3_20090802.tar HIFI_ICP_OD0086_3_0.icp PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/PACS> ls 2createOBSMODtable.csh* OD0090_PACS_FULL_1_090806.tar PACS_AOR_OD0090_1_0.aor PACS_DUR_OD0090_compare_1_0.txt PACS_ICP_OD0090_1_0.icp PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS_CAL.xml PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS.def PACS_POS_OD0090_1_0.pos PACS_Readme_OD0090_1_0.txt PACS_SSF_OD0090_1_0.ssf hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/PACS> rm PACS_DUR_OD0090_compare_1_0.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/PACS> ls 2createOBSMODtable.csh* OD0090_PACS_FULL_1_090806.tar PACS_AOR_OD0090_1_0.aor PACS_ICP_OD0090_1_0.icp PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS_CAL.xml PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS.def PACS_POS_OD0090_1_0.pos PACS_Readme_OD0090_1_0.txt PACS_SSF_OD0090_1_0.ssf 5. Steps to Import the new SPIRE Instrument model into a new MC Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) Set the Instrument Model & check with CUSGUI Clean the CUS & Cal tables from the instrument model Import the new Instrument Cus & Cal into the DB GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. If Durations are OK then COMMIT the Delivery with CUSGUI Create the new Mission Configuration name in the DB Import the New SPIRE 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/OD0098/SPIRE/SPIRE_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: -delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1> cd develop/data/observingmodes/hscpv/od098/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1/develop/data/observingmodes/hscpv/od098> ls CVS/ OD0098_SPIRE_FULL_1_20090816.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1/develop/data/observingmodes/hscpv/od098> cp OD0098_SPIRE_FULL_1_20090816.tar /home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1> ls develop/ OD0098_SPIRE_FULL_1_20090816.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0094/SPIRE/SPIRE_FULL_1> ls OD0094_SPIRE_FULL_1_20090810.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1> tar -xvf OD0098_SPIRE_FULL_1_20090816.tar SPIRE_MC_pv36_FULL_21_0_CUS.def SPIRE_MC_pv36_FULL_21_0_CUS_CAL.xml SPIRE_SSF_OD0098_1_0.ssf SPIRE_POS_OD0098_1_0.pos SPIRE_ICP_OD0098_1_0.icp SPIRE_AOR_OD0098_1_0.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_OD0098_1_0.txt TAKE NOTE : The above steps are to be copied into the PACS BASIC TEMPLATE LOG FILE for OD98 - OK! - mission_config directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/SPIRE/SPIRE_FULL_1> cp *.* /home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/SPIRE> ls OD0098_SPIRE_FULL_1_20090816.tar SPIRE_Duration.txt SPIRE_MC_pv36_FULL_21_0_CUS.def SPIRE_SSF_OD0098_1_0.ssf SPIRE_AOR_OD0098_1_0.aor SPIRE_ICP_OD0098_1_0.icp SPIRE_POS_OD0098_1_0.pos SPIRE_CUS_THCP.py SPIRE_MC_pv36_FULL_21_0_CUS_CAL.xml SPIRE_Readme_OD0098_1_0.txt 6(b) Set the Instrument Model & check with CUSGUI Update the instrument properties in the .hcss directory hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props Select SPIRE as the instrument #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Opened cusgui hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/SPIRE> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/SPIRE> Aug 16, 2009 7:55:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 7:55:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 7:55:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:55:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:55:07 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Aug 16, 2009 7:56:07 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE 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_H21_P15_S21_PV/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Aug 16, 2009 7:57:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 7:57:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 7:57: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 16, 2009 7:57:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:57:11 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted [1] + Running nedit MC_H21_P15_S21_PV.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/SPIRE> cus -f -m "clean SPIRE CUS from DB" -caldeleteall Aug 16, 2009 7:57:20 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 7:57:21 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 7:57: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 16, 2009 7:57:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:57:26 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_FM1_M_903062241 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (Version 20.0 = pvPhase_mconfig_34). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/SPIRE> cus -m "upload SPIRE_MC_20 mission config" -import SPIRE_MC_pv36_FULL_21_0_CUS.def -importcaltables SPIRE_MC_pv36_FULL_21_0_CUS_CAL.xml Aug 16, 2009 7:59:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 7:59:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 7:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:59:38 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Aug 16, 2009 7:59:38 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Aug 16, 2009 7:59:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:59:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 7:59:40 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv36_FULL_21_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 : SPIRE_MC_pv36_FULL_21_0_CUS_CAL.xml CONFIRMED!! 6(e) GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. At this point, you should have open a log file for the OD98 Import for SPIRE i.e. OD98_SPIRE_FULL_1.log which is located in /icchsc/delivery/OD0098/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. DONE. No differences found. 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_21 TAKE NOTE : It is very important that you commit the delivery as defined above. 6(g) Create the new Mission Configuration name in the DB The command to be run is : missetup -addconfig MC_H21_P15_S21_PV hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/PACS> missetup -addconfig MC_H21_P15_S21_PV Aug 16, 2009 4:11:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 4:11:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 4:11: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 16, 2009 4:11:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:11:11 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Aug 16, 2009 4:11:11 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H21_P15_S21_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 : CONFIRMED. 6(h) Import the New SPIRE Instrument Model into the Mission Configuration. ADDED SPIRE MODEL TO THE NEW MISSION CONFIGURATION MC_H21_P15_S21_PV Run CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/SPIRE> Aug 16, 2009 8:11:58 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 8:11:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 8:11:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 8:11:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 8:11:59 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Aug 16, 2009 8:12:45 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P15_S21_PV" Aug 16, 2009 8:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 8:13:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 8:13:36 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P15_S21_PV" Aug 16, 2009 8:14:17 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. 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(a) Set Instrument Model = HIFI 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_P15_S21_PV/HIFI> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/HIFI> Aug 16, 2009 4:13:43 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 4:13:44 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 4:13:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:13:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:13:45 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Aug 16, 2009 4:14:03 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Run the duration script for the SPIRE instrument Run the duration script for OD 86 delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/HIFI> ./duration.sh 86 next OD = 86 -- mode HifiEngSetIntoPrimary -- mode HifiEngSetIntoStandby_II_Dissipate -- mode HifiEng_Spur_Investigation_COP -- mode HifiEngSScanDBS -- mode HifiEngSwitchonLO -- mode HifiMappingModeDBSCross -- mode HifiMappingModeDBSRaster -- mode HifiMappingModeFastDBSCross -- mode HifiMappingModeFastDBSRaster -- mode HifiMappingModeFSwitchOTF -- mode HifiMappingModeFSwitchOTFNoRef -- mode HifiMappingModeLoadChopOTF -- mode HifiMappingModeLoadChopOTFNoRef -- mode HifiMappingModeOTF Duration of HifiEngSetIntoPrimary with default parameters = 6 Duration of HifiEngSetIntoStandby_II_Dissipate with default parameters = 24 Duration of HifiEng_Spur_Investigation_COP with default parameters = 191 Duration of HifiEngSScanDBS with default parameters = 1074 Duration of HifiEngSwitchonLO with default parameters = 384 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 DIFF hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/HIFI> diff HIFI_DUR_OD0086_3_0.txt summary_OD86.log 0a1 > No differences. This confirms the Instrument model contents is consistent with the HIFI last Mission Configuration. 7(d) Import HIFI into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/HIFI> Aug 16, 2009 4:15:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 4:15:11 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 4:15: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 16, 2009 4:15:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:15:12 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Aug 16, 2009 4:15:42 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P15_S21_PV" Aug 16, 2009 4:15:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:15:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:16:35 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P15_S21_PV" Aug 16, 2009 4:16:40 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the OLD PACS Instrument model into the MC Set Instrument Model = PACS 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 = 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_H21_P15_S21_PV/PACS> cusgui& hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/PACS> Aug 16, 2009 4:08:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 4:08:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 4:08:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:08:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 16, 2009 4:08:23 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Aug 16, 2009 4:08:52 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. - CONFIRMED!! hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S21_PV/PACS> ls 2createOBSMODtable.sh* PACS_DUR_OD0090.txt PACS_POS_OD0090_1_0.pos OD0090_PACS_FULL_1_090806.tar PACS_ICP_OD0090_1_0.icp PACS_Readme_OD0090_1_0.txt PACS_AOR_OD0090_1_0.aor PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS_CAL.xml PACS_SSF_OD0090_1_0.ssf PACS_DUR_OD0090_compare_1_0.txt PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS.def 8(c) Run the duration script for the PACS instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/PACS> bash bash-3.00$ ./2createOBSMODtable.sh PACS_POS_OD0090_1_0.pos /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/PACS/ 0090 bash-3.00$ ls 2createOBSMODtable.csh PACS_AOR_OD0090_1_0.aor 2createOBSMODtable.sh PACS_DUR_OD0090_compare_1_0.txt msgPacsCal_PacsLineSpec_PV.txt PACS_DUR_OD0090.txt msgPacsCal_PacsSpecSlewCal35_Flex.txt PACS_ICP_OD0090_1_0.icp msgPacsCal_Spec_Rsrf.txt PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS_CAL.xml msgPacsCal_WaveCalChop.txt PACS_MC_CoP_PV_2009-08-06C_FULL_15_0_CUS.def msgPacsCal_WaveCalNoChop.txt PACS_POS_OD0090_1_0.pos msgPacsEng_orbit_epilogue_CSon.txt PACS_Readme_OD0090_1_0.txt msgPacsEng_Spec_setup_Flex.txt PACS_SSF_OD0090_1_0.ssf msgPacsEng_Spec_spu_setup_wait_reset.txt tmp msgPacsLineSpec.txt tmpobsmode OD0090_PACS_FULL_1_090806.tar bash-3.00$ diff PACS_DUR_OD0090_compare_1_0.txt PACS_DUR_OD0090.txt bash-3.00$exit No differences! 8(d) Import PACS model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P15_S20_PV/PACS> Aug 11, 2009 9:03:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 11, 2009 9:03:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 11, 2009 9:03:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 11, 2009 9:03:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 11, 2009 9:03:08 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Aug 11, 2009 9:03:38 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P15_S20_PV" Aug 11, 2009 9:03:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 11, 2009 9:03:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Aug 11, 2009 9:05:46 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P15_S20_PV" Aug 11, 2009 9:05:49 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 Prophandler to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H21_P15_S21_PV Source the PHS Environment for 1.1.0 hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v1.1.0_phs setHcssExtLibs_csh:INFO:Variable HCSS_DIR set to [/herschel/software/hcss/hcss_1.1.0_phs/dp-core] setHcssExtLibs_csh:INFO:Start setting up variables for HCSS #1 reference platform v8.6 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 #1 reference platform v8.6 hscphs2@heropl02/home/hscphs2/otherSetups> propHandler & hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0098/logs> Aug 16, 2009 8:54:20 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Aug 16, 2009 8:54:21 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Aug 16, 2009 8:54: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 16, 2009 8:54:21 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 16, 2009 8:54:21 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Aug 16, 2009 8:54:21 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 21 Aug 16, 2009 8:54:21 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Aug 16, 2009 8:54:21 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P15_S21_PV" 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_H21_P15_S21_PV Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P15_S21_PV/ Example of the last entry in the log: Aug 16, 2009 8:50:34 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P15_S21_PV/HifiSScanModeFastDBSGen.prop Aug 16, 2009 8:50:34 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P15_S21_PV/HifiManCmd_HIFI_Rescue_to_switched_offGen.prop 11. Do the check for a new script for Eva Do the following: >cd /home/hscphs2/icchsc/HSpot_files/MC_H21_P15_S21_PV hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P15_S21_PV> ls *.prop > & MC_H21_P15_S21_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_P15_S20_PV.txt MC_H21_P15_S21_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. No differences Eva and Larry have been informed 12. Final Jboss Activities Log into Jboss #2 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 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_H21_P15_S20_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. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P15_S21_PV> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H21_P15_S21_PV/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> emacs 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!! #MARK & CHARO TIME ESTIMATOR hcss.phs.timeEstimatorVersion=MARK-CHARO-USE-ONLY-MC_H21_P15_S21_PV_090816 #MARK & CHARO MISSION CONFIG hcss.ccm.mission.config = MC_H21_P15_S21_PV #MARK & CHARO DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H21_P15_S21_PV Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.