PACS & HIFI Cycle 13 delivery 1. Delivery Note PACS Delivery note - 22nd April 2010 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of PACS RP cycle#13 tar file onto the CVS server, including a new ASTR MC. As agreed during yesterday's planning meeting you should expect a cycle#13 update delivery for OD370 (the last OD of cycle#13) by Friday 30 April lunch time to accomodate the PACS-S pointing calibration follow-up to be defined in detail from the results of ODs 345 and 348 which will be available next week. Due to POS generation failure (telecommand too long, 234 bytes, see PACS-2128 update) when scheduling the engineering block foreseen for the DTCP of OD 362, a delivery of this has to be postponed to Monday, 26 April (feasibility of this has been checked with HSC MPS group). This will likely include a new calibration MC to enable the modified engineering mode. It needs to be re-tested on the PACS FS. 1. Delivery file & directory (a) OD tar file name : CYCLE013_PACS_FULL_1_20100422.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle013, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 48.0 2. Mission Configurations (a) Does this delivery include a new Calibration mission configuration? YES (b) Does this delivery include a new ASTR mission configuration? YES high level SCR for cCCB: PHS-1391 (New Astronomer Mission Configuration PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48) SPRs affecting ASTR backend PHS-1377 (PacsLineSpec) PHS-1383 (PacsRangeSpec) PHS-1389 (PacsLineSpec) SPRs affecting CAL backend PHS-1119 (PacsCal_PacsLineSpec_PV) PACS-2128 (new engineering mode PacsEng_PacsDPUOBCP32Updategen) 3. Operations Issues (TC,HPSDB,SIAM,Real Time Science) (a) Will any of these delivered observations generate a significant amount of telecommands? NO (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? NO (c) ICC to add anything specific which HSC & MOC should be aware of The delivery contains the following PACS RP calibration blocks: (for an overview, please see PACS Routine Phase Calibration Plan, PICC-MA-PL-002. Section numbers refer to the currently released issue 0.60 (Note at the time of writing this delivery notification this issue is still under work) . * RPPhotFPG 2.6.1 D & E, PACS RP Cal Plan, section 10.1 on HIP 13502, HIP 21479, HIP 48036, IRAS 22134+5834 to verify pointings and spatial structure of PACS spectrometer pointing sources with the photometer Scheduling instructions per OD (from Readme file) (f) AOR distribution according to ODs and PACS sub-instruments: PACS PHOT observations of PACS SPEC pointing sources (OD 360) ============================================================= RPPhotFPG_261D_cPS_blu_SAA-20+30_HIP13502_0001 RPPhotFPG_261E_sPS_070_blu_HIP13502_0001 RPPhotFPG_261E_sPS_110_blu_HIP13502_0001 RPPhotFPG_261D_cPS_blu_SAA-20+30_HIP21479_0001 RPPhotFPG_261E_sPS_070_blu_HIP21479_0001 RPPhotFPG_261E_sPS_110_blu_HIP21479_0001 RPPhotFPG_261D_cPS_blu_SAA-20+30_HIP48036_0001 RPPhotFPG_261E_sPS_070_blu_HIP48036_0001 RPPhotFPG_261E_sPS_110_blu_HIP48036_0001 RPPhotFPG_261D_cPS_blu_SAA-20+30_IRAS22134_0001 RPPhotFPG_261E_sPS_070_hi_blu_IRAS22134_0001 RPPhotFPG_261E_sPS_110_hi_blu_IRAS22134_0001 RPPhotFPG_261E_sPS_070_lo_blu_IRAS22134_0001 RPPhotFPG_261E_sPS_110_lo_blu_IRAS22134_0001 The AORs should be executed on OD 360, each block shall be scheduled in the indicated sequence. Please acknowledge receipt of the e-mail and the delivery. Kind regards, Ulrich ------------------------------------------------- HIFI Delivery note - 23rd April 2010 Dear HSC Colleagues, This e-mail is to notify you that HIFI ICC has just uploaded the tar file containing the delivery of HIFI observations for cycle 13 onto the CVS server. 1. Delivery file, directory & Mission Configuration issues 1) OD tar file names: - CYCLE013_HIFI_FULL_1_20100424.tar 2) CVS server directory: - develop/data/observingmodes/rp_cycles/cycle013 3) Does this delivery include a new Mission configuration? Yes: (using HIFI CUS 16.168) HIFI_MC_R056_FULL_37_0_CUS_CAL.xml and HIFI_MC_R056_FULL_37_0_CUS.def 2. Operations Issues (described in more detail in the Readme file) The calibration observations in this cycle will be separated in three blocks: 1. A dedicated program for the second half of OD355 2. A series of test schedulable with flexibility during the DTCPs of OD362-367 3. A series of pointed observations (FPG3) during the second half of OD370 The current delivery only contains points 1 and 2, the last set of AORs for OD370 will be delivered on the 26th of April. Please acknowledge receipt of the e-mail and the delivery. Kind regards, Christophe Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE013_HIFI_FULL_1_20100424.tar New MCs - MC P48_ASTR (to be processed as PV until it receives cCCB approval). - MC H37_PV 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_H37_P48_S52_PV 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI> mkdir PACS_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle013_PACS_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle013_HIFI_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the SPIRE directory from a previous mission_config subdirectory intothe equivalent subdirectories of the MC_H37_P48_S52_PV folder. Next remove in the SPIRE subfolders all files which were created when you ran the SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/SPIRE> ls CYCLE012_SPIRE_FULL_1_0_20100409.tar SPIRE_Duration.txt SPIRE_AOR_C012_52_CAL.aor SPIRE_harness_duration_summary_20100409_18h35m27s.log SPIRE_AOR_C012_52_ENG.aor SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv77_C012_52_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C012_52.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_Cycle13/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/HIFI/HIFI_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/Calibration_Cycle13/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle013/CYCLE013_PACS_FULL_1_20100422.tar U develop/data/observingmodes/rp_cycles/cycle013/CYCLE013_PACS_FULL_1_20100422.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle013/CYCLE013_PACS_FULL_1_20100422.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/PACS/PACS_FULL_1> ls CYCLE013_PACS_FULL_1_20100422.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/PACS/PACS_FULL_1> tar -xvf CYCLE013_PACS_FULL_1_20100422.tar PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS.def PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS_CAL.xml PACS_AOR_C013_48.aor PACS_Duration_PACS_compare.txt PACS_Readme_C013_48.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/PACS/PACS_FULL_1> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt CYCLE013_PACS_FULL_1_20100422.tar PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS_CAL.xml develop/ PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS.def PACS_AOR_C013_48.aor PACS_Readme_C013_48.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C013_48.txt CYCLE013_PACS_FULL_1_20100422.tar PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS_CAL.xml PACS_AOR_C013_48.aor PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS.def 6(b) To import the new 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/delivery/Calibration_Cycle13/PACS/PACS_FULL_1> Apr 22, 2010 5:27:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 5:27:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 5:27:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:27:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:27:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:27:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:27:08 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 22, 2010 5:27:43 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_H37_P48_S52_PV/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Apr 22, 2010 5:28:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 5:28:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 5:28:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:28:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:28:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:28:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:28:25 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Apr 22, 2010 5:28:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 5:28:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 5:28:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:28:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:28:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:28:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:28:40 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_MOC7_201002011600 - CONFIRMED!! 6(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (Version 48.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/PACS> cus -m "upload PACS_MC_48ASTR mission config" -import PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS.def -importcaltables PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_CUS_CAL.xml Apr 22, 2010 5:37:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 5:37:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 5:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:37:46 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 22, 2010 5:37:46 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 22, 2010 5:37:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:37:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 5:37:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:37:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 5:37:52 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_CalPhase_2010-04-19A_C013_48_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_CalPhase_2010-04-19A_C013_48_CUS_CAL.xml CONFIRMED!! 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_H37_P48_S52_PV/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C013_48.aor /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/delivery/Calibration_Cycle13/PACS/PACS_FULL_1 hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/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 CYCLE013_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_Cycle13/PACS/PACS_FULL_1> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! 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 P48ASTR 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_H37_P48_S52_PV/PACS> missetup -addconfig MC_H37_P48_S52_PV Apr 22, 2010 6:05:20 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:05:21 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:05:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:05:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:05:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:05:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:05:22 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Apr 22, 2010 6:05:22 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H37_P48_S52_PV" 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_H37_P48_S52_PV/PACS> Apr 22, 2010 6:06:58 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:06:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:06:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:06:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:06:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:06:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:06:59 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 22, 2010 6:07:27 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H37_P48_S52_PV" Apr 22, 2010 6:07:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:07:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:07:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:07:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:08:04 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) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI/HIFI_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI/HIFI_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/Calibration_Cycle13/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle013/CYCLE013_HIFI_FULL_1_20100424.tar U develop/data/observingmodes/rp_cycles/cycle013/CYCLE013_HIFI_FULL_1_20100424.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI/HIFI_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle013/CYCLE013_HIFI_FULL_1_20100424.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI/HIFI_FULL_1> ls CYCLE013_HIFI_FULL_1_20100424.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI/HIFI_FULL_1> tar -xvf CYCLE013_HIFI_FULL_1_20100424.tar HIFI_AOR_C013_37.aor HIFI_DUR_C013_37.txt HIFI_MC_R056_FULL_37_0_CUS_CAL.xml HIFI_MC_R056_FULL_37_0_CUS.def HIFI_Readme_C013_37.txt duration_cal.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI/HIFI_FULL_1> ls CYCLE013_HIFI_FULL_1_20100424.tar HIFI_AOR_C013_37.aor HIFI_MC_R056_FULL_37_0_CUS.def develop/ HIFI_DUR_C013_37.txt HIFI_Readme_C013_37.txt duration_cal.sh* HIFI_MC_R056_FULL_37_0_CUS_CAL.xml ls hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle13/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/HIFI/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/HIFI> ls CYCLE013_HIFI_FULL_1_20100424.tar HIFI_AOR_C013_37.aor HIFI_MC_R056_FULL_37_0_CUS_CAL.xml HIFI_Readme_C013_37.txt duration_cal.sh* HIFI_DUR_C013_37.txt HIFI_MC_R056_FULL_37_0_CUS.def ls 7(b) 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_H37_P48_S52_PV/HIFI> Apr 22, 2010 6:29:45 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:29:46 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:29:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:29:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:29:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:29:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:29:47 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 22, 2010 6:30:03 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_H37_P48_S52_PV/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Apr 22, 2010 6:30:24 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:30:25 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:30:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:30:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:30:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:30:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:30:29 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Apr 22, 2010 6:30:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:30:42 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:30:47 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 (H37). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/HIFI> cus -m "upload HIFI MC37_PV mission config" -import HIFI_MC_R056_FULL_37_0_CUS.def -importcaltables HIFI_MC_R056_FULL_37_0_CUS_CAL.xml Apr 23, 2010 2:36:53 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 23, 2010 2:36:54 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 23, 2010 2:36:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:36:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:36:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:36:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:37:15 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 23, 2010 2:37:15 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 23, 2010 2:37:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:37:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:37:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:37:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:37:23 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R056_FULL_37_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_R056_FULL_37_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_H37_P48_S52_PV/HIFI> ./duration_cal.sh HIFI_AOR_C013_37 next AOR file = HIFI_AOR_C013_37 -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_Diplexer_calibration_vs_D2_COP -- mode HifiEng_Diplexer_Response_time_COP -- mode HifiEng_FPU_FT_IVC_COP -- mode HifiEng_HRS_FT_COP -- mode HifiEng_LO_FT_IVC_COP -- mode HifiEngSwitchonLO -- mode HifiEng_Tsys_Vecscan_COP -- mode HifiEng_Tsys_Vecscan_M1_COP -- mode HifiEng_WBS_FT_COP -- mode HifiSScanModeDBS -- mode HifiSScanModeFastDBS -- mode HifiSScanModeFSwitch -- mode HifiSScanModeFSwitchNoRef -- mode HifiSScanModeLoadChop -- mode HifiSScanModeLoadChopNoRef Total duration of HifiEng_Chopper_Response_time_COP with default parameters = 44 Total duration of HifiEng_Diplexer_calibration_vs_D2_COP with default parameters = 5081 Total duration of HifiEng_Diplexer_Response_time_COP with default parameters = 85 Total duration of HifiEng_FPU_FT_IVC_COP with default parameters = 38 Total duration of HifiEng_HRS_FT_COP with default parameters = 1101 Total duration of HifiEng_LO_FT_IVC_COP with default parameters = 198 Total duration of HifiEngSwitchonLO with default parameters = 395 Total duration of HifiEng_Tsys_Vecscan_COP with default parameters = 1811 Total duration of HifiEng_Tsys_Vecscan_M1_COP with default parameters = 3848 Total duration of HifiEng_WBS_FT_COP with default parameters = 1387 Total duration of HifiSScanModeDBS with default parameters = 383 Total duration of HifiSScanModeFastDBS with default parameters = 335 Total duration of HifiSScanModeFSwitch with default parameters = 497 Total duration of HifiSScanModeFSwitchNoRef with default parameters = 414 Total duration of HifiSScanModeLoadChop with default parameters = 347 Total duration of HifiSScanModeLoadChopNoRef with default parameters = 282 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/HIFI> ls -ls total 11060 5524 -rw-r--r-- 1 hscphs2 herschel 5642240 Apr 23 12:49 CYCLE013_HIFI_FULL_1_20100424.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Apr 23 11:38 duration_cal.sh* 96 -rw-r--r-- 1 hscphs2 herschel 90339 Apr 23 12:24 HIFI_AOR_C013_37.aor 4 -rw-r--r-- 1 hscphs2 herschel 1183 Apr 23 12:22 HIFI_DUR_C013_37.txt 2164 -rw-r--r-- 1 hscphs2 herschel 2205819 Apr 23 12:17 HIFI_MC_R056_FULL_37_0_CUS_CAL.xml 3256 -rw-r--r-- 1 hscphs2 herschel 3322747 Apr 23 12:17 HIFI_MC_R056_FULL_37_0_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 8176 Apr 23 12:24 HIFI_Readme_C013_37.txt 4 -rw-r--r-- 1 hscphs2 herschel 1183 Apr 23 14:40 summary_HIFI_AOR_C013_37.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/HIFI> diff HIFI_DUR_C013_37.txt summary_HIFI_AOR_C013_37.log 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 H37_PV 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_H37_P48_S52_PV/HIFI> Apr 23, 2010 2:53:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 23, 2010 2:53:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 23, 2010 2:53:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:53:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:53:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:53:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:53:17 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 23, 2010 2:53:45 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H37_P48_S52_PV" Apr 23, 2010 2:54:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:54:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 2:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:54:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 2:54:44 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 Reset the OBDB/STPF properties 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_H37_P48_S52_PV/SPIRE> Apr 22, 2010 6:12:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:12:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:12:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:12:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:12:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:12:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:12:06 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 22, 2010 6:12:25 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_H37_P48_S52_PV/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Apr 22, 2010 6:13:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:13:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:13:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:13:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:13:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:13:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:13:50 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Apr 22, 2010 6:14:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:14:07 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:14:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:14:12 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 52.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/SPIRE> cus -m "upload SPIRE MC_52ASTR mission config" -import SPIRE_MC_ASTR_pv77_C012_52_CUS.def -importcaltables SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml Apr 22, 2010 6:16:59 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:16:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:17:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:17:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:17:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:17:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:17:14 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 22, 2010 6:17:14 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 22, 2010 6:17:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:17:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:17:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:17:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:17:17 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv77_C012_52_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_CalPhase_2010-03-04A_C010_44_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/SPIRE> ls -ls total 5492 2728 -rw-r--r-- 1 hscphs2 herschel 2785280 Apr 9 18:19 CYCLE012_SPIRE_FULL_1_0_20100409.tar 136 -rw-r--r-- 1 hscphs2 herschel 131289 Apr 9 18:07 SPIRE_AOR_C012_52_CAL.aor 280 -rw-r--r-- 1 hscphs2 herschel 280090 Apr 9 18:07 SPIRE_AOR_C012_52_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 1881 Apr 22 18:18 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Apr 9 18:17 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 4970 Apr 9 18:17 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 4970 Apr 9 18:35 SPIRE_harness_duration_summary_20100409_18h35m27s.log 8 -rw-rw-rw- 1 hscphs2 herschel 4970 Apr 22 18:22 SPIRE_harness_duration_summary_20100422_18h22m21s.log 268 -rw-r--r-- 1 hscphs2 herschel 269717 Apr 9 18:17 SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml 2032 -rw-r--r-- 1 hscphs2 herschel 2072931 Apr 9 18:17 SPIRE_MC_ASTR_pv77_C012_52_CUS.def 16 -rw-r--r-- 1 hscphs2 herschel 13193 Apr 9 18:17 SPIRE_Readme_C012_52.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H37_P48_S52_PV/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20100422_18h22m21s.log Perfect. No differences! 8(f) If Durations are OK then COMMIT the Delivery with CUSGUI No new CUS. Don't commit. OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE SPIRE DELIVERY In the Comment field, refer to SPIRE MC S52 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_H37_P48_S52_PV/SPIRE> Apr 22, 2010 6:25:12 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 22, 2010 6:25:13 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 22, 2010 6:25:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:25:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:25:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:25:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:25:13 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 22, 2010 6:25:56 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H37_P48_S52_PV" Apr 22, 2010 6:26:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:26:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 22, 2010 6:26:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:26:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 22, 2010 6:26:31 PM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE PACS 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_H37_P48_S52_PV Source the PHS Environment for 2.3.0_phs hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v2.3.0_phs hscphs2@heropl02/home/hscphs2/otherSetups> Apr 23, 2010 3:02:11 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 23, 2010 3:02:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 23, 2010 3:02:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 3:02:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 23, 2010 3:02:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 23, 2010 3:02:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Running CDH.getObsProgrammes() Apr 23, 2010 3:02:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Apr 23, 2010 3:02:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 32 Apr 23, 2010 3:02:13 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Apr 23, 2010 3:02:13 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H37_P48_S52_PV" Apr 23, 2010 3:02:19 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 5470 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_H37_P48_S52_PV Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H37_P48_S52_PV Example of the last entry in the log: Apr 23, 2010 3:04:55 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H37_P48_S52_PV/HifiManCmdSetIntoDissipative_IIGen.prop Apr 23, 2010 3:04:55 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H37_P48_S52_PV/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H37_P48_S52_PV> ls *.prop > & MC_H37_P48_S52_PV.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H37_P48_S52_PV> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 17165 Apr 23 15:06 MC_H37_P48_S52_PV.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H37_P48_S52_PV> cp MC_H37_P48_S52_PV.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_H35_P47_S51_PV.txt MC_H37_P48_S52_PV.txt 261a262 > PacsEng_PacsDPUOBCP32UpdateGen.prop 413a415 If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. One new HIFI script. 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_H37_P48_S52_PV copied HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H37_P48_S52_PV> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H37_P48_S52_PV/ 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 & CHIQUI TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_MAN_S7_100329 #hcss.phs.timeEstimatorVersion=MC_H36ASTR_P47ASTR_S52ASTR_RP_100409 hcss.phs.timeEstimatorVersion=MC_H37_P48_S52_PV_100423_Saint_George #MARK & CHIQUI MISSION CONFIG #hcss.ccm.mission.config = MC_MAN_S7 #hcss.ccm.mission.config = MC_H36ASTR_P47ASTR_S52ASTR_RP hcss.ccm.mission.config = MC_H37_P48_S52_PV #MARK & CHIQUI DIRECTORIES #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_MAN_S7 #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H36ASTR_P47ASTR_S52ASTR_RP hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H37_P48_S52_PV Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.