1. Delivery note from PACS: 30th August 2009 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of PACS Astronomer PRE-release CUS backend for OD0120 tar file (OD0120_PACS_ASTR_FULL_1_090901.tar) onto the CVS server under develop/data/observingmodes/hscpv/od120, CVS version 1.1. This delivery corresponds to new Mission Configuration (Version 18.0). Please be aware of the following limitations as discussed during telecon Monday: AOT delivered: PacsPhoto observingmodes: ScanMap and PointSource Please acknowledge receipt of the e-mail and the delivery. Kind regards, Vanessa Doublier-Pritchard TAKE NOTE : Tar file Name OD0120_PACS_ASTR_FULL_1_090901.tar & MC Name 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 1.1.0 Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal_herjbo02 : PHS: Using BUILDNUM 534 & PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 When Jboss checked later in the procedure I obtained: PHS: Using BUILDNUM 578 PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account If the Environment has not yet been sourced then source it!! hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v1.1.0 3. What is the New Mission Configuration Name going to be?? Go to the mission_config directory and do an ls -ltr to see what is the last Mission Configuration generated. Take note also of the last email sent to the MPS group which contains the name and confirm it is the same name. Last Mission Config = MC_H21_P17_S27_PV/ PACS are delivering a new MC, so the new Mission Configuration name shall be MC_H21_P18_S27_PV 4. Make the directories in the /icchsc/mission_config (& in the delivery directory) Make the directory MC_H21_P18_S27_PV in the /icchsc/mission_config directory. Within this directory create the subdirectories : SPIRE, PACS, HIFI & logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV> ls HIFI/ logs/ PACS/ SPIRE/ This LOG file has been placed in the /logs directory and given the name MC_H21_P18_S27_PV.log. Make also the delivery directory & subdirectories. If the tar file is called OD0120_PACS_ASTR_FULL_1_090901.tar Then you create a directory in /home/hscphs2/icchsc/delivery called OD0120. Within this directory you create PACS/PACS_ASTR_FULL_1 subdirectories. Also create in this OD0120 directory a log file directory where the BASIC TEMPLATE Log file shall be placed. hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120> ls logs/ PACS/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120> cd PACS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS> mkdir PACS_ASTR_FULL_1 hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS> ls PACS_ASTR_FULL_1/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS> cd PACS_ASTR_FULL_1/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/logs> ls OD120_PACS_ASTR_FULL_1.log 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. As the last Mission Configuration was called MC_H21_P17_S27_PV/ then go to that directory and copy across the contents of the HIFI & SPIRE subdirectories into the equivalent subdirectories of the MC_H21_P17_S25_PV folder. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P17_S27_PV/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H21_P17_S27_PV/HIFI/*.* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P17_S27_PV/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H21_P17_S27_PV/SPIRE/*.* . Next remove in the HIFI & SPIRE subfolders all files which were created when you ran the HIFI & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> ls duration.sh* HIFI_DUR_OD0086_3_0.txt HIFI_Readme_OD0086_3_0.txt summary_OD86.log HIFI_AOR_OD0086_3_0.aor HIFI_ICP_OD0086_3_0.icp HIFI_SSF_OD0086_3_0.ssf HIFI_AOR_OD86.aor HIFI_POS_OD0086_3_0.pos OD0086_HIFI_FULL_3_20090802.tar hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> rm summary_OD86.log rm: remove regular file `summary_OD86.log'? y [1] + Running nedit MC_H21_P18_S27_PV.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> ls duration.sh* HIFI_DUR_OD0086_3_0.txt HIFI_Readme_OD0086_3_0.txt HIFI_AOR_OD0086_3_0.aor HIFI_ICP_OD0086_3_0.icp HIFI_SSF_OD0086_3_0.ssf HIFI_AOR_OD86.aor HIFI_POS_OD0086_3_0.pos OD0086_HIFI_FULL_3_20090802.tar SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> ls OD0117_SPIRE_FULL_1_20090902.tar SPIRE_Duration.txt SPIRE_MC_ASTR_pv43_FULL_27_0_CUS.def SPIRE_AOR_OD0117_1_0.aor SPIRE_harness_duration_summary_20090902_18h16m50s.log SPIRE_POS_OD0117_1_0.pos SPIRE_cus_scripts.txt SPIRE_ICP_OD0117_1_0.icp SPIRE_Readme_OD0117_1_0.txt SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv43_FULL_27_0_CUS_CAL.xml SPIRE_SSF_OD0117_1_0.ssf hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> rm *.log rm: remove regular file `SPIRE_harness_duration_summary_20090902_18h16m50s.log'? y [1] + Running nedit MC_H21_P18_S27_PV.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> ls OD0117_SPIRE_FULL_1_20090902.tar SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv43_FULL_27_0_CUS_CAL.xml SPIRE_Readme_OD0117_1_0.txt SPIRE_AOR_OD0117_1_0.aor SPIRE_Duration.txt SPIRE_MC_ASTR_pv43_FULL_27_0_CUS.def SPIRE_SSF_OD0117_1_0.ssf SPIRE_cus_scripts.txt SPIRE_ICP_OD0117_1_0.icp SPIRE_POS_OD0117_1_0.pos 6. Steps to Import the new PACS Instrument model into a new MC Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) Set the Instrument Model & check with CUSGUI Clean the CUS & Cal tables from the instrument model Import the new Instrument Cus & Cal into the DB GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. If Durations are OK then COMMIT the Delivery with CUSGUI Create the new Mission Configuration name in the DB Import the New SPIRE Instrument Model into the Mission Configuration. 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS/PACS_ASTR_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS/PACS_ASTR_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/OD0120/PACS/PACS_ASTR_FULL_1> cvs co develop/data/observingmodes/hscpv/od120/OD0120_PACS_ASTR_FULL_1_090901.tar U develop/data/observingmodes/hscpv/od120/OD0120_PACS_ASTR_FULL_1_090901.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS/PACS_ASTR_FULL_1> cp develop/data/observingmodes/hscpv/od120/OD0120_PACS_ASTR_FULL_1_090901.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS/PACS_ASTR_FULL_1> ls develop/ OD0120_PACS_ASTR_FULL_1_090901.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS/PACS_ASTR_FULL_1> tar -xvf OD0120_PACS_ASTR_FULL_1_090901.tar PACS_Readme_ASTR_PRE_18_0.txt PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CUS.def PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CAL.xml -delivery directory TAKE NOTE : The above steps are to be copied into the PACS BASIC TEMPLATE LOG FILE for OD120 - OK! - mission_config directory hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/PACS> ls OD0120_PACS_ASTR_FULL_1_090901.tar PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CUS.def PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CAL.xml PACS_Readme_ASTR_PRE_18_0.txt 6(b) Set the Instrument Model & check with CUSGUI Update the instrument properties in the .hcss directory hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props Select PACS as the instrument #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 hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS/PACS_ASTR_FULL_1> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/delivery/OD0120/PACS/PACS_ASTR_FULL_1> Sep 2, 2009 7:53:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 7:53:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 7:53:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:53:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:53:02 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 2, 2009 7:53:17 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT PACS IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 6(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Sep 2, 2009 7:55:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 7:55:24 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 7:55:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:55:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:55:33 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Sep 2, 2009 7:55:38 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 7:55:38 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 7:55:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:55:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:55:45 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_FM1_M_903062241 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (Version 18.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/PACS> cus -m "upload PACS_MC_18 mission config" -import PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CUS.def -importcaltables PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CAL.xml Sep 2, 2009 7:57:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 7:57:41 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 7:57: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 2, 2009 7:57:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:58:03 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 2, 2009 7:58:03 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 2, 2009 7:58: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 2, 2009 7:58:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 7:58:05 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by PACS : PACS_MC_ASTR_CoP_PV_2009-08-28A_FULL_18_0_CAL.xml CONFIRMED!! 6(e) GO TO THE BASIC TEMPLATE FILE FOR THIS INSTRUMENT. Check Durations & then RETURN TO THIS TEMPLATE. At this point, you should have open a log file for the OD120 Import for PACS i.e. OD120_PACS_ASTR_FULL_1.log which is located in /icchsc/delivery/OD0120/logs directory. Go to that Log file, update it with some of the information now contained in this LOG file. Run the duration scripts in that LOG file i.e. running them against the files located in the Delivery directory. When this is successful, then you MUST come back to this step of the Procedure. Note that the Templates send you back to here also!!! If No Differences found then proceed to the Next Step. DONE. No differences found. 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS_ASTR_MC_18 TAKE NOTE : It is very important that you commit the delivery as defined above. 6(g) Create the new Mission Configuration name in the DB The command to be run is : missetup -addconfig MC_H21_P18_S27_PV hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/PACS> missetup -addconfig MC_H21_P18_S27_PV Sep 2, 2009 8:04:25 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 8:04:26 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 8:04:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:04:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:04:27 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Sep 2, 2009 8:04:27 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H21_P18_S27_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 : CONFIRMED. 6(h) Import the New PACS Instrument Model into the Mission Configuration. ADDED PACS MODEL TO THE NEW MISSION CONFIGURATION MC_H21_P18_S27_PV Run CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/PACS> Sep 2, 2009 8:04:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 8:04:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 8:04:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:04:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:04:59 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 2, 2009 8:05:14 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P18_S27_PV" Sep 2, 2009 8:05:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:05:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:05:42 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. #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 THIS ENDS THE IMPORT OF THE NEW PACS INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. Steps to Import the OLD HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(a) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> 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/MC_H21_P18_S27_PV/HIFI> Sep 2, 2009 8:06:56 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 8:06:57 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 8:06: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 2, 2009 8:06:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:06:58 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 2, 2009 8:07:11 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Run the duration script for the HIFI instrument Run the duration script for OD 86 delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> ./duration.sh 86 next OD = 86 -- mode HifiEngSetIntoPrimary -- mode HifiEngSetIntoStandby_II_Dissipate -- mode HifiEng_Spur_Investigation_COP -- mode HifiEngSScanDBS -- mode HifiEngSwitchonLO -- mode HifiMappingModeDBSCross -- mode HifiMappingModeDBSRaster -- mode HifiMappingModeFastDBSCross -- mode HifiMappingModeFastDBSRaster -- mode HifiMappingModeFSwitchOTF -- mode HifiMappingModeFSwitchOTFNoRef -- mode HifiMappingModeLoadChopOTF -- mode HifiMappingModeLoadChopOTFNoRef -- mode HifiMappingModeOTF Duration of HifiEngSetIntoPrimary with default parameters = 6 Duration of HifiEngSetIntoStandby_II_Dissipate with default parameters = 24 Duration of HifiEng_Spur_Investigation_COP with default parameters = 191 Duration of HifiEngSScanDBS with default parameters = 1074 Duration of HifiEngSwitchonLO with default parameters = 384 Duration of HifiMappingModeDBSCross with default parameters = 537 Duration of HifiMappingModeDBSRaster with default parameters = 176 Duration of HifiMappingModeFastDBSCross with default parameters = 465 Duration of HifiMappingModeFastDBSRaster with default parameters = 152 Duration of HifiMappingModeFSwitchOTF with default parameters = 109 Duration of HifiMappingModeFSwitchOTFNoRef with default parameters = 26 Duration of HifiMappingModeLoadChopOTF with default parameters = 109 Duration of HifiMappingModeLoadChopOTFNoRef with default parameters = 26 Duration of HifiMappingModeOTF with default parameters = 75 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> ls -ls total 15148 4 -rwxr-xr-x 1 hscphs2 herschel 2678 Jul 10 10:03 duration.sh* 120 -rw-r--r-- 1 hscphs2 herschel 118292 Aug 2 08:39 HIFI_AOR_OD0086_3_0.aor 120 -rw-r--r-- 1 hscphs2 herschel 118292 Aug 2 08:39 HIFI_AOR_OD86.aor 4 -rw-r--r-- 1 hscphs2 herschel 960 Aug 2 08:39 HIFI_DUR_OD0086_3_0.txt 2904 -rw-r--r-- 1 hscphs2 herschel 2961784 Aug 2 08:39 HIFI_ICP_OD0086_3_0.icp 1820 -rw-r--r-- 1 hscphs2 herschel 1857478 Aug 2 08:39 HIFI_POS_OD0086_3_0.pos 4 -rw-r--r-- 1 hscphs2 herschel 2552 Aug 2 08:39 HIFI_Readme_OD0086_3_0.txt 16 -rw-r--r-- 1 hscphs2 herschel 12850 Aug 2 08:39 HIFI_SSF_OD0086_3_0.ssf 10152 -rw-r--r-- 1 hscphs2 herschel 10373120 Aug 2 11:05 OD0086_HIFI_FULL_3_20090802.tar 4 -rw-r--r-- 1 hscphs2 herschel 961 Sep 2 20:08 summary_OD86.log DIFF hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> diff HIFI_DUR_OD0086_3_0.txt summary_OD86.log 0a1 >> No differences. This confirms the Instrument model contents is consistent with the HIFI last Mission Configuration. 7(d) Import HIFI into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/HIFI> Sep 2, 2009 8:10:03 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 8:10:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 8:10:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:10:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:10:04 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 2, 2009 8:10:23 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P18_S27_PV" Sep 2, 2009 8:10:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:10:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:11:13 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P18_S27_PV" Sep 2, 2009 8:11:17 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the OLD SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the SPIRE instrument Import into the new Mission Configuration 8(a) Set Instrument Model = SPIRE #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_P18_S27_PV/SPIRE> Sep 2, 2009 8:12:17 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 8:12:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 8:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:12:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:12:19 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 2, 2009 8:12:31 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. - CONFIRMED!! hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> ls OD0117_SPIRE_FULL_1_20090902.tar SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv43_FULL_27_0_CUS_CAL.xml SPIRE_Readme_OD0117_1_0.txt SPIRE_AOR_OD0117_1_0.aor SPIRE_Duration.txt SPIRE_MC_ASTR_pv43_FULL_27_0_CUS.def SPIRE_SSF_OD0117_1_0.ssf SPIRE_cus_scripts.txt SPIRE_ICP_OD0117_1_0.icp SPIRE_POS_OD0117_1_0.pos 8(c) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE>python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> ls -ls total 17244 8612 -rw-r--r-- 1 hscphs2 herschel 8796160 Sep 2 17:50 OD0117_SPIRE_FULL_1_20090902.tar 320 -rw-r--r-- 1 hscphs2 herschel 321042 Sep 2 17:35 SPIRE_AOR_OD0117_1_0.aor 4 -rw-r--r-- 1 hscphs2 herschel 1606 Sep 2 20:13 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Sep 2 15:48 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 4255 Sep 2 15:48 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 4255 Sep 2 20:16 SPIRE_harness_duration_summary_20090902_20h16m37s.log 3304 -rw-r--r-- 1 hscphs2 herschel 3372389 Sep 2 17:33 SPIRE_ICP_OD0117_1_0.icp 224 -rw-r--r-- 1 hscphs2 herschel 224650 Sep 2 15:48 SPIRE_MC_ASTR_pv43_FULL_27_0_CUS_CAL.xml 1652 -rw-r--r-- 1 hscphs2 herschel 1686613 Sep 2 15:48 SPIRE_MC_ASTR_pv43_FULL_27_0_CUS.def 3072 -rw-r--r-- 1 hscphs2 herschel 3136947 Sep 2 17:33 SPIRE_POS_OD0117_1_0.pos 4 -rw-r--r-- 1 hscphs2 herschel 3818 Sep 2 17:41 SPIRE_Readme_OD0117_1_0.txt 32 -rw-r--r-- 1 hscphs2 herschel 28960 Sep 2 17:33 SPIRE_SSF_OD0117_1_0.ssf hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20090902_20h16m37s.log No differences! 8(d) Import SPIRE model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> cusgui & hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> Sep 2, 2009 8:17:36 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 8:17:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 8:17:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:17:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:17:38 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 2, 2009 8:17:52 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P18_S27_PV" Sep 2, 2009 8:18: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 2, 2009 8:18:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:18:23 PM herschel.cus.gui.CusEditor exit INFO: Quitting. 9.Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophandler to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H21_P18_S27_PV Source the PHS Environment for 1.1.0 hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v1.1.0_phs setHcssExtLibs_csh:INFO:Variable HCSS_DIR set to [/herschel/software/hcss/hcss_1.1.0_phs/dp-core] setHcssExtLibs_csh:INFO:Start setting up variables for HCSS #1 reference platform v8.6 setHcssExtLibs_csh:INFO: Initializing HCSS_CLASSPATH for a new style build setHcssExtLibs_csh:INFO:Updating existing CLASSPATH setHcssExtLibs_csh:INFO:Loading the OS specific enhancements setHcssExtLibs_csh:INFO:- found OS type linux setHcssExtLibs_csh:INFO:- found 32 bit platform. setHcssExtLibs_csh:INFO:Finished setting up variables for HCSS #1 reference platform v8.6 hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> propHandler & hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> Sep 2, 2009 8:19:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 2, 2009 8:19:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 2, 2009 8:19:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 2, 2009 8:19:19 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 2, 2009 8:19:19 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Sep 2, 2009 8:19:19 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 29 Sep 2, 2009 8:19:19 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Sep 2, 2009 8:19:19 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H21_P18_S27_PV" Sep 2, 2009 8:19:26 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 6998 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration : CONFIRMED!! 10. Export the Hspot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. CONFIRMED!! Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same as the Mission Confifguration: MC_H21_P18_S27_PV Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P18_S27_PV/ Example of the last entry in the log: Sep 2, 2009 8:21:12 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P18_S27_PV/HifiSScanModeFastDBSGen.prop Sep 2, 2009 8:21:12 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H21_P18_S27_PV/HifiManCmd_HIFI_Rescue_to_switched_offGen.prop 11. Do the check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P17_S25_PV> ls *.prop > & MC_H21_P18_S27_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> diff MC_H21_P17_S27_PV.txt MC_H21_P18_S27_PV.txt If there is a difference inform Eva & Larry of the result. If there is NO difference then no need to inform Eva or Larry. No differences 12. Final Jboss Activities Log into Jboss #2 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H21_P18_S27_PV/SPIRE> ssh -X hsc_phs@herjbo02 hsc_phs@herjbo02's password: Last login: Wed Sep 2 18:38:41 2009 from herl38.net4.lan 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_P17_S25_PV copy HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H21_P18_S27_PV> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H21_P18_S27_PV/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> emacs HCSS_PHS_TEST_herjbo02_0_6_6.props Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #MARK & CHARO TIME ESTIMATOR hcss.phs.timeEstimatorVersion=MARK-CHARO-USE-ONLY-MC_H21_P18_S27_PV_090902 #MARK & CHARO MISSION CONFIG hcss.ccm.mission.config = MC_H21_P18_S27_PV #MARK & CHARO DIRECTORIES hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H21_P18_S27_PV Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.