1. Delivery note from SPIRE: 19 September 09 Dear Colleagues of the HSC Ops Group, This e-mail is to notify you that I have just uploaded the SPIRE PV OD0134 tar file onto the CVS server. 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. 1. Delivery file, directory & Mission Configuration issues (a) OD tar file name : OD0134_SPIRE_FULL_1_20090919.tar (b) CVS server directory : develop/data/observingmodes/hscpv/od134 (c) Does this delivery include a new Mission configuration? Yes, a new MC is included. 2. TM & TC issues (a) What is the # of TC counts for the OD? TC Counts = 7108 (b) Has the TM limit been exceeded? No, the TM limit has not been exceeded. 3. MPS Input file issues (a) Has a new orbit file been used for the first time in this OD? Yes - we are using the new orbit file H20090916_0001.LOE (b) Has a new SIAM file been used for the first time in this OD? No. We are using 0122_0001.SIAM. (c) Has a new HPSDB file been used for the first time in this OD? No. We are using HPSDB_MOC_HERSCH_CCS_issueMOC3_200908141600. 4. Operations Issues (a) Should FDS disable the checks of Gyro Propagation Requests (ATT_PROP) for this OD? Yes. (b) Are there any Real Time Science Requests in the DTCP? No. (c) For PACS, does this OD include burst mode? N/A. (d) TM limit exceeded (>100%) - possibility of dump over two DTCPs? N/A. (e) ICC to add anything specific to this OD which HSC & MOC should be aware of. We switch from PHOT-STBY to REDY at the end of OD134. Please acknowledge the receipt of this delivery to us. Kind regards, Brian O'Halloran TAKE NOTE : Tar file Name OD0134_SPIRE_FULL_1_20090919.tar & MC Name MC name, taken from CVS: SPIRE_MC_pv48_FULL_30_0_CUS.def SPIRE_MC_pv48_FULL_30_0_CUS_CAL.xml 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 1.1.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal_herjbo02 : 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_P24AST_S29 SPIRE are delivering a new MC, so the new Mission Configuration name shall be MC_H21_P24AST_S30 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) Make the directory MC_H21_P24AST_S30 in the /icchsc/mission_config directory. Within this directory create the subdirectories : SPIRE, PACS, HIFI & logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config> mkdir MC_H21_P24AST_S30/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config> cd MC_H21_P24AST_S30/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30> ls HIFI/ logs/ PACS/ SPIRE/ This LOG file has been placed in the /logs directory and given the name MC_H21_P24AST_S30.log. Make also the delivery directory & subdirectories. If the tar file is called OD0134_SPIRE_FULL_1_20090919.tar Then you create a directory in /home/hscphs2/icchsc/delivery called OD0134. Within this directory you create SPIRE/SPIRE_FULL_1 subdirectories. Also create in this OD0134 directory a log file directory where the BASIC TEMPLATE Log file shall be placed. hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134> ls logs/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134> cd SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE> ls SPIRE_FULL_1/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE> cd ../logs hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/logs> ls OD0134_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_P24AST_S29/ then go to that directory and copy across the contents of the HIFI & PACS subdirectories into the equivalent subdirectories of the MC_H21_P24AST_S30 folder. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S29/PACS/*.* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S29/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_P22_S29_PV/HIFI> ls duration.sh* HIFI_DUR_OD0086_3_0.txt HIFI_Readme_OD0086_3_0.txt summary_OD86.log HIFI_AOR_OD0086_3_0.aor HIFI_ICP_OD0086_3_0.icp HIFI_SSF_OD0086_3_0.ssf HIFI_AOR_OD86.aor HIFI_POS_OD0086_3_0.pos OD0086_HIFI_FULL_3_20090802.tar hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P22_S29_PV/HIFI> rm summary_OD86.log rm: remove regular file `summary_OD86.log'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P22_S29_PV/HIFI> l duration.sh HIFI_DUR_OD0086_3_0.txt HIFI_Readme_OD0086_3_0.txt HIFI_AOR_OD0086_3_0.aor HIFI_ICP_OD0086_3_0.icp HIFI_SSF_OD0086_3_0.ssf HIFI_AOR_OD86.aor HIFI_POS_OD0086_3_0.pos OD0086_HIFI_FULL_3_20090802.tar PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P22_S29_PV/PACS> ls 2createOBSMODtable.sh* PACS_ICP_OD0128_1_0.icp PACS_Readme_OD0128_1_0.txt OD0128_PACS_FULL_1_090913.tar PACS_MC_ASTR_CoP_PV_2009-09-11A_FULL_22_0_CUS_CAL.xml PACS_SSF_OD0128_1_0.ssf PACS_AOR_OD0128_1_0.aor PACS_MC_ASTR_CoP_PV_2009-09-11A_FULL_22_0_CUS.def PACS_DUR_OD0128_compare_1_0.txt PACS_POS_OD0128_1_0.pos 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) - delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> cvs co develop/data/observingmodes/hscpv/od134/OD0134_SPIRE_FULL_1_20090919.tar U develop/data/observingmodes/hscpv/od134/OD0134_SPIRE_FULL_1_20090919.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> cp develop/data/observingmodes/hscpv/od134/OD0134_SPIRE_FULL_1_20090919.tar . == Done using firefox browser and TeamCSDT account in CVS === hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> tar -xvf OD0134_SPIRE_FULL_1_20090919.tar SPIRE_MC_pv48_FULL_30_0_CUS_CAL.xml SPIRE_AOR_OD0134_1_0.aor SPIRE_MC_pv48_FULL_30_0_CUS.def SPIRE_CUS_THCP.py SPIRE_POS_OD0134_1_0.pos SPIRE_Duration.txt SPIRE_Readme_OD0134_1_0.txt SPIRE_ICP_OD0134_1_0.icp SPIRE_SSF_OD0134_1_0.ssf - MC directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> cp *.* /home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE> ls OD0134_SPIRE_FULL_1_20090919.tar SPIRE_MC_pv48_FULL_30_0_CUS_CAL.xml SPIRE_AOR_OD0134_1_0.aor SPIRE_MC_pv48_FULL_30_0_CUS.def SPIRE_CUS_THCP.py SPIRE_POS_OD0134_1_0.pos SPIRE_Duration.txt SPIRE_Readme_OD0134_1_0.txt SPIRE_ICP_OD0134_1_0.icp SPIRE_SSF_OD0134_1_0.ssf TAKE NOTE : The above steps are to be copied into the SPIRE BASIC TEMPLATE LOG FILE for OD134 - OK! 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 cusgui hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> cusgui & [3] 6784 [1] + Running emacs MC_H21_P24AST_S30.log [2] - Running emacs OD0134_SPIRE_FULL_1.log [3] Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0134/SPIRE/SPIRE_FULL_1> Sep 19, 2009 6:00:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:00:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:00:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:00:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:00:58 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 19, 2009 6:01:09 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_P24AST_S30/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Sep 19, 2009 6:02:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:02:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:02:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:02:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:02:47 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Sep 19, 2009 6:04:14 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:04:15 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:04:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:04:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:04:21 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_CCS_MOC3_200908141600 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (Version 30.0 = pvPhase_mconfig_48). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE> cus -m "upload SPIRE_MC_30 mission config" -import SPIRE_MC_pv48_FULL_30_0_CUS.def -importcaltables SPIRE_MC_pv48_FULL_30_0_CUS_CAL.xml Sep 19, 2009 6:12:37 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:12:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:12:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:12:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:12:51 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 19, 2009 6:12:51 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 19, 2009 6:12:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:12:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:12:53 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv48_FULL_30_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_pv48_FULL_30_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 OD0134 Import for SPIRE i.e. OD0134_SPIRE_FULL_1.log which is located in /icchsc/delivery/OD0134/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_30 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_P24AST_S30 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE> missetup -addconfig MC_H21_P24AST_S30 Sep 19, 2009 6:50:41 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:50:42 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:50:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:50:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:50:43 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Sep 19, 2009 6:50:43 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H21_P24AST_S30" 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_P22_S29_PV Run CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE> Sep 19, 2009 6:51:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:51:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:51:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:51:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:51:31 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 19, 2009 6:52:26 PM herschel.versant.ccm.MissionImpl getMissionConfigurationINFO: Using configuration "MC_H21_P24AST_S30" Sep 19, 2009 6:52:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:52:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:52:48 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> emacs 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_P24AST_S30/SPIRE> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/SPIRE> Sep 19, 2009 6:53:58 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:53:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:53:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:53:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:53:59 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 19, 2009 6:54:09 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 HIFI instrument Run the duration script for OD 86 delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/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 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/HIFI> ls duration.sh* HIFI_POS_OD0086_3_0.pos HIFI_AOR_OD0086_3_0.aor HIFI_Readme_OD0086_3_0.txt HIFI_AOR_OD0086.aor HIFI_SSF_OD0086_3_0.ssf HIFI_AOR_OD86.aor OD0086_HIFI_FULL_3_20090802.tar HIFI_DUR_OD0086_3_0.txt summary_OD86.log HIFI_ICP_OD0086_3_0.icp DIFF hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/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_P24AST_S30/HIFI> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/HIFI> Sep 19, 2009 6:58:03 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 6:58:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 6:58:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:58:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:58:04 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 19, 2009 6:58:20 PM herschel.versant.ccm.MissionImpl getMissionConfigurationINFO: Using configuration "MC_H21_P24AST_S30" Sep 19, 2009 6:58:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:58:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 6:58:59 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_P24AST_S30/PACS> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/PACS> Sep 19, 2009 7:00:16 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 7:00:17 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 7:00:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 7:00:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 7:00:18 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 19, 2009 7:00:26 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_P24AST_S30/PACS> ls 2createOBSMODtable.sh* OD0133_PACS_FULL_2_090919.tar PACS_AOR_OD0133_2_0.aor PACS_DUR_OD0133_compare_2_0.txt PACS_ICP_OD0133_2_0.icp PACS_MC_ASTR_CoP_PV_2009-09-18C_FULL_24_0_CUS_CAL.xml PACS_MC_ASTR_CoP_PV_2009-09-18C_FULL_24_0_CUS.def PACS_POS_OD0133_2_0.pos PACS_Readme_OD0133_2_0.txt PACS_SSF_OD0133_2_0.ssf 8(c) Run the duration script for the PACS instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P22_S29_PV/PACS> bash hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P22_S29_PV/PACS> bash bash-3.00$ ./2createOBSMODtable.sh PACS_POS_OD0133_2_0.pos /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/PACS/ 0133 bash-3.00$ ls 2createOBSMODtable.sh msgPacsCal_PacsLineSpec_PV.txt msgPacsCal_PacsRangeSpec_PV.txt msgPacsCal_Spec_Star_Lin_Source.txt msgPacsCal_WaveCalNoChop.txt msgPacsEng_orbit_epilogue.txt msgPacsEng_setCSsTemp.txt msgPacsEng_Spec_setup_Flex.txt msgPacsEng_Spec_spu_setup_wait_reset.txt OD0133_PACS_FULL_2_090919.tar PACS_AOR_OD0133_2_0.aor PACS_DUR_OD0133_compare_2_0.txt PACS_DUR_OD0133.txt PACS_ICP_OD0133_2_0.icp PACS_MC_ASTR_CoP_PV_2009-09-18C_FULL_24_0_CUS_CAL.xml PACS_MC_ASTR_CoP_PV_2009-09-18C_FULL_24_0_CUS.def PACS_POS_OD0133_2_0.pos PACS_Readme_OD0133_2_0.txt PACS_SSF_OD0133_2_0.ssf tmp tmpobsmode bash-3.00$ diff PACS_DUR_OD0133_compare_2_0.txt PACS_DUR_OD0133.txt bash-3.00$ bash-3.00$exit No differences! 8(d) Import PACS model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/PACS> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P24AST_S30/PACS> Sep 19, 2009 7:07:03 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 7:07:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 7:07:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 7:07:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 7:07:04 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 19, 2009 7:07:18 PM herschel.versant.ccm.MissionImpl getMissionConfigurationINFO: Using configuration "MC_H21_P24AST_S30" Sep 19, 2009 7:07:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 7:07:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 7:07:55 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_P22_S29_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/otherSetups> Sep 19, 2009 7:10:12 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 19, 2009 7:10:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 19, 2009 7:10:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 19, 2009 7:10:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Running CDH.getObsProgrammes() Sep 19, 2009 7:10:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Sep 19, 2009 7:10:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 25 Sep 19, 2009 7:10:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Sep 19, 2009 7:10:13 PM herschel.versant.ccm.MissionImpl getMissionConfigurationINFO: Using configuration "MC_H21_P24AST_S30" Sep 19, 2009 7:10:19 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 5601 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_P24AST_S30 Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P24AST_S30/ Example of the last entry in the log: Sep 19, 2009 7:14:56 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P24AST_S30/HifiManCmd_LOU_FDIR_enableGen.prop Sep 19, 2009 7:14:56 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P24AST_S30/HifiSScanModeFastDBSGen.prop Sep 19, 2009 7:14:56 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P24AST_S30/HifiManCmd_HIFI_Rescue_to_switched_offGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P24AST_S30> ls *.prop > & MC_H21_P24AST_S30.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/MC_H21_P24AST_S30> diff MC_H21_P24AST_S30.txt ../MC_H21_P24AST_S29/MC_H21_P24AST_S29.txt 416d415 < SpirePhoto_Cal_PointJiggleId55Gen.prop 430d428 < SpireSpectro_CalGCO_FixedSmecBeamProfileGen.prop 2 new files found: SpirePhoto_Cal_PointJiggleId55Gen.prop SpireSpectro_CalGCO_FixedSmecBeamProfileGen.prop If there is a difference inform Eva & Larry of the result. If there is NO difference then no need to inform Eva or Larry. Message sent to Eva/Larry 12. Final Jboss Activities Log into Jboss #2 [pgarcia@herl22 OD134]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Sat Sep 19 14:46:37 2009 from herl22.net4.lan herjbo02.esac.esa.int/home/hsc_phs> source .mi .minimal .minimal_herjbo02 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_P24AST_S30 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_P24AST_S30> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H21_P24AST_S30/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/fileHolder_ops_MC_H21_P24AST_S30> emacs ~/.hcss/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_P24AST_S30_090919 #MARK & CHARO MISSION CONFIG hcss.ccm.mission.config = MC_H21_P24AST_S30 #MARK & CHARO DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H21_P24AST_S30 Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.