PACS Cycle 24 special MC delivery for Gyro Pointing validation PACS Delivery note - 20th September 2010 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of the PACS gyro nodding test (part 1 and 2 with PACS photometer) tar file onto the CVS server. 1. Delivery file & directory (a) OD tar file name : GYRONOD_PHOT_PACS_FULL_1_20100920.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle024, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 57.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? NO 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? YES, see minutes of CP Raster Telecon #2 - 17th September 2010 DRAFT Minutes http://www.herschel.be/twiki/bin/view/HSC/GyropointingModeTelecon#2 (c) ICC to add anything specific which HSC & MOC should be aware of This delivery contains the special gyro nodding test AORs and the corresponding calibration MC with the gyro nodding AOTs for the first two test steps planned for ODs 516 and 526 with the PACS photometer. Note, that at least HSpot 5.1.2 (HCSS: 5.0 #1229 with PHS 5.1.2 (#632) at PACS-ICC) is needed to process the AORs and HCSS 5.0 #1387 is needed for the SMPS to produce a valid POS file. 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.95.) * RPPhotFPG 2.6.2A, PACS RP Cal Plan, section 10.1 on HIP 45058 - gyro nodding test PACS chop/nod point source photometry with gyro nodding pointing: test case 1: tmax = 634s, koff = 4, nnod = 16 foreseen for OD 516. test case 2: tmax = 954s, koff = 6, nnod = 18 foreseen for OD 526. Both test cases shall be scheduled into the Real Time Science Window of the respective DTCP. They need to be proceeded by a PACS-PhotSetup_na_nStd_orbitproWait_na AOR. On OD 516, the reference AOR RPPhotFPG_262A_cPS_blu_ref_HIP45058_0001, provided with calibration cycle#24 delivery shall be scheduled independently, i.e. not directly after the gyro nodding AOR, in order to have an independent absolute re-pointing of the telescope. Scheduling instructions per OD (from Readme file) (f) AOR distribution according to ODs and PACS sub-instruments: PACS PHOT (to be scheduled in real time science window of OD 516) ================================================================= RPPhotFPG_262B_gyronodcPS_blu_tmax634_HIP45058_0001 PACS PHOT (to be scheduled in real time science window of OD 526) ================================================================= RPPhotFPG_262B_gyronodcPS_blu_tmax954_HIP45058_0001 Please acknowledge receipt of the e-mail and the delivery. Kind regards, Ulrich Take Note of the Tar File & the New MC name (for MPS email and for steps below) GYRONOD_PHOT_PACS_FULL_1_20100920.tar (Note: Name given in delivery note is incorrect - checked on CVS server) New MC - MC P57_GYRO 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 = 5.0.5_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_H57_P57_S59_GYRO 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24/HIFI> mkdir HIFI_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle024_PACS_GYRO_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H55_P56_S57_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO> 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_H57_P57_S59_GYRO 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. HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H57_P56_S59_CAL/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> ls CYCLE024_HIFI_FULL_1_20100914.tar HIFI_AOR_C024_57.aor HIFI_MC_R066_FULL_57_0_CUS_CAL.xml HIFI_Readme_C024_57.txt duration_cal.sh* HIFI_DUR_C024_57.txt HIFI_MC_R066_FULL_57_0_CUS.def summary_HIFI_AOR_C024_57.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> rm summary_HIFI_AOR_C024_57.log rm: remove regular file `summary_HIFI_AOR_C024_57.log'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> ls CYCLE024_HIFI_FULL_1_20100914.tar HIFI_AOR_C024_57.aor HIFI_MC_R066_FULL_57_0_CUS_CAL.xml HIFI_Readme_C024_57.txt duration_cal.sh* HIFI_DUR_C024_57.txt HIFI_MC_R066_FULL_57_0_CUS.def SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H54ASTR_P55ASTR_S59ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/SPIRE> ls CYCLE023_SPIRE_FULL_1_0_20100826.tar SPIRE_Duration.txt SPIRE_AOR_C023_59_CAL.aor SPIRE_harness_duration_summary_20100827_11h06m13s.log SPIRE_AOR_C023_59_ENG.aor SPIRE_harness_duration_summary_20100827_14h03m54s.log SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv85_C023_59_CUS_CAL.xml SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv85_C023_59_CUS.def SPIRE_CUS_THCP.py~ SPIRE_Readme_C023_59.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_Cycle24/PACS/GYRO> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24/PACS/GYRO> 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_Cycle24/PACS/GYRO> cvs co develop/data/observingmodes/rp_cycles/cycle024/GYRONOD_PHOT_PACS_FULL_1_20100920.tar U develop/data/observingmodes/rp_cycles/cycle024/GYRONOD_PHOT_PACS_FULL_1_20100920.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24/PACS/GYRO> cp develop/data/observingmodes/rp_cycles/cycle024/GYRONOD_PHOT_PACS_FULL_1_20100920.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24/PACS/GYRO> ls develop/ GYRONOD_PHOT_PACS_FULL_1_20100920.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24/PACS/GYRO> tar -xvf GYRONOD_PHOT_PACS_FULL_1_20100920.tar PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS.def PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS_CAL.xml PACS_AOR_GYRO_PHOT_57.aor PACS_Duration_PACS_compare.txt PACS_Readme_GYRO_PHOT_57.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24/PACS/GYRO> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt develop/ PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS_CAL.xml GYRONOD_PHOT_PACS_FULL_1_20100920.tar PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS.def PACS_AOR_GYRO_PHOT_57.aor PACS_Readme_GYRO_PHOT_57.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle24/PACS/GYRO> cp * /home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_GYRO_PHOT_57.txt GYRONOD_PHOT_PACS_FULL_1_20100920.tar PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS_CAL.xml PACS_AOR_GYRO_PHOT_57.aor PACS_MC_GYRO_T1_2010-09-20A_C024_57_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/mission_config/MC_H57_P57_S59_GYRO/PACS> Sep 20, 2010 4:49:46 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 4:49:46 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 4:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 4:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 4:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 4:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 4:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 4:49:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 4:49:47 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 20, 2010 4:50:02 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_H57_P57_S59_GYRO/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Sep 20, 2010 4:50:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 4:50:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 4:50:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 4:50:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 4:50:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 4:50:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 4:50:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 4:50:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 4:50:35 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Sep 20, 2010 4:50:56 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 4:50:57 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 4:50:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 4:50:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 4:50:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 4:50:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 4:50:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 4:50:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 4:51:01 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 57.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS> cus -m "upload PACS_MC_57GYRO mission configuration" -import PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS.def -importcaltables PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS_CAL.xml Sep 20, 2010 6:33:56 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 6:33:57 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 6:33:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:33:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:33:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:33:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:33:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:33:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:34:17 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 20, 2010 6:34:17 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 20, 2010 6:34:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:34:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:34:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:34:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:34:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:34:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:34:17 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 20, 2010 6:34:23 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_GYRO_T1_2010-09-20A_C024_57_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_GYRO_T1_2010-09-20A_C024_57_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 4.3.0 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_GYRO_PHOT_57.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS> ls -ls total 11084 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Sep 20 18:41 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Sep 20 18:41 2createOBSMODtable4RP.sh~* 5532 -rw-r--r-- 1 hscphs2 herschel 5652480 Sep 20 14:11 GYRONOD_PHOT_PACS_FULL_1_20100920.tar 4 -rw-r--r-- 1 hscphs2 herschel 71 Sep 20 18:41 msgPacsCal_PacsPhotoGyro.txt 8 -rw-r--r-- 1 hscphs2 herschel 6815 Sep 20 12:09 PACS_AOR_GYRO_PHOT_57.aor 4 -rw-r--r-- 1 hscphs2 herschel 142 Sep 20 13:50 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 142 Sep 20 18:41 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404091 Sep 20 13:50 PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS_CAL.xml 5116 -rw-r--r-- 1 hscphs2 herschel 5223226 Sep 20 13:50 PACS_MC_GYRO_T1_2010-09-20A_C024_57_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 3730 Sep 20 14:05 PACS_Readme_GYRO_PHOT_57.txt 4 -rw-r--r-- 1 hscphs2 herschel 128 Sep 20 18:41 tmp 0 -rw-r--r-- 1 hscphs2 herschel 44 Sep 20 18:41 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/PACS> 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 special MC P57GYRO 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_H57_P57_S59_GYRO/PACS> missetup -addconfig MC_H57_P57_S59_GYRO Sep 20, 2010 6:48:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 6:48:11 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 6:48:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:48:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:48:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:48:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:48:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:48:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:48:11 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Sep 20, 2010 6:48:15 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H57_P57_S59_GYRO" 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_H57_P57_S59_GYRO/PACS> Sep 20, 2010 6:49:17 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 6:49:17 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 6:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:49:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:49:18 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Sep 20, 2010 6:50:06 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H57_P57_S59_GYRO" Sep 20, 2010 6:50:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:50:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:50:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:50:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:50:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:50:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:50:17 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 20, 2010 6:51:34 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(a) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> 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_H57_P57_S59_GYRO/HIFI> Sep 20, 2010 6:52:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 6:52:43 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 6:52:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:52:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:52:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:52:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:52:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:52:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:52:44 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 20, 2010 6:52:54 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_H57_P57_S59_GYRO/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Sep 20, 2010 6:53:26 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 6:53:27 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 6:53:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:53:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:53:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:53:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:53:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:53:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:53:32 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Sep 20, 2010 6:53:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 6:53:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 6:53:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:53:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:53:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:53:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:53:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:53:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:53:59 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 old Mission Configuration (H57Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> cus -m "upload HIFI MC57Cal mission config" -import HIFI_MC_R066_FULL_57_0_CUS.def -importcaltables HIFI_MC_R066_FULL_57_0_CUS_CAL.xml Sep 20, 2010 6:54:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 6:54:50 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 6:54:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:54:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:54:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:54:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:54:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:54:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:55:08 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 20, 2010 6:55:08 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 20, 2010 6:55:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:55:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 6:55:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:55:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 6:55:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:55:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 6:55:08 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 20, 2010 6:55:13 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R066_FULL_57_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_R066_FULL_57_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_H57_P57_S59_GYRO/HIFI> ./duration_cal.sh HIFI_AOR_C024_57 next AOR file = HIFI_AOR_C024_57 -- mode HifiEng_Diplexer_calibration_vs_D2_COP -- mode HifiEng_Fast_LCU_HK_COP -- mode HifiMappingModeFastDBSRaster -- mode HifiPointProcLoadChopNoRef_FCal -- mode HifiPointProcLoadChopNoRef -- mode HifiPointModeDBS -- mode HifiPointModeFastDBS -- mode HifiPointModeFSwitch -- mode HifiPointModeFSwitchNoRef -- mode HifiPointModeLoadChop -- mode HifiPointModeLoadChopNoRef -- mode HifiPointModePositionSwitch -- mode HifiMappingModeDBSCross -- mode HifiMappingModeDBSRaster -- mode HifiMappingModeFastDBSCross -- mode HifiMappingModeFastDBSRaster -- mode HifiMappingModeFSwitchOTF -- mode HifiMappingModeFSwitchOTFNoRef -- mode HifiMappingModeLoadChopOTF -- mode HifiMappingModeLoadChopOTFNoRef -- mode HifiMappingModeOTF -- mode HifiSScanModeDBS -- mode HifiSScanModeFastDBS -- mode HifiSScanModeFSwitch -- mode HifiSScanModeFSwitchNoRef -- mode HifiSScanModeLoadChop -- mode HifiSScanModeLoadChopNoRef Total duration of HifiEng_Diplexer_calibration_vs_D2_COP with default parameters = 5099 Total duration of HifiEng_Fast_LCU_HK_COP with default parameters = 328 Total duration of HifiMappingModeFastDBSRaster with default parameters = 209 Total duration of HifiPointProcLoadChopNoRef_FCal with default parameters = 125 Total duration of HifiPointProcLoadChopNoRef with default parameters = 123 Total duration of HifiPointModeDBS with default parameters = 157 Total duration of HifiPointModeFastDBS with default parameters = 145 Total duration of HifiPointModeFSwitch with default parameters = 180 Total duration of HifiPointModeFSwitchNoRef with default parameters = 156 Total duration of HifiPointModeLoadChop with default parameters = 147 Total duration of HifiPointModeLoadChopNoRef with default parameters = 123 Total duration of HifiPointModePositionSwitch with default parameters = 139 Total duration of HifiMappingModeDBSCross with default parameters = 497 Total duration of HifiMappingModeDBSRaster with default parameters = 233 Total duration of HifiMappingModeFastDBSCross with default parameters = 425 Total duration of HifiMappingModeFastDBSRaster with default parameters = 209 Total duration of HifiMappingModeFSwitchOTF with default parameters = 235 Total duration of HifiMappingModeFSwitchOTFNoRef with default parameters = 162 Total duration of HifiMappingModeLoadChopOTF with default parameters = 202 Total duration of HifiMappingModeLoadChopOTFNoRef with default parameters = 129 Total duration of HifiMappingModeOTF with default parameters = 168 Total duration of HifiSScanModeDBS with default parameters = 386 Total duration of HifiSScanModeFastDBS with default parameters = 338 Total duration of HifiSScanModeFSwitch with default parameters = 500 Total duration of HifiSScanModeFSwitchNoRef with default parameters = 417 Total duration of HifiSScanModeLoadChop with default parameters = 350 Total duration of HifiSScanModeLoadChopNoRef with default parameters = 285 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> ls -ls total 11280 5632 -rw-r--r-- 1 hscphs2 herschel 5754880 Sep 15 10:20 CYCLE024_HIFI_FULL_1_20100914.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Sep 14 18:05 duration_cal.sh* 132 -rw-r--r-- 1 hscphs2 herschel 129969 Sep 15 10:09 HIFI_AOR_C024_57.aor 4 -rw-r--r-- 1 hscphs2 herschel 2013 Sep 15 10:03 HIFI_DUR_C024_57.txt 2172 -rw-r--r-- 1 hscphs2 herschel 2215354 Sep 14 17:43 HIFI_MC_R066_FULL_57_0_CUS_CAL.xml 3324 -rw-r--r-- 1 hscphs2 herschel 3391651 Sep 14 17:43 HIFI_MC_R066_FULL_57_0_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5423 Sep 15 10:16 HIFI_Readme_C024_57.txt 4 -rw-r--r-- 1 hscphs2 herschel 2013 Sep 20 18:57 summary_HIFI_AOR_C024_57.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/HIFI> diff HIFI_DUR_C024_57.txt summary_HIFI_AOR_C024_57.log No differences. 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 H57CAL 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_H57_P57_S59_GYRO/HIFI> Sep 20, 2010 7:00:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 7:00:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 7:00:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:00:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:00:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:00:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:00:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:00:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:00:08 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Sep 20, 2010 7:00:27 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H57_P57_S59_GYRO" Sep 20, 2010 7:00:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:00:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:00:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:00:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:00:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:00:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:00:41 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 20, 2010 7:00:58 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_H57_P57_S59_GYRO/SPIRE> Sep 20, 2010 7:02:02 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 7:02:02 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 7:02:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:02:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:02:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:02:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:02:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:02:03 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:02:03 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 20, 2010 7:02:16 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_H57_P57_S59_GYRO/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Sep 20, 2010 7:02:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 7:02:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 7:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:02:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:02:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:02:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:02:45 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Sep 20, 2010 7:03:24 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 7:03:25 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 7:03:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:03:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:03:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:03:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:03:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:03:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:03:28 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 59.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/SPIRE> cus -m "upload SPIRE MC_59ASTR mission config as CAL" -import SPIRE_MC_ASTR_pv85_C023_59_CUS.def -importcaltables SPIRE_MC_ASTR_pv85_C023_59_CUS_CAL.xml Sep 20, 2010 7:04:24 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 7:04:24 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 7:04:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:04:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:04:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:04:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:04:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:04:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:04:36 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Sep 20, 2010 7:04:36 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Sep 20, 2010 7:04:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:04:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:04:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:04:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:04:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:04:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:04:37 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 20, 2010 7:04:39 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv85_C023_59_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_ASTR_pv85_C023_59_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/SPIRE> ls -ls total 4872 2420 -rw-r--r-- 1 hscphs2 herschel 2467840 Aug 26 18:47 CYCLE023_SPIRE_FULL_1_0_20100826.tar 12 -rw-r--r-- 1 hscphs2 herschel 11100 Aug 26 18:09 SPIRE_AOR_C023_59_CAL.aor 12 -rw-r--r-- 1 hscphs2 herschel 11937 Aug 26 18:08 SPIRE_AOR_C023_59_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2023 Sep 20 19:05 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1203 Aug 27 13:51 SPIRE_CUS_THCP.py 4 -rw-r--r-- 1 hscphs2 herschel 1191 Aug 27 13:51 SPIRE_CUS_THCP.py~ 8 -rw-r--r-- 1 hscphs2 herschel 5451 Aug 26 18:32 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Aug 27 11:06 SPIRE_harness_duration_summary_20100827_11h06m13s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Aug 27 14:03 SPIRE_harness_duration_summary_20100827_14h03m54s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Sep 20 19:17 SPIRE_harness_duration_summary_20100920_19h17m04s.log 276 -rw-r--r-- 1 hscphs2 herschel 277205 Aug 26 18:39 SPIRE_MC_ASTR_pv85_C023_59_CUS_CAL.xml 2100 -rw-r--r-- 1 hscphs2 herschel 2140168 Aug 26 18:32 SPIRE_MC_ASTR_pv85_C023_59_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5218 Aug 26 18:37 SPIRE_Readme_C023_59.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H57_P57_S59_GYRO/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20100920_19h17m04s.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 S59ASTR as CAL. 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_H57_P57_S59_GYRO/SPIRE> Sep 20, 2010 7:19:11 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 7:19:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 7:19:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:19:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:19:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:19:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:19:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:19:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:19:12 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Sep 20, 2010 7:19:26 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H57_P57_S59_GYRO" Sep 20, 2010 7:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:19:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:19:36 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Sep 20, 2010 7:19:46 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_H57_P57_S59_GYRO Skipped. This part was done directly by Rafa... Source the PHS Environment for 5.0.5_phs hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v5.0.5_phs hscphs2@heropl02/home/hscphs2> Sep 20, 2010 7:23:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Sep 20, 2010 7:23:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Sep 20, 2010 7:23:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:23:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Sep 20, 2010 7:23:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:23:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Sep 20, 2010 7:23:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Sep 20, 2010 7:23:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Running CDH.getObsProgrammes() Sep 20, 2010 7:23:11 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Sep 20, 2010 7:23:11 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 24 Sep 20, 2010 7:23:11 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Sep 20, 2010 7:23:11 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H57_P57_S59_GYRO" Sep 20, 2010 7:23:14 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 3302 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_H57_P57_S59_GYRO Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H57_P57_S59_GYRO hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> cd MC_H57_P57_S59_GYRO Example of the last entry in the log: Sep 15, 2010 2:13:07 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H57_P56_S59_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Sep 15, 2010 2:13:07 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H57_P56_S59_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H57_P57_S59_GYRO> ls *.prop > & MC_H57_P56_S59_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H57_P56_S59_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 17997 Sep 15 14:13 MC_H57_P56_S59_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H57_P57_S59_GYRO> cp MC_H57_P56_S59_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_H57_P57_S59_GYRO.txt MC_H57_P56_S59_CAL.txt 17a18 > HifiEng_Fast_LCU_HK_COPGen.prop 33a35 > HifiEng_Multiple_Comb_COPGen.prop If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. Two new HIFI scripts. Notify Eva & Jose Re-join here... 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_H57_P56_S59_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_H57_P57_S59_GYRO> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H5_P56_S59_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_H54ASTR_P55ASTR_S59ASTR_RP_100827 #hcss.phs.timeEstimatorVersion=MC_H58ASTR_P55ASTR_S59ASTR_RP_100916 #hcss.phs.timeEstimatorVersion=MC_H57_P56_S59_CAL_100915 hcss.phs.timeEstimatorVersion=MC_H57_P57_S59_GYRO-100922 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H54ASTR_P55ASTR_S59ASTR_RP #hcss.ccm.mission.config = MC_H58ASTR_P55ASTR_S59ASTR_RP #hcss.ccm.mission.config = MC_H57_P56_S59_CAL hcss.ccm.mission.config = MC_H57_P57_S59_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H54ASTR_P55ASTR_S59ASTR_RP #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H58ASTR_P55ASTR_S59ASTR_RP #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H57_P56_S59_CAL hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H57_P57_S59_GYRO Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.