1. Delivery Notes PACS Delivery note - 11th September 09 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of PACS PV OD0126 tar file onto the CVS server. 1. Delivery file, directory & Mission Configuration issues (a) OD tar file name : OD0126_PACS_FULL_2_090911.tar (b) CVS server directory : develop/data/observingmodes/hscpv/od126, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 21.0. 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 884. (b) Has the TM limit been exceeded? NO. 3. MPS Input file issues (a) Has a new orbit file been used for the first time in this OD? YES, H20090909_001.LOE. (b) Has a new SIAM file been used for the first time in this OD? NO, SIAM file 0122_0001.SIAM (c) Has a new HPSDB file been used for the first time in this OD? NO (d) Is the avoidance set-up default? NO, Mars avoidance area has been set equal to 0. 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? NO (d) TM limit exceeded - possibility of dump over two DTCPs? NO, the expected TM size is 764.27MB (e) ICC to add anything specific to this OD which HSC & MOC should be aware of. The delivery contains the following PACS PV calibration blocks: * PVMechChop 2.3.2A Chopper 1 kHz diagnostic HK to check that DECMEC control board in right T range (has to come first before the orbit prologue!) * PVSpecSetUp_orbit prologue classic (including signal stability monitoring during DTCP) * PVSpecAOTVal 5.2.4A SED scan parameters * PVSpecFPG 4.1.1G skew/offset verification on continuum and line * PVSpecFlux 4.3.8F RSRF measurement on Mars * 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) OD0126_PACS_FULL_2_090911.tar MC Version 21.0 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/otherSetups> source 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_P21_S28_PV/ 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_P20_S28_PV/ Configuration name shall be MC_H21_P21_S28_PV/ 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/mission_config> mkdir MC_H21_P21_S28_PV/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config> mkdir MC_H21_P21_S28_PV/HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config> mkdir MC_H21_P21_S28_PV/SPIRE Make also the delivery directory & subdirectories. hscphs2@heropl02/home/hscphs2/icchsc/delivery> mkdir OD0126 hscphs2@heropl02/home/hscphs2/icchsc/delivery> mkdir OD0126/PACS hscphs2@heropl02/home/hscphs2/icchsc/delivery> mkdir OD0126/PACS/PACS_FULL_2 hscphs2@heropl02/home/hscphs2/icchsc/delivery> mkdir OD0126/logs 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> cp MC_H21_P20_S28_PV/HIFI/* MC_H21_P21_S28_PV/HIFI/. hscphs2@heropl02/home/hscphs2/icchsc/mission_config> cp MC_H21_P20_S28_PV/SPIRE/* MC_H21_P21_S28_PV/SPIRE/. As the last Mission Configuration was called MC_H19_P13_S17_PV then go to that directory and copy across the contents of the SPIRE & PACS subdirectories into the equivalent subdirectories of the MC_H20_P13_S17_PV folder. 6.Steps to Import the new HIFI 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/OD0126> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0126> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0126> cvs co develop/data/observingmodes/hscpv/od126/OD0126_PACS_FULL_2_090911.tar U develop/data/observingmodes/hscpv/od126/OD0126_PACS_FULL_2_090911.tar Delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0126> cd PACS/PACS_FULL_2/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0126/PACS/PACS_FULL_2> cp ../../develop/data/observingmodes/hscpv/od126/OD0126_PACS_FULL_2_090911.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0126/PACS/PACS_FULL_2> ls OD0126_PACS_FULL_2_090911.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0126/PACS/PACS_FULL_2> tar -xvf OD0126_PACS_FULL_2_090911.tar PACS_MC_CoP_PV_2009-09-10A_FULL_21_0_CUS.def PACS_MC_CoP_PV_2009-09-10A_FULL_21_0_CUS_CAL.xml PACS_AOR_OD0126_2_0.aor PACS_DUR_OD0126_compare_2_0.txt PACS_POS_OD0126_2_0.pos PACS_ICP_OD0126_2_0.icp PACS_SSF_OD0126_2_0.ssf PACS_Readme_OD0126_2_0.txt 2createOBSMODtable.sh TAKE NOTE : The above steps are to be copied into the PACS BASIC TEMPLATE LOG FILE MC directory hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV> cp ../../delivery/OD0126/PACS/PACS_FULL_2/* PACS/. . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/PACS> ls 2createOBSMODtable.sh* OD0126_PACS_FULL_2_090911.tar PACS_AOR_OD0126_2_0.aor PACS_DUR_OD0126_compare_2_0.txt PACS_ICP_OD0126_2_0.icp PACS_MC_CoP_PV_2009-09-10A_FULL_21_0_CUS_CAL.xml PACS_MC_CoP_PV_2009-09-10A_FULL_21_0_CUS.def PACS_POS_OD0126_2_0.pos PACS_Readme_OD0126_2_0.txt PACS_SSF_OD0126_2_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/icchsc/mission_config/MC_H21_P21_S28_PV/PACS> cusgui Sep 11, 2009 1:52:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 1:52:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 1:52: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 11, 2009 1:52:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 1:52:03 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.inst TAKE NOTE : Instrument above must be PACS 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Sep 11, 2009 1:53:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 1:53:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 1:53:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 1:53:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 1:53:19 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Sep 11, 2009 1:53:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 1:53:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 1:53: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 11, 2009 1:53:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 1:53:41 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 PACS_FULL_2 Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/PACS> cus -m "upload PACS_MC_21 mission config" -import PACS_MC_CoP_PV_2009-09-10A_FULL_21_0_CUS.def -importcaltables PACS_MC_CoP_PV_2009-09-10A_FULL_21_0_CUS_CAL.xml Sep 11, 2009 1:59:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 1:59:07 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 1:59: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 11, 2009 1:59:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 1:59:29 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 11, 2009 1:59:29 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 11, 2009 1:59:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 1:59:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 1:59:32 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_CoP_PV_2009-09-10A_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 HIFI. 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 HIFI DELIVERY In the Comment field, refer to PACS_MC_21 TAKE NOTE : It is very important that you commit the delivery as defined above. OK 6(g) Create the new Mission Configuration name in the DB hscphs2@heropl02/home/hscphs2/icchsc/mission_config> missetup -addconfig MC_H21_P21_S28_PV Sep 11, 2009 2:19:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 2:19:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 2:19:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:19:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:19:57 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Sep 11, 2009 2:19:57 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H21_P21_S28_PV" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" TAKE NOTE : Confirm the correct Mission Config Name has been created as shown in the last line above. OK 6(h) Import the New PACS Instrument Model into the Mission Configuration. ADDED PACS MODEL TO THE NEW MISSION CONFIGURATION MC_H21_P21_S28_PV Run CUSGUI >cusgui& Select "ADD Instrument Model to a Mission Configuration" and select the correct Mission Config. [1] + Running cusgui INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 11, 2009 2:21:24 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P21_S28_PV" 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 HIFI 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/mission_config> cusgui Sep 11, 2009 2:23:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 2:23:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 2:23:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:23:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:23:11 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. 7(c) Run the duration script for the SPIRE instrument hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/SPIRE> diff SPIRE_harness_duration_summary_20090911_14h27m31s.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 INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:43:43 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 11, 2009 2:44:01 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P21_S28_PV" 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 8(a) Set Instrument Model = HIFI & 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_P21_S28_PV/HIFI> cusgui Sep 11, 2009 2:45:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 2:45:57 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 2:45: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 11, 2009 2:45:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:45:58 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 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/HIFI> ./duration.sh 0086 next OD = 0086 -- 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_P21_S28_PV/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 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/HIFI> diff summary_OD0086.log HIFI_DUR_OD0086_3_0.txt 1d0 < No differences 8(d) Import into the new Mission Configuration Imported HIFI model into the new mission config hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P21_S28_PV/HIFI> Sep 11, 2009 2:52:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 2:52:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 2:52:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:52:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:52:07 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 11, 2009 2:52:24 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P21_S28_PV" Sep 11, 2009 2:52:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:52:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int S 8(e) Reset the OBDB/STPF properties ==================== 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_P21_S28_PV Source the propHandler Software : 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 TAKE NOTE : If there is a newer PHS software version in the otherSetups directory then source that new version. [1] + Running propHandler hscphs2@heropl02/home/hscphs2/otherSetups> Sep 11, 2009 2:55:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 11, 2009 2:55:41 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 11, 2009 2:55:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 11, 2009 2:55:41 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 11, 2009 2:55:41 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Sep 11, 2009 2:55:41 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 22 Sep 11, 2009 2:55:41 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Sep 11, 2009 2:55:41 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P21_S28_PV" TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration. 10. Export the Hspot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same name as the Mission Configuration i.e. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H21_P21_S28_PV Exported all the HSpot files to this folder : Example of the last entry in the log : ScanModeFastDBSGen.prop Sep 11, 2009 2:58:32 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P21_S28_PV/HifiManCmd_HIFI_Rescue_to_switched_offGen.prop 11. Do the Check for a new cus script for Eva Do the following : hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P21_S28_PV> ls *.prop > & MC_H21_P21_S28_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/MC_H21_P21_S28_PV> diff ../MC_H21_P20_S28_PV/MC_H21_P20_S28_PV.txt MC_H21_P21_S28_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. 12. Final Jboss Activities Log into Jboss #2 [rlorente@herl21 ~]$ ssh -X hsc_phs@herjbo02 Source the correct Environment : herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02 PHS: Using BUILDNUM 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_P21_S28_PV copied HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P21_S28_PV> scp *.* hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H21_P21_S28_PV/ Next Update the properties file : herjbo02.esac.esa.int/home/hsc_phs/.hcss> vi HCSS_PHS_TEST_herjbo02_0_6_6.props Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! ##LARRY & MARK & CHARO TIME ESTIMATOR hcss.phs.timeEstimatorVersion=LARRY/MARK/CHARO -USE-ONLY-PV_MC_H21_P21_S28_PV_090911 #LARRY & MARK & CHARO MISSION CONFIG hcss.ccm.mission.config = MC_H21_P21_S28_PV #LARRY & MARK & CHARO DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H21_P21_S28_PV Finally Restart the Test Jboss. > startJbossTest LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.