1. Delivery Notes PACS Delivery note - 18th Sep 09 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of PACS PV OD0133 tar file onto the CVS server. 1. Delivery file, directory & Mission Configuration issues (a) OD tar file name : OD0133_PACS_FULL_1_090918.tar (b) CVS server directory : develop/data/observingmodes/hscpv/od133, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 23.0. This has been labeled ASTR, because it affects astronomer backend (see PACS_Readme_OD0133_1_0.txt for details) 2. TM & TC issues (HSC TAKE NOTE FOR TM LIMIT) (a) What is the # of TC counts for the OD? The number of TC_COUNTS in the PACS POS file is 2668. (b) Has the TM limit been exceeded? YES, 102.9% (105% was indicated by MOC as feasible during one dump). 3. MPS Input file issues (a) Has a new orbit file been used for the first time in this OD? NO (b) Has a new SIAM file been used for the first time in this OD? NO (c) Has a new HPSDB file been used for the first time in this OD? NO (d) Is the avoidance set-up default: YES 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? YES, 2 burst mode AORs are between 2009-09-24T15:16:21Z and 2009-09-24T19:37:34Z (2 times occurrence of SDBBUSCG_PACS_BURST) (d) TM limit exceeded - possibility of dump over two DTCPs? POSSIBLE, the expected TM size is 1410.50MB (e) ICC to add anything specific to this OD which HSC & MOC should be aware of. The last 3 hours had to be left empty because of TM excess. The delivery contains the following PACS PV calibration blocks: * PVSpecSetup_orbit_prologue classic (including signal stability monitoring during part of DTCP) * PVSpecWave 4.1.2D on NGC 6302 * PVSpecAOTVal 5.2.1J on OMC1 (HD line, sensitivity) * PVSpecAOTval 5.2.2C on OMC1 (HD line, sensitivity) * PVSpecAOTVal 5.2.3A on TX Cam (range spectroscopy sensitivity, water line spectrum on low continnum) * PVSpecAOTVal 5.2.4A on NGC 6302 (scan strategy ramp length, X-cal source with SPIRE) * PVSpecAOTVal 5.2.1X chopped vesus wave switch performance * PVSpecAOTVal 5.2.2X on NGC 1569 * PVSpecSetUp_setCSs (heating CSs to non-nominal T) * PVSpecGeGa 1.2.3B (on nominal CS2, 80K heated CS1, buffer transmission mode) * PVSpecSetUp_orbit_epilogue Please acknowledge receipt of the e-mail and the delivery. Kind regards, Ulrich Take Note of the Tar File & the New MC name (for MPS email and for steps below) OD0133_PACS_FULL_1_090918.tar 23_AST 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 1.1.0 (Always use the most recent HCSS Software version) PHS SOFTWARE = 1.1.0_PHS (Always use the most recent PHS Software version) 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 Source the Environment before you proceed to step 3. hscphs2@heropl02/home/hscphs2/icchsc/mission_config> source ~/otherSetups/setHcssEnvironment_v1.1.0 TAKE NOTE : If there is a newer HCSS software version in the otherSetups directory then source that new version. 3. What is the New Mission Configuration Name going to be?? MC_H21_P23AST_S29/ hscphs2@heropl02/home/hscphs2/icchsc/mission_config> ls MC_H21_P23AST_S29/ HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery> mkdir OD0133/PACS hscphs2@heropl02/home/hscphs2/icchsc/delivery> mkdir OD0133/PACS/PACS_FULL_1 5. Copy across the contents of the SPIRE & 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. hscphs2@heropl02/home/hscphs2/icchsc/mission_config> ls MC_H21_P22_S29_PV/HIFI 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_OD0086.log HIFI_ICP_OD0086_3_0.icp summary_OD86.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config> cp MC_H21_P22_S29_PV/HIFI/* MC_H21_P23AST_S29/HIFI/. hscphs2@heropl02/home/hscphs2/icchsc/mission_config> ls MC_H21_P22_S29_PV/SPIRE/ OD0130_SPIRE_FULL_1_20090915.tar SPIRE_AOR_OD0130_1_0.aor SPIRE_cus_scripts.txt SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_harness_duration_summary_20090915_15h42m32s.log SPIRE_ICP_OD0130_1_0.icp SPIRE_MC_pv46_FULL_29_0_CUS_CAL.xml SPIRE_MC_pv46_FULL_29_0_CUS.def SPIRE_POS_OD0130_1_0.pos SPIRE_Readme_OD0130_1_0.txt SPIRE_SSF_OD0130_1_0.ssf hscphs2@heropl02/home/hscphs2/icchsc/mission_config> cp MC_H21_P22_S29_PV/SPIRE/* MC_H21_P23AST_S29/SPIRE/. Next remove in the SPIRE & PACS subfolders all files which were created when you ran the SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/SPIRE> rm SPIRE_harness_duration_summary_20090915_15h42m32s.log rm: remove regular file `SPIRE_harness_duration_summary_20090915_15h42m32s.log'? y 6.Steps to Import the new 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/OD0133> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133> cvs co develop/data/observingmodes/hscpv/od133/OD0133_PACS_FULL_1_090918.tar U develop/data/observingmodes/hscpv/od133/OD0133_PACS_FULL_1_090918.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133> ls develop/ logs/ PACS/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133> cd PACS/PACS_FULL_1/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133/PACS/PACS_FULL_1> cp ../../develop/data/observingmodes/hscpv/od133/OD0133_PACS_FULL_1_090918.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133/PACS/PACS_FULL_1> ls OD0133_PACS_FULL_1_090918.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133/PACS/PACS_FULL_1> tar -xvf OD0133_PACS_FULL_1_090918.tar PACS_MC_ASTR_CoP_PV_2009-09-18A_FULL_23_0_CUS.def PACS_MC_ASTR_CoP_PV_2009-09-18A_FULL_23_0_CUS_CAL.xml PACS_AOR_OD0133_1_0.aor PACS_DUR_OD0133_compare_1_0.txt PACS_POS_OD0133_1_0.pos PACS_ICP_OD0133_1_0.icp PACS_SSF_OD0133_1_0.ssf PACS_Readme_OD0133_1_0.txt 2createOBSMODtable.sh TAKE NOTE : The above steps are to be copied into the BASIC TEMPLATE LOG FILE OK MC directory hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/PACS> cp ../../../delivery/OD0133/PACS/PACS_FULL_1/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/PACS> ls 2createOBSMODtable.sh* PACS_MC_ASTR_CoP_PV_2009-09-18A_FULL_23_0_CUS_CAL.xml OD0133_PACS_FULL_1_090918.tar PACS_MC_ASTR_CoP_PV_2009-09-18A_FULL_23_0_CUS.def PACS_AOR_OD0133_1_0.aor PACS_POS_OD0133_1_0.pos PACS_DUR_OD0133_compare_1_0.txt PACS_Readme_OD0133_1_0.txt PACS_ICP_OD0133_1_0.icp PACS_SSF_OD0133_1_0.ssf 6(b) Set the Instrument Model & check with CUSGUI Set instrument = PACS hscphs2@heropl02/home/hscphs2/.hcss> vi Uplink_Coord.props #Comment out next two for PACS only #hcss.mps.obdb_file = OBDB_4_0_B004_20090325.csv #hcss.mps.stpf_file = STPF_00002_20090324.csv #CUS #var.hcss.instrument = SPIRE var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Opened CUSGUI with PACS hscphs2@heropl02/home/hscphs2/otherSetups> cusgui& [1] 31039 [1] + Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/PACS> Sep 18, 2009 3:58:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 3:58:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 3:58:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 3:58:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 3:58:24 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument TAKE NOTE : Instrument above must be PACS if you want to work with the PACS instrument model. 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Sep 18, 2009 3:59:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 3:59:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 3:59:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 3:59:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 3:59:40 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Sep 18, 2009 4:00:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:00:02 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:00:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:00:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:00:09 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_CCS_MOC3_200908141600 6(d) Import the new Instrument CUS & Cal tables into the DB Import HIFI_FULL_20 Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/PACS> cus -m "upload PACS_MC_23AST mission config" -import PACS_MC_ASTR_CoP_PV_2009-09-18A_FULL_23_0_CUS.def -importcaltables PACS_MC_ASTR_CoP_PV_2009-09-18A_FULL_23_0_CUS_CAL.xml Sep 18, 2009 4:03:11 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:03:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:03: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 18, 2009 4:03:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:03:35 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 18, 2009 4:03:35 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 18, 2009 4:03:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:03:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:03:39 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_CoP_PV_2009-09-18A_FULL_23_0_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered OK 6(e) GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. If No Differences found then proceed to the Next Step. 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS_MC_23AST OK 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/delivery/OD0133/PACS/PACS_FULL_1> missetup -addconfig MC_H21_P23AST_S29 Sep 18, 2009 4:23:03 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:23:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:23: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 18, 2009 4:23:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:23:04 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Sep 18, 2009 4:23:04 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H21_P23AST_S29" 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 PACS Instrument Model into the Mission Configuration. Run CUSGUI >cusgui& Select "ADD Instrument Model to a Mission Configuration" and select the correct Mission Config. [hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133/PACS/PACS_FULL_1> cusgui& [1] 10583 [1] + Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133/PACS/PACS_FULL_1> Sep 18, 2009 4:23:46 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:23:47 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:23:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:23:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:23:48 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 18, 2009 4:24:18 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P23AST_S29" Sep 18, 2009 4:24:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:24:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:24:44 PM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE NEW PACS INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. 7. Steps to Import the OLD SPIRE Instrument model into the MC a.Set Instrument Model = SPIRE 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 #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/delivery/OD0133/PACS/PACS_FULL_1> cusgui& [1] 10673 [1] + Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0133/PACS/PACS_FULL_1> Sep 18, 2009 4:26:14 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:26:15 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:26: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 18, 2009 4:26:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:26:15 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument TAKE NOTE : Instrument above must be SPIRE if you want to work with the SPIRE instrument model. OK 7(c) Run the duration script for the SPIRE instrument Run the duration script for OD 130 delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/SPIRE> diff SPIRE_harness_duration_summary_20090918_16h30m41s.log SPIRE_Duration.txt No Differences found. This confirms the Instrument model contents is consistent with the SPIRE last Mission Configuration. 7(d) Import into the new Mission Configuration OPENED CUSGUI FOR THE SPIRE DELIVERY ADDED SPIRE MODEL TO THE NEW MISSION CONFIG - hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/SPIRE> cusgui& [1] 12554 [1] + Running cusgui hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/SPIRE> Sep 18, 2009 4:31:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:31:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:31:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:31:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:31:40 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 18, 2009 4:32:08 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P23AST_S29" S TAKE NOTE : When SPIRE is added to the Mission Configuration, it logged in the Cusgui terminal log (as can be seen above) ================== 8. Steps to Import the OLD HIFI Instrument model into the MC a.Set Instrument Model = HIFI & OBDB/STPF properties b.Check with CUSGUI c.Run the duration script for the PACS instrument d.Import into the new Mission Configuration 8(a) Set Instrument Model = HIFI & OBDB/STPF properties Set Instrument model = HIFI #Comment out next two for PACS only hcss.mps.obdb_file = OBDB_4_0_B004_20090325.csv hcss.mps.stpf_file = STPF_00002_20090324.csv #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT 8(b) Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/SPIRE> cusgui Sep 18, 2009 4:34:12 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:34:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:34: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 18, 2009 4:34:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:34:13 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument 8(c) Run the duration script for the HIFI instrument Run the duration script of OD86 against the HIFI Instrument Model in my session : hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/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_P23AST_S29/HIFI> ls duration.sh* HIFI_DUR_OD0086_3_0.txt HIFI_SSF_OD0086_3_0.ssf HIFI_AOR_OD0086_3_0.aor HIFI_ICP_OD0086_3_0.icp OD0086_HIFI_FULL_3_20090802.tar HIFI_AOR_OD0086.aor HIFI_POS_OD0086_3_0.pos summary_OD0086.log HIFI_AOR_OD86.aor HIFI_Readme_OD0086_3_0.txt summary_OD86.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/HIFI> ls -ltr total 15272 -rwxr-xr-x 1 hscphs2 herschel 2678 Jul 10 10:03 duration.sh* -rw-r--r-- 1 hscphs2 herschel 12850 Aug 2 08:39 HIFI_SSF_OD0086_3_0.ssf -rw-r--r-- 1 hscphs2 herschel 1857478 Aug 2 08:39 HIFI_POS_OD0086_3_0.pos -rw-r--r-- 1 hscphs2 herschel 118292 Aug 2 08:39 HIFI_AOR_OD86.aor -rw-r--r-- 1 hscphs2 herschel 118292 Aug 2 08:39 HIFI_AOR_OD0086.aor -rw-r--r-- 1 hscphs2 herschel 118292 Aug 2 08:39 HIFI_AOR_OD0086_3_0.aor -rw-r--r-- 1 hscphs2 herschel 2552 Aug 2 08:39 HIFI_Readme_OD0086_3_0.txt -rw-r--r-- 1 hscphs2 herschel 2961784 Aug 2 08:39 HIFI_ICP_OD0086_3_0.icp -rw-r--r-- 1 hscphs2 herschel 960 Aug 2 08:39 HIFI_DUR_OD0086_3_0.txt -rw-r--r-- 1 hscphs2 herschel 10373120 Aug 2 11:05 OD0086_HIFI_FULL_3_20090802.tar -rw-r--r-- 1 hscphs2 herschel 961 Sep 13 17:11 summary_OD0086.log -rw-r--r-- 1 hscphs2 herschel 961 Sep 18 16:37 summary_OD86.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/HIFI> diff summary_OD86.log HIFI_DUR_OD0086_3_0.txt 1d0 < No differences 8(d) Import into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/HIFI> Sep 18, 2009 4:38:53 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:38:54 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:38:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:38:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:38:55 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 18, 2009 4:39:22 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P23AST_S29" Sep 18, 2009 4:39:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:39:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:40:08 PM herschel.cus.gui.CusEditor exit INFO: Quitting. ==================== 9. Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophander to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H21_P23AST_S29 Source the propHandler Software : hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/HIFI> source ~/otherSetups/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/icchsc/mission_config/MC_H21_P23AST_S29/HIFI> TAKE NOTE : If there is a newer PHS software version in the otherSetups directory then source that new version. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P23AST_S29/HIFI> Sep 18, 2009 4:42:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 18, 2009 4:42:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 18, 2009 4:42:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 18, 2009 4:42:07 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 18, 2009 4:42:07 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Sep 18, 2009 4:42:07 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 25 Sep 18, 2009 4:42:07 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Sep 18, 2009 4:42:07 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P23AST_S29" Sep 18, 2009 4:42:14 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 6734 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration. OK 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. Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ /home/hscphs2/icchsc/HSpot_files/MC_H21_P23AST_S29 /home/hscphs2/icchsc/HSpot_files/MC_H21_P23AST_S29 Called the same name as the Mission Configuration i.e. Exported all the HSpot files to this folder : /home/hscphs2/icchsc/HSpot_files/MC_H21_P23AST_S29 Example of the last entry in the log : Sep 18, 2009 4:44:10 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P23AST_S29/HifiManCmd_HIFI_Rescue_to_switched_offGen.prop 11. Do the Check for a new cus script for Eva Do the following : hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P23AST_S29> ls *.prop > MC_H21_P23AST_S29.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P23AST_S29> diff MC_H21_P23AST_S29.txt ../MC_H21_P22_S29_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 12. Final Jboss Activities Log into Jboss #2 [rlorente@herl21 ~]$ ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Thu Sep 17 17:54:04 2009 from herl36.net4.lan herjbo02.esac.esa.int/home/hsc_phs/.hcss> cd herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02 PHS: Using BUILDNUM 578 PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 herjbo02.esac.esa.int/home/hsc_phs> stopJbossTest set old=/home/hsc_phs chdir /usr/local/software/jboss/jboss-3.2.6_0_6_5/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1199 Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion herjbo02.esac.esa.int/home/hsc_phs> Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/home/hsc_phs> mkdir fileHolder_ops_MC_H21_P23AST_S29 copied HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P23AST_S29> scp *.* hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H21_P23AST_S29/ 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!! #MARK & CHARO TIME ESTIMATOR hcss.phs.timeEstimatorVersion=MARK-CHARO-USE-ONLY-MC_H21_P23AST_S29_090918 #MARK & CHARO MISSION CONFIG hcss.ccm.mission.config = MC_H21_P23AST_S29 #MARK & CHARO DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H21_P23AST_S29 Finally Restart the Test Jboss. > startJbossTest LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.