HIFI calibration delivery for OD407 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just uploaded the tar file containing the delivery of HIFI CAL observations for OD407 (part of cycle 16) onto the CVS server. 1. Delivery file, directory: a) OD tar file names: - CYCLE016_HIFI_FULL_2_20100614.tar b) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle016 2. Mission Configurations: a) Does this delivery include a new Calibration Mission configuration? Yes b) Does this delivery include a new Astro Mission configuration? No 3. Operations Issues a) Will any of these delivered observations generate a significant amount of Telecommands? No b) Do you wish to have these calibrations observations scheduled in the Real Time Science period of the DTCP? No c) ICC to add anything specific to this OD which HSC & MOC should be aware of: Instructions are in the Readme file. These CAL AORs should be only scheduled during OD-407. Part of the CAL observations should be done in the DTCP. Please acknowledge receipt of the e-mail and the delivery. Kind regards, David Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE015_HIFI_FULL_2_20100520.tar New MC - MC H44CAL 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 2.0.1 (Always use the most recent HCSS Software version) PHS SOFTWARE = 2.3.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_v2.0.1 TAKE NOTE : If there is a newer HCSS software version in the otherSetups directory then source that new version. 3. What is the Mission Configuration Name going to be?? MC_H44_P53_S56_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle15> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI> mkdir HIFI_FULL_2 This LOG file has been placed in the /logs directory and given the name Cycle015_HIFI_FULL_2.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the PACS directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H44_P53_S56_CAL folder. Next remove in the subfolders all files which were created when you ran the HIFI, SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H42ASTR_P53ASTR_S55ASTR_AO/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> ls CYCLE017_PACS_FULL_2_20100609.tar PACS_MC_ASTR_OT1_2010-06-09A_C017_53_CUS.def PACS_MC_ASTR_OT1_2010-06-09A_C017_53_CUS_CAL.xml PACS_Readme_C017_53.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> rm tmp* msg* PACS_Duration_PACS.txt rm: No match. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> ls CYCLE017_PACS_FULL_2_20100609.tar PACS_MC_ASTR_OT1_2010-06-09A_C017_53_CUS.def PACS_MC_ASTR_OT1_2010-06-09A_C017_53_CUS_CAL.xml PACS_Readme_C017_53.txt SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H43_P50_S56_CAL/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> ls CYCLE015_SPIRE_UPDATE_1_1_20100520.tar SPIRE_harness_duration_summary_20100521_12h06m32s.log SPIRE_AOR_C015_56_ENG.aor SPIRE_MC_pv82_C015_56_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_pv82_C015_56_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C015_56.txt SPIRE_Duration.txt 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI/HIFI_FULL_2> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI/HIFI_FULL_2> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI/HIFI_FULL_2> cvs co develop/data/observingmodes/rp_cycles/cycle016/CYCLE016_HIFI_FULL_2_20100614.tar U develop/data/observingmodes/rp_cycles/cycle016/CYCLE016_HIFI_FULL_2_20100614.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI/HIFI_FULL_2> cp develop/data/observingmodes/rp_cycles/cycle016/CYCLE016_HIFI_FULL_2_20100614.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI/HIFI_FULL_2> ls CYCLE016_HIFI_FULL_2_20100614.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI/HIFI_FULL_2> tar -xvf CYCLE016_HIFI_FULL_2_20100614.tar duration_cal.sh HIFI_AOR_C016_44.aor HIFI_DUR_C016_44.txt HIFI_MC_R060_FULL_44_0_CUS_CAL.xml HIFI_MC_R060_FULL_44_0_CUS.def HIFI_Readme_C016_44.txt toto.aor hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI/HIFI_FULL_2> ls CYCLE016_HIFI_FULL_2_20100614.tar HIFI_AOR_C016_44.aor HIFI_MC_R060_FULL_44_0_CUS.def develop/ HIFI_DUR_C016_44.txt HIFI_Readme_C016_44.txt duration_cal.sh* HIFI_MC_R060_FULL_44_0_CUS_CAL.xml toto.aor hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI> cp * /home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> ls CYCLE016_HIFI_FULL_2_20100614.tar HIFI_AOR_C016_44.aor HIFI_MC_R060_FULL_44_0_CUS_CAL.xml HIFI_Readme_C016_44.txt duration_cal.sh* HIFI_DUR_C016_44.txt HIFI_MC_R060_FULL_44_0_CUS.def toto.aor 6(b) To import the old PACS delivery: #CUS #var.hcss.instrument = SPIRE var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> Jun 14, 2010 4:27:54 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 4:27:55 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 4:27:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:27:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:27:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:27:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:27:55 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jun 14, 2010 4:28:41 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_H44_P53_S56_CAL/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Jun 14, 2010 4:30:01 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 4:30:02 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 4:30:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:30:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:30:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:30:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:30:10 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Jun 14, 2010 4:30:17 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 4:30:18 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 4:30:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:30:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:30:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:30:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:30:24 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_MOC9_201003161700 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (Version 53.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> cus -m "upload PACS_MC_53ASTR mission config as Cal" -import PACS_MC_ASTR_OT1_2010-06-09A_C017_53_CUS.def -importcaltables PACS_MC_ASTR_OT1_2010-06-09A_C017_53_CUS_CAL.xml Jun 14, 2010 4:32:41 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 4:32:41 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 4:32:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:32:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:32:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:32:42 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:33:05 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jun 14, 2010 4:33:05 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jun 14, 2010 4:33:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:33:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:33:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:33:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:33:09 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT1_2010-06-09A_C017_53_CUS_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_OT1_2010-06-09A_C017_53_CUS_CAL.xml CONFIRMED!! PACS did not deliver AORs, so skip this next bit... 6(e) Run the duration script for the PACS instrument model: Open duration script (2createOBSMODtable4RP.sh) and point it to HCSS 2.0.1 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C013_48.aor /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/delivery/Calibration_Cycle15/PACS/PACS_FULL_1 hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle15/PACS/PACS_FULL_1> ls -ls total 10680 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Apr 22 15:30 2createOBSMODtable4RP.sh* 5332 -rw-r--r-- 1 hscphs2 herschel 5447680 Apr 22 16:01 Cycle015_PACS_FULL_1_20100422.tar 4 drwxr-xr-x 4 hscphs2 herschel 4096 Apr 22 17:20 develop/ 0 -rw-r--r-- 1 hscphs2 herschel 59 Apr 22 17:44 msgPacsPhoto.txt 40 -rw-r--r-- 1 hscphs2 herschel 35390 Apr 22 15:21 PACS_AOR_C013_48.aor 4 -rw-r--r-- 1 hscphs2 herschel 826 Apr 22 15:36 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 826 Apr 22 17:44 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 401435 Apr 22 15:59 PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS_CAL.xml 4884 -rw-r--r-- 1 hscphs2 herschel 4988214 Apr 22 15:59 PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 4513 Apr 22 15:41 PACS_Readme_C013_48.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle15/PACS/PACS_FULL_1> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! Re-join here. 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS MC P50ASTR as Cal TAKE NOTE : It is very important that you commit the delivery as defined above. Now create the MC in the database hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> missetup -addconfig MC_H44_P53_S56_CAL Jun 14, 2010 4:52:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 4:52:41 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 4:52:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:52:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:52:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:52:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:52:41 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Jun 14, 2010 4:52:41 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H44_P53_S56_CAL" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Add the commited CUS to the new MC hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/PACS> Jun 14, 2010 4:53:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 4:53:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 4:53:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:53:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:53:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:53:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:53:30 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jun 14, 2010 4:56:44 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H44_P53_S56_CAL" Jun 14, 2010 4:56:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:56:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:56:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:56:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:57:42 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the new 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> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> Jun 14, 2010 7:17:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 7:17:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 7:17:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:17:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:17:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:17:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:17:10 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jun 14, 2010 7:17:18 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) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Jun 14, 2010 7:18:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 7:18:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 7:18:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:18:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:18:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:18:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:18:12 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Jun 14, 2010 7:18:28 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 7:18:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 7:18:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:18:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:18:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:18:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:18:35 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_MOC9_201003161700 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (H44Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> cus -m "upload HIFI MC44Cal mission config" -import HIFI_MC_R060_FULL_44_0_CUS.def -importcaltables HIFI_MC_R060_FULL_44_0_CUS_CAL.xml Jun 14, 2010 7:20:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 7:20:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 7:20:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:20:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:20:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:20:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:20:42 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jun 14, 2010 7:20:42 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jun 14, 2010 7:20:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:20:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:20:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:20:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:20:50 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R060_FULL_44_0_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by HIFI: HIFI_MC_R060_FULL_44_0_CUS_CAL.xml CONFIRMED!! 7(e) Run the duration script for the HIFI instrument Run the duration script delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C016_44 next AOR file = HIFI_AOR_C016_44 -- mode HifiEngSetIntoPrimary -- mode HifiEngSwitchonLO -- mode HifiEng_Tsys_COP -- mode HifiMappingProcFastDBSRaster -- mode HifiMappingModeDBSCross -- mode HifiMappingModeDBSRaster -- mode HifiMappingModeFastDBSCross -- mode HifiMappingModeFastDBSRaster -- mode HifiMappingModeFSwitchOTF -- mode HifiMappingModeFSwitchOTFNoRef -- mode HifiMappingModeLoadChopOTF -- mode HifiMappingModeLoadChopOTFNoRef -- mode HifiMappingModeOTF Total duration of HifiEngSetIntoPrimary with default parameters = 6 Total duration of HifiEngSwitchonLO with default parameters = 395 Total duration of HifiEng_Tsys_COP with default parameters = 1331 Total duration of HifiMappingProcFastDBSRaster with default parameters = 727 Total duration of HifiMappingModeDBSCross with default parameters = 494 Total duration of HifiMappingModeDBSRaster with default parameters = 230 Total duration of HifiMappingModeFastDBSCross with default parameters = 422 Total duration of HifiMappingModeFastDBSRaster with default parameters = 206 Total duration of HifiMappingModeFSwitchOTF with default parameters = 232 Total duration of HifiMappingModeFSwitchOTFNoRef with default parameters = 159 Total duration of HifiMappingModeLoadChopOTF with default parameters = 199 Total duration of HifiMappingModeLoadChopOTFNoRef with default parameters = 126 Total duration of HifiMappingModeOTF with default parameters = 165 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> ls -ls total 11624 5804 -rw-r--r-- 1 hscphs2 herschel 5928960 Jun 14 18:56 CYCLE016_HIFI_FULL_2_20100614.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Jun 14 12:17 duration_cal.sh* 152 -rw-r--r-- 1 hscphs2 herschel 150644 Jun 14 18:52 HIFI_AOR_C016_44.aor 4 -rw-r--r-- 1 hscphs2 herschel 964 Jun 14 18:28 HIFI_DUR_C016_44.txt 2176 -rw-r--r-- 1 hscphs2 herschel 2216243 Jun 14 12:03 HIFI_MC_R060_FULL_44_0_CUS_CAL.xml 3276 -rw-r--r-- 1 hscphs2 herschel 3343968 Jun 14 12:03 HIFI_MC_R060_FULL_44_0_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 4858 Jun 14 18:54 HIFI_Readme_C016_44.txt 4 -rw-r--r-- 1 hscphs2 herschel 964 Jun 14 19:26 summary_HIFI_AOR_C016_44.log 196 -rw-r--r-- 1 hscphs2 herschel 193690 Jun 14 18:23 toto.aor hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> diff HIFI_DUR_C016_44.txt summary_HIFI_AOR_C016_44.log No differences. Perfect 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY In the Comment field, refer to HIFI MC H44_Cal TAKE NOTE : It is very important that you commit the delivery as defined above. 7(g) Import HIFI into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/HIFI> Jun 14, 2010 7:28:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 7:28:41 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 7:28:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:28:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:28:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:28:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:28:41 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jun 14, 2010 7:28:58 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H44_P53_S56_CAL" Jun 14, 2010 7:29:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:29:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:29:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:29:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:29:45 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 PACS instrument Import into the new Mission Configuration 8(a) Set Instrument Model = SPIRE #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> Jun 14, 2010 4:58:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 4:58:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 4:58:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:58:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 4:58:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:58:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 4:58:51 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jun 14, 2010 4:58:58 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Jun 14, 2010 5:01:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 5:01:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 5:01:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:01:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:01:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:01:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:01:37 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jun 14, 2010 5:02:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 5:02:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 5:02:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:02:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:02:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:02:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:02:41 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 56.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> cus -m "upload SPIRE MC_56 mission config" -import SPIRE_MC_pv82_C015_56_CUS.def -importcaltables SPIRE_MC_pv82_C015_56_CUS_CAL.xml Jun 14, 2010 5:05:03 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 5:05:03 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 5:05:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:05:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:05:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:05:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:05:18 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jun 14, 2010 5:05:18 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jun 14, 2010 5:05:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:05:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:05:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:05:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:05:21 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv82_C015_56_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by SPIRE: SPIRE_MC_pv82_C015_56_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> ls -ls total 4696 2340 -rw-r--r-- 1 hscphs2 herschel 2385920 May 20 19:16 CYCLE015_SPIRE_UPDATE_1_1_20100520.tar 4 -rw-r--r-- 1 hscphs2 herschel 3290 May 20 19:05 SPIRE_AOR_C015_56_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 1931 Jun 14 17:06 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 May 14 17:20 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5147 May 20 19:07 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5147 May 21 12:06 SPIRE_harness_duration_summary_20100521_12h06m32s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5147 Jun 14 17:11 SPIRE_harness_duration_summary_20100614_17h11m05s.log 276 -rw-r--r-- 1 hscphs2 herschel 276611 May 20 19:06 SPIRE_MC_pv82_C015_56_CUS_CAL.xml 2040 -rw-r--r-- 1 hscphs2 herschel 2083806 May 20 19:06 SPIRE_MC_pv82_C015_56_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 3437 May 20 19:10 SPIRE_Readme_C015_56.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20100614_17h11m05s.log Perfect. No differences! 8(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE SPIRE DELIVERY In the Comment field, refer to SPIRE MC S56CAL. TAKE NOTE : It is very important that you commit the delivery as defined above. 8(g) Import SPIRE model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H44_P53_S56_CAL/SPIRE> Jun 14, 2010 5:13:11 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 5:13:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 5:13:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:13:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:13:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:13:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:13:13 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jun 14, 2010 5:13:31 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H44_P53_S56_CAL" Jun 14, 2010 5:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 5:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 5:14:06 PM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. 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_H44_P53_S56_CAL Source the PHS Environment for 2.3.0_phs hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v2.3.0_phs hscphs2@heropl02/home/hscphs2> Jun 14, 2010 7:31:51 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jun 14, 2010 7:31:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jun 14, 2010 7:31:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:31:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jun 14, 2010 7:31:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jun 14, 2010 7:31:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Running CDH.getObsProgrammes() Jun 14, 2010 7:31:52 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Jun 14, 2010 7:31:52 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 34 Jun 14, 2010 7:31:52 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Jun 14, 2010 7:31:52 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H44_P53_S56_CAL" Jun 14, 2010 7:31:57 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 5068 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_H44_P53_S56_CAL Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H44_P53_S56_CAL Example of the last entry in the log: Jun 14, 2010 7:34:17 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H44_P53_S56_CAL/HifiManCmdSetIntoDissipative_IIGen.prop Jun 14, 2010 7:34:17 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H44_P53_S56_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H44_P53_S56_CAL> ls *.prop > & MC_H44_P53_S56_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H44_P53_S56_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 17282 Jun 14 19:34 MC_H44_P53_S56_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H44_P53_S56_CAL> cp MC_H44_P53_S56_CAL.txt /home/hscphs2/icchsc/HSpot_files/ 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_H43_P50_S56_CAL.txt MC_H44_P53_S56_CAL.txt If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. No new HIFI scripts. Do not notify Eva & Jose 12. Final Jboss Activities Log into Jboss #2 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_H44_P53_S56_CAL 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. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H44_P53_S56_CAL> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H44_P53_S56_CAL/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit HCSS_PHS_TEST_herjbo02_0_6_6.props & [1] 3171 Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #MARK TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_H42ASTR_P53ASTR_S55ASTR_AO_100610 hcss.phs.timeEstimatorVersion=MC_H44_P53_S56_CAL_100614 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H42ASTR_P53ASTR_S55ASTR_AO hcss.ccm.mission.config = MC_H44_P53_S56_CAL #MARK DIRECTORIES #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H42ASTR_P53ASTR_S55ASTR_AO hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H44_P53_S56_CAL Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.