HSC-PROC-UPLC-0004 : Standard Mission Config Template 1. Delivery Notes PACS Delivery note - 13th Nov 09 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of PACS PV OD0191 tar file onto the CVS server. We were in telephone contact with Mark and Charo before and agreed that part of the delivery could be put on OD190, if this facilitates the scheduling. We had a telecon with Mark, Charo, Tony and Carlos Eiroa agreeing in the end that we would deliver, within the available time budget, 2 more mini scanmap AORs on HD 15371. (see extra PACS_AOR_OD0191_HIP15371_miniscanmap.aor file below). The delivery addresses the following 2 PV Planning meeting AIs: 1) AI: PVSched#20_111109_4: 4h for repetition of spectrometer raster map on Neptune 2) AI: PVSched#20_111109_5: 4h for alternative photometer PS AOT in scan map mode The total time of the AORs delivered is 07:36:47. (Mark was informed beforehand by phone that the tar files are available on the CVS server.) 1. Delivery file, directory & Mission Configuration issues (a) OD tar file name : 1) OD0191_PACS_FULL_1_091113.tar 2) PACS_AOR_OD0191_HIP15371_miniscanmap.aor (b) CVS server directory : develop/data/observingmodes/hscpv/od191, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 35.0 It is an ASTR MC updating spectrometer standard CUS code/CAL files 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 1066 (only for the PACS PV part). (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, (H20091111_0001.LOE, from OD188 onwards) (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? n/a for the AORs delivered (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 406.85MB (only PACS PV AORs in POS file) (e) ICC to add anything specific to this OD which HSC & MOC should be aware of. The delivery is not a full delivery in the respect, that we did neither a full planning of the OD nor did we put in engineering AORs to set up the OD properly. These have to come from HSC together with the additional AORs to fill the OD. The AORs of this delivery can be put also on OD190 and distributed over OD191 to minimize slew overheads with the only following constraint: We require scheduling the photmetry scan maps (designated with 63 in the AOR label) and cross scans (designated with 117 in the AOR label) of the same observational setup together. Example: PVPhotAOTVal_514P_StdScan63_6legs_grn_gamDra_0001 PVPhotAOTVal_514P_StdScan117_6legs_grn_gamDra_0001 (We did not use concatenation). The delivery contains one spectroscopy AOR on planet Neptune which can be scheduled in case of mixed photometry and spectroscopy OD. The delivery contains the following PACS PV calibration blocks: * PVPhotAOTVal 5.1.4P on gam Dra - executing the mini scan map scenario as descriped in PACS PS photometery AOT release note: scans and cross scans under 63 and 117 deg array orientation 3.9' (length of array diagonal) and 3' (on-array) scan legs 16 legs with 2" separation 8 legs with 4" separation 6 legs with 5" separation * PVPhotAOTVal 5.1.4P on SDSS J1148+5251 expecting release of standard PS SDP AOR by K. Meisenheimer for comparison. * PVPhotAOTVal 5.1.4P on HIP 7978 expecting release of standard PS SDP AOR by C. Eiroa for comparison * PVPhotAOTVal 5.1.4P on HIP 15371 for comparison with OD120 standard PS AOTVAL AOR on same source * PVSpecAotVal 5.2.1G to be repeated 5x5 map on Neptune 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) OD0191_PACS_FULL_1_091113.tar MC 35.0 ASTR 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 1.2.2 (Always use the most recent HCSS Software version) PHS SOFTWARE = 1.2.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.2.2 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_P35ASTR_S34ASTR_SDP 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP> ls HIFI/ logs/ PACS/ SPIRE/ Make also the delivery directory & subdirectories. hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0191> ls logs/ PACS/ 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_P35ASTR_S34ASTR_SDP/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_HPhase3_P34ASTR_S34ASTR_SDP/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_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_P35ASTR_S34ASTR_SDP/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_HPhase3_P34ASTR_S34ASTR_SDP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/SPIRE> ls OD0159_SPIRE_FULL_1_20091012.tar SPIRE_harness_duration_summary_20091028_19h09m33s.log SPIRE_cus_scripts.txt SPIRE_harness_duration_summary_20091028_19h28m25s.log SPIRE_CUS_THCP.py SPIRE_harness_duration_summary_20091103_18h24m51s.log SPIRE_Duration.txt SPIRE_MC_ASTR_pv52_FULL_34_0_CUS_CAL.xml SPIRE_harness_duration_summary_20091013_14h24m23s.log SPIRE_MC_ASTR_pv52_FULL_34_0_CUS.def SPIRE_harness_duration_summary_20091020_14h25m00s.log SPIRE_Readme_OD0159_1_0.txt SPIRE_harness_duration_summary_20091020_15h02m30s.log 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/OD0190/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0190/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/OD0190/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/hscpv/od191/OD0191_PACS_FULL_1_091113.tar U develop/data/observingmodes/hscpv/od191/OD0191_PACS_FULL_1_0911113.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0190/PACS/PACS_MC_ASTR> cp develop/data/observingmodes/hscpv/od191/OD0191_PACS_MC_ASTR_FULL_1_091113.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0190/PACS/PACS_MC_ASTR> tar -xvf OD0191_PACS_MC_ASTR_FULL_1_091113.tar PACS_MC_ASTR_CoP_PV_2009-11-03B_FULL_34_0_CUS.def PACS_MC_ASTR_CoP_PV_2009-11-03B_FULL_34_0_CUS_CAL.xml PACS_Readme_OD0191_1_0.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0190/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/PACS> ls 2createOBSMODtable.sh* PACS_MC_ASTR_CoP_PV_2009-11-12A_FULL_35_0_CUS_CAL.xml OD0191_PACS_FULL_1_091113.tar PACS_MC_ASTR_CoP_PV_2009-11-12A_FULL_35_0_CUS.def PACS_AOR_OD0191_1_0.aor PACS_POS_OD0191_1_0.pos PACS_AOR_OD0191_HIP15371_miniscanmap.aor PACS_Readme_OD0191_1_0.txt PACS_DUR_OD0191_compare_1_0.txt PACS_SSF_OD0191_1_0.ssf PACS_ICP_OD0191_1_0.icp #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/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/PACS> Nov 13, 2009 5:44:03 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 5:44:04 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 5:44:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:44:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:44:05 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Nov 13, 2009 5:44:19 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_P35ASTR_S34ASTR_SDP/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Nov 13, 2009 5:44:41 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 5:44:42 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 5:44:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:44:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:44:52 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Nov 13, 2009 5:45:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 5:45:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 5:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:45:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:45:13 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_P35ASTR_S34ASTR_SDP/PACS> cus -m "upload PACS MC35ASTR" -import PACS_MC_ASTR_CoP_PV_2009-11-12A_FULL_35_0_CUS.def -importcaltables PACS_MC_ASTR_CoP_PV_2009-11-12A_FULL_35_0_CUS_CAL.xml Nov 13, 2009 5:47:11 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 5:47:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 5:47:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:47:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:47:34 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Nov 13, 2009 5:47:34 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Nov 13, 2009 5:47:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:47:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 5:47:37 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_CoP_PV_2009-11-12A_FULL_35_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. No durations to check 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_P35ASTR_S34ASTR_SDP/PACS> missetup -addconfig MC_HPhase3_P35ASTR_S34ASTR_SDP Nov 13, 2009 6:03:36 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:03:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:03:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:03:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:03:38 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Nov 13, 2009 6:03:38 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_HPhase3_P35ASTR_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_P35ASTR_S34ASTR_SDP/PACS> Nov 13, 2009 6:04:00 PM hersche l.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:04:00 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:04:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:04:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:04:01 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Nov 13, 2009 6:05:01 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P35ASTR_S34ASTR_SDP" Nov 13, 2009 6:05:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:05:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:06:30 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_P35ASTR_S34ASTR_SDP/SPIRE> Nov 13, 2009 6:10:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:10:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:10:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:10:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:10:03 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Nov 13, 2009 6:10:11 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_P35ASTR_S34ASTR_SDP/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Nov 13, 2009 6:10:39 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:10:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:10:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:10:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:10:48 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Nov 13, 2009 6:10:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:10:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:10:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:10:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:11:03 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_P35ASTR_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 Nov 13, 2009 6:12:16 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:12:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:12:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:12:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:12:31 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Nov 13, 2009 6:12:31 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Nov 13, 2009 6:12:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:12:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:12:34 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_P35ASTR_S34ASTR_SDP/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/SPIRE> ls -ls total 4100 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 Nov 13 18:13 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 28 19:09 SPIRE_harness_duration_summary_20091028_19h09m33s.log 8 -rw-rw-rw- 1 hscphs2 herschel 4413 Oct 28 19:28 SPIRE_harness_duration_summary_20091028_19h28m25s.log 8 -rw-rw-rw- 1 hscphs2 herschel 4413 Nov 3 18:24 SPIRE_harness_duration_summary_20091103_18h24m51s.log 8 -rw-rw-rw- 1 hscphs2 herschel 4413 Nov 13 18:16 SPIRE_harness_duration_summary_20091113_18h16m54s.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_P31ASTR_S34ASTR_SDP/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20091020_15h02m30s.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20091113_18h16m54s.log 29c29 < Duration of SpirePhoto_Cal_PointJiggleId55 with default parameters = 427 --- > Duration of SpirePhoto_Cal_PointJiggleId55 with default parameters = 419 36,37c36,37 < Duration of SpirePhotoPointJiggle with default parameters = 425 < Duration of SpirePhotoPointLogic with default parameters = 425 --- > Duration of SpirePhotoPointJiggle with default parameters = 417 > Duration of SpirePhotoPointLogic with default parameters = 417 39c39 < Duration of SpirePhotoSmallLogic with default parameters = 311 --- > Duration of SpirePhotoSmallLogic with default parameters = 303 Same differences found as for the previous MC. This confirms that 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_P35ASTR_S34ASTR_SDP/SPIRE> Nov 13, 2009 6:19:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:19:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:19:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:19:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:19:11 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Nov 13, 2009 6:19:22 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P35ASTR_S34ASTR_SDP" Nov 13, 2009 6:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:19:51 PM herschel.cus.gui.CusEditor exit INFO: Quitting. 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_P35ASTR_S34ASTR_SDP/HIFI> Nov 13, 2009 6:20:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:20:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:20:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:20:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:20:58 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Nov 13, 2009 6:21:07 PM herschel.cus.gui.CusEditor exit INFO: Quitting. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Nov 13, 2009 6:21:28 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:21:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:21:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:21:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:21:39 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Nov 13, 2009 6:22:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:22:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:22:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:22:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:22:08 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_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_P35ASTR_S34ASTR_SDP/HIFI> cus -m "upload HIFI PHASE3" -import ICC_OBSMODES_HIFI_115.def -importcaltables ICC_OBSMODES_HIFI_115.xml Nov 13, 2009 6:23:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:23:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:23:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:23:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:23:35 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Nov 13, 2009 6:23:35 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Nov 13, 2009 6:23:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:23:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:23:41 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "ICC_OBSMODES_HIFI_115.xml" 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/!!! COMMITTED THE DELIVERY 8(d) Import into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_HPhase3_P35ASTR_S34ASTR_SDP/HIFI> Nov 13, 2009 6:25:32 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:25:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:25:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:25:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:25:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Nov 13, 2009 6:25:50 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P35ASTR_S34ASTR_SDP" Nov 13, 2009 6:26:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:26:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:26:29 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_P35ASTR_S34ASTR_SDP Source the propHandler Software : hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v1.2.0_phs setHcssExtLibs_csh:INFO:Variable HCSS_DIR set to [/herschel/software/hcss/hcss_1.2.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. hscphs2@heropl02/home/hscphs2> Nov 13, 2009 6:28:14 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 13, 2009 6:28:14 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 13, 2009 6:28:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 13, 2009 6:28:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Running CDH.getObsProgrammes() Nov 13, 2009 6:28:15 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Nov 13, 2009 6:28:15 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 21 Nov 13, 2009 6:28:15 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Nov 13, 2009 6:28:15 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_HPhase3_P35ASTR_S34ASTR_SDP" Nov 13, 2009 6:28:22 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 6953 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/ hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_HPhase3_P35ASTR_S34ASTR_SDP/ hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> cd MC_HPhase3_P35ASTR_S34ASTR_SDP/ Nov 13, 2009 6:31:38 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_HPhase3_P35ASTR_S34ASTR_SDP/HifiSScanProcLoadChopNoRefGen.prop Nov 13, 2009 6:31:38 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_HPhase3_P35ASTR_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_P35ASTR_S34ASTR_SDP> ls *.prop > & MC_HPhase3_P35ASTR_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_P34ASTR_S34ASTR_SDP.txt MC_HPhase3_P35ASTR_S34ASTR_SDP.txt NO DIFFERENCES 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_P35ASTR_S34ASTR_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. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_HPhase3_P35ASTR_S34ASTR_SDP> scp *.* hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_HPhase3_P35ASTR_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_P35ASTR_S34ASTR_SDP_091113 #hcss.phs.timeEstimatorVersion=MC_H21_P32_S39_PV_091113 #MARK & CHARO MISSION CONFIG hcss.ccm.mission.config = MC_HPhase3_P35ASTR_S34ASTR_SDP #hcss.ccm.mission.config = MC_H21_P32_S39_PV #MARK & CHARO DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_HPhase3_P35ASTR_S34ASTR_SDP #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H21_P32_S39_PV Finally Restart the Test Jboss. > startJbossTest LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.