HSC-PROC-UPLC-0004 : Standard Mission Config Template 1. Delivery Notes PACS Delivery note - 21st Oct 09 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of PACS PV OD0166 tar file onto the CVS server. 1. Delivery file, directory & Mission Configuration issues (a) OD tar file name: OD0166_PACS_FULL_1_091021.tar (b) CVS server directory: develop/data/observingmodes/hscpv/od166, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 32.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 1027. (b) Has the TM limit been exceeded? NO, the expected TM size is 1170.39MB. 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? NO (d) TM limit exceeded - possibility of dump over two DTCPs? NO, the expected TM size is 1170.39MB. (e) ICC to add anything specific to this OD which HSC & MOC should be aware of. The observing programme consists of one AOR extracted from a PACS SPEC SDP programme executed on comet C/2006 W3 Christensen to be used as a PACS spectrometer AOT validation observation. The label of the AOR used in this delivery is: SDP_pharto01_3-PACS dedicated line spectroscopy It has to be replaced by the AOR from the HSC SDP database. No change to original configuration is needed. Three SSOs are scheduled on this OD: comet 217P/LINEAR (NAIFID 1000345) comet C/2006 W3 Christensen (NAIFID 1002430) planet Neptune (NAIFID 899) The delivery contains the following PACS PV calibration blocks: * PVSpecSetup CSs on * PVSpecFlux 343A flux stability * PVSpecFPG 411J 7x7 raster * SDPSpec on comet C/2006 W3 Christensen * PVSpecAotVal 523B range spectroscopy * PVSpecAotVal 523C non-chopped SED spectroscopy * PVSpecAotVal 524F chopped SED spectroscopy * PVSpecSetup orbit epilogue Please acknowledge receipt of the e-mail and the delivery. Kind regards, Markus Nielbock. Take Note of the Tar File & the New MC name (for MPS email and for steps below) OD0166_PACS_FULL_1_091021.tar MC 32.0 ASTR 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_HPhase3_P32ASTR_S34ASTR_SDP 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP> ls HIFI/ logs/ PACS/ SPIRE/ Make also the delivery directory & subdirectories. hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0166> ls logs/ PACS/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0166> ls PACS PACS_FULL_1/ 5. Copy across the contents of the HIFI & SPIRE 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/MC_HPhase3_P32ASTR_S34ASTR_SDP/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_HPhase3_P31ASTR_S34ASTR_SDP/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/HIFI> ls cus-defdur.sh* HIFI_Phase3b_Durations.txt ICC_OBSMODES_HIFI_115.tar ICC_OBSMODES_HIFI_115.xml default-durations.dat ICC_OBSMODES_HIFI_115.def ICC_OBSMODES_HIFI_115.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_HPhase3_P31ASTR_S34ASTR_SDP/SPIRE/* . [1] + Running nedit MC_HPhase3_P32ASTR_S34ASTR_SDP.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> ls OD0159_SPIRE_FULL_1_20091012.tar SPIRE_harness_duration_summary_20091020_14h25m00s.log SPIRE_cus_scripts.txt SPIRE_harness_duration_summary_20091020_15h02m30s.log SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv52_FULL_34_0_CUS_CAL.xml SPIRE_Duration.txt SPIRE_MC_ASTR_pv52_FULL_34_0_CUS.def SPIRE_harness_duration_summary_20091013_14h24m23s.log SPIRE_Readme_OD0159_1_0.txt 6.Steps to Import the new PACS Instrument model into a new MC 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0165/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0165/PACS/PACS_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/OD0166/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/hscpv/od166/OD0166_PACS_FULL_1_091021.tar U develop/data/observingmodes/hscpv/od166/OD0166_PACS_FULL_1_091021.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0166/PACS/PACS_FULL_1> cp develop/data/observingmodes/hscpv/od166/OD0166_PACS_FULL_1_091021.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0166/PACS/PACS_FULL_1> ls develop/ OD0166_PACS_FULL_1_091021.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0166/PACS/PACS_FULL_1> tar -xvf OD0166_PACS_FULL_1_091021.tar PACS_MC_CoP_PV_2009-10-21A_FULL_32_0_CUS.def PACS_MC_CoP_PV_2009-10-21A_FULL_32_0_CUS_CAL.xml PACS_AOR_OD0166_1_0.aor PACS_DUR_OD0166_compare_1_0.txt PACS_POS_OD0166_1_0.pos PACS_ICP_OD0166_1_0.icp PACS_SSF_OD0166_1_0.ssf PACS_Readme_OD0166_1_0.txt 2createOBSMODtable.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0165/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_HPhase3_P31ASTR_S34ASTR_SDP/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 6(b) Set the Instrument Model & check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0166/PACS/PACS_FULL_1> Oct 21, 2009 3:49:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 3:49:07 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 3:49:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:49:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:49:08 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Oct 21, 2009 3:49:25 PM herschel.cus.gui.CusEditor exit INFO: Quitting. 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Oct 21, 2009 3:50:04 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 3:50:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 3:50:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:50:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:50:14 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Oct 21, 2009 3:50:19 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 3:50:20 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 3:50:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:50:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:50:26 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables OK 6(d) Import the new Instrument CUS & Cal tables into the DB Import hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/PACS> cus -m "upload PACS MC32ASTR" -import PACS_MC_CoP_PV_2009-10-21A_FULL_32_0_CUS.def -importcaltables PACS_MC_CoP_PV_2009-10-21A_FULL_32_0_CUS_CAL.xml Oct 21, 2009 3:53:47 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 3:53:48 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 3:53:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:53:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:54:11 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Oct 21, 2009 3:54:11 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Oct 21, 2009 3:54:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:54:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 3:54:15 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_CoP_PV_2009-10-21A_FULL_32_0_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered 6(e) GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. Done 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY Done 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 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/PACS> missetup -addconfig MC_HPhase3_P32ASTR_S34ASTR_SDP Oct 21, 2009 4:01:32 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:01:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:01:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:01:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:01:33 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Oct 21, 2009 4:01:34 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_HPhase3_P32ASTR_S34ASTR_SDP" 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. 6(h) Import the New PACS Instrument Model into the Mission Configuration. Run CUSGUI >cusgui& Select "Create Instrument Model in a Configuration" and select the correct Mission Config. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/PACS> Oct 21, 2009 4:02:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:02:09 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:02:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:02:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:02:10 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Oct 21, 2009 4:02:26 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P32ASTR_S34ASTR_SDP" Oct 21, 2009 4: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 Oct 21, 2009 4:02:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:02:56 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 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 #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_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> Oct 21, 2009 4:04:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:04:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:04:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:04:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:04:06 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Oct 21, 2009 4:04:20 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be SPIRE if you want to work with the SPIRE instrument model. 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Oct 21, 2009 4:05:19 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:05:20 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:05:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:05:20 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:05:28 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Oct 21, 2009 4:05:33 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:05:34 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:05:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:05:39 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 7(d) Import the new Instrument CUS & Cal tables into the DB Import hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> cus -m "upload SPIRE MC34ASTR" -import SPIRE_MC_ASTR_pv52_FULL_34_0_CUS.def -importcaltables SPIRE_MC_ASTR_pv52_FULL_34_0_CUS_CAL.xml Oct 21, 2009 4:06:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:06:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:06:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:06:54 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Oct 21, 2009 4:06:54 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Oct 21, 2009 4:06:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:06:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:06:57 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv52_FULL_34_0_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered 7(e) Run the duration script for the SPIRE instrument Run the duration script for OD 159 delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> ls -ls total 4076 2016 -rw-r--r-- 1 hscphs2 herschel 2058240 Oct 12 15:58 OD0159_SPIRE_FULL_1_20091012.tar 4 -rw-r--r-- 1 hscphs2 herschel 1678 Oct 21 16:10 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Oct 12 15:43 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 4413 Oct 12 15:43 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 4413 Oct 13 14:24 SPIRE_harness_duration_summary_20091013_14h24m23s.log 8 -rw-rw-rw- 1 hscphs2 herschel 4413 Oct 20 14:25 SPIRE_harness_duration_summary_20091020_14h25m00s.log 8 -rw-rw-rw- 1 hscphs2 herschel 4413 Oct 20 15:02 SPIRE_harness_duration_summary_20091020_15h02m30s.log 8 -rw-rw-rw- 1 hscphs2 herschel 4413 Oct 21 16:13 SPIRE_harness_duration_summary_20091021_16h13m49s.log 252 -rw-r--r-- 1 hscphs2 herschel 251857 Oct 12 15:56 SPIRE_MC_ASTR_pv52_FULL_34_0_CUS_CAL.xml 1756 -rw-r--r-- 1 hscphs2 herschel 1792227 Oct 12 15:56 SPIRE_MC_ASTR_pv52_FULL_34_0_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 3145 Oct 12 15:54 SPIRE_Readme_OD0159_1_0.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20091021_16h13m49s.log No Differences found. This confirms the Instrument model contents is consistent with the SPIRE last Mission Configuration. 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE SPIRE DELIVERY Done 7(g) 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_HPhase3_P32ASTR_S34ASTR_SDP/SPIRE> Oct 21, 2009 4:17:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:17:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:17:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:17:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:17:51 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Oct 21, 2009 4:18:02 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P32ASTR_S34ASTR_SDP" Oct 21, 2009 4:18:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:18:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:19:00 PM herschel.cus.gui.CusEditor exit 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 #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_HPhase3_P32ASTR_S34ASTR_SDP/HIFI> Oct 21, 2009 4:20:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:20:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:20:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:20:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:20:40 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Oct 21, 2009 4:20:48 PM herschel.cus.gui.CusEditor exit INFO: Quitting. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/HIFI> ls cus-defdur.sh* HIFI_Phase3b_Durations.txt ICC_OBSMODES_HIFI_115.tar ICC_OBSMODES_HIFI_115.xml default-durations.dat ICC_OBSMODES_HIFI_115.def ICC_OBSMODES_HIFI_115.txt 8(c) Run the duration script for the HIFI instrument Run the duration script against the HIFI Instrument Model in my session : **** We do not do this step because we know from previous experience that the durations DO NOT agree, thus this step is not informative **** hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P30ASTR_S27ASTR_SDP/HIFI> ./cus-defdur.sh>HIFI_durations.txt DIFF bhscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P30ASTR_S27ASTR_SDP/HIFI> ls -ltr total 5124 -rwxr-xr-x 1 hscphs2 herschel 654 Feb 13 2009 cus-defdur.sh* -rw-r--r-- 1 hscphs2 herschel 1763391 Mar 12 2009 ICC_OBSMODES_HIFI_115.def -rw-r--r-- 1 hscphs2 herschel 771921 Mar 12 2009 ICC_OBSMODES_HIFI_115.xml -rw-r--r-- 1 hscphs2 herschel 846 Mar 12 2009 ICC_OBSMODES_HIFI_115.txt -rw-r--r-- 1 hscphs2 herschel 27391 Mar 12 2009 default-durations.dat -rw-r--r-- 1 hscphs2 herschel 2570240 Mar 12 2009 ICC_OBSMODES_HIFI_115.tar -rw-r--r-- 1 hscphs2 herschel 34726 Oct 4 13:23 HIFI_Phase3b_Durations.txt -rw-r--r-- 1 hscphs2 herschel 34726 Oct 9 21:12 HIFI_durations.txt Clearly HIFI_durations.txt and default-durations.dat are different, as they were in the first MC_HPhase3_P27ASTR_S27ASTR_SDP/!!! 8(d) Import into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P32ASTR_S34ASTR_SDP/HIFI> Oct 21, 2009 4:21:35 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:21:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:21:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:21:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:21:36 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Oct 21, 2009 4:21:53 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P32ASTR_S34ASTR_SDP" Oct 21, 2009 4:22:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:22:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:22:25 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_HPhase3_P32ASTR_S34ASTR_SDP Source the propHandler Software : hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v1.1.3_phs setHcssExtLibs_csh:INFO:Variable HCSS_DIR set to [/herschel/software/hcss/hcss_1.1.3_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. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_HPhase3_P32ASTR_S34ASTR_SDP> Oct 21, 2009 4:26:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Oct 21, 2009 4:26:05 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Oct 21, 2009 4:26:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Oct 21, 2009 4:26:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Running CDH.getObsProgrammes() Oct 21, 2009 4:26:06 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Oct 21, 2009 4:26:06 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 24 Oct 21, 2009 4:26:06 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Oct 21, 2009 4:26:06 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P32ASTR_S34ASTR_SDP" Oct 21, 2009 4:26:12 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 6324 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/ Oct 21, 2009 4:27:39 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_HPhase3_P32ASTR_S34ASTR_SDP/HifiSScanProcLoadChopNoRefGen.prop Oct 21, 2009 4:27:39 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_HPhase3_P32ASTR_S34ASTR_SDP/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new cus script for Eva Do the following : hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_HPhase3_P31ASTR_S34ASTR_SDP> ls *.prop > & MC_HPhase3_P32ASTR_S34ASTR_SDP.txt Now do a diff between this new txt file and the one generated with the last Mission configuration. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_HPhase3_P31ASTR_S34ASTR_SDP.txt MC_HPhase3_P32ASTR_S34ASTR_SDP.txt No difference If there is a difference inform Jose, 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 [mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02 Source the correct Environment : herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02 PHS: Using BUILDNUM 585 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 Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/home/hsc_phs> mkdir fileHolder_ops_MC_HPhase3_P30ASTR_S27ASTR_SDP 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. herjbo02.esac.esa.int/home/hsc_phs> mkdir fileHolder_ops_MC_HPhase3_P32ASTR_S34ASTR_SDP 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=MC_HPhase3_P32ASTR_S34ASTR_SDP_091021 #MARK & CHARO MISSION CONFIG hcss.ccm.mission.config = MC_HPhase3_P32ASTR_S34ASTR_SDP #MARK & CHARO DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_HPhase3_P32ASTR_S34ASTR_SDP Finally Restart the Test Jboss. > startJbossTest LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.