PACS AO updated MC & Cycle 16 delivery 1. Delivery Note PACS Delivery note - 27th May 2010 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of PACS RP cycle#16 tar file onto the CVS server, including a new ASTR MC. 1. Delivery file & directory (a) OD tar file name : CYCLE016_PACS_FULL_1_20100526.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle016, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 52.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-1443 (New Astronomer Mission Configuration PACS_MC_ASTR_OT1_2010-05-26B_C016_52) SPRs affecting ASTR backend PHS-1439 (PacsPhoto) PHS-1444 (PacsLineSpec) 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 AORs on 2 SSOs, namely asteroids 21 Lutetia and 54 Alexandra The delivery contains a self-standing PACS mechanism test executed via MTL. This AOR does not require a PACS cooler recycling. It provides its own set-up and switch to safe mode and it must therefore be scheduled outside the PACS instrument set-up periods bracketed by the photometer/spectrometer orbit prologues and epilogues. It can be scheduled onto a non-PACS OD, too. 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.65 (Note at the time of writing this delivery notification this issue is still under work to include the latest updates). * RPMechChop 2.3.1A, PACS RP Cal Plan, section 8.1 engineering AOR to check the properties of the PACS chopper drive parameters after 1 year of operation: specific torque, oscillation frequency and damping * RPPhotFlux 3.2.1A & B, PACS RP Cal Plan, section 6.2 on gamma Dra - photometer flux calibration reproducibility monitoring * RPPhotFlux 3.2.4B, PACS RP Cal Plan, section 6.3 on Lutetia, Alexandra and HD 39608 - photometer flux linearity assessment and monitoring * RPSpecWave 4.2.1A, PACS RP Cal Plan, section 6.7 on NGC 6543 - spectrometer wavelength calibration monitoring * RPSpecFlux 4.3.4A, PACS RP Cal Plan, section 6.8 on HD 161796 - spectrometer flux calibration reproducibility monitoring * RPSpecFlux 7.2.1A, PACS RP Cal Plan, section 7.3 on PACS dark field - half-year telescope background assessment close to seasonal solar illumination minimum (around OD 400). Scheduling instructions per OD (from Readme file) (f) AOR distribution according to ODs and PACS sub-instruments: PACS PHOT (can be scheduled on any PACS-P OD) ============================================= RPPhotFlux_321A_cPS_repro_blu_gamDra_0008 RPPhotFlux_321B_sPS_070_repro_blu_gamDra_0008 RPPhotFlux_321B_sPS_110_repro_blu_gamDra_0008 RPPhotFlux_324B_sPS_070_2Jy_grn_Lutetia_0002 RPPhotFlux_324B_sPS_110_2Jy_grn_Lutetia_0002 RPPhotFlux_324B_sPS_070_500mJy_red_Lutetia_0002 RPPhotFlux_324B_sPS_110_500mJy_red_Lutetia_0002 RPPhotFlux_324B_sPS_070_20Jy_blu_Alexandra_0002 RPPhotFlux_324B_sPS_110_20Jy_blu_Alexandra_0002 RPPhotFlux_324B_sPS_070_10Jy_grn_Alexandra_0002 RPPhotFlux_324B_sPS_110_10Jy_grn_Alexandra_0002 RPPhotFlux_324B_sPS_070_20mJy_blu_HD39608_0002 RPPhotFlux_324B_sPS_110_20mJy_blu_HD39608_0002 RPPhotFlux_324B_sPS_070_20mJy_grn_HD39608_0002 RPPhotFlux_324B_sPS_110_20mJy_grn_HD39608_0002 Each block shall be scheduled in the indicated sequence. PACS SPEC (can be scheduled on any PACS-S OD) ============================================= RPSpecWave_421A_StdLS_NGC6543_A_0006 RPSpecWave_421A_StdLS_NGC6543_B_0006 RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0011 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0011 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0011 RPSpecFlux_721A_StdSED_sedb2a_s_DarkField_0002 RPSpecFlux_721A_StdSED_sedb2b_s_DarkField_0002 RPSpecFlux_721A_StdSED_sedb3a_s_DarkField_0002 RPSpecFlux_721A_StdSED_sedb2a_m_DarkField_0002 RPSpecFlux_721A_StdSED_sedb2b_m_DarkField_0002 RPSpecFlux_721A_StdSED_sedb3a_m_DarkField_0002 RPSpecFlux_721A_StdSED_sedb2a_l_DarkField_0002 RPSpecFlux_721A_StdSED_sedb2b_l_DarkField_0002 RPSpecFlux_721A_StdSED_sedb3a_l_DarkField_0002 Each block shall be scheduled in the indicated sequence. PACS Mechanism Check ==================== RPMechChop_231A_nStd_OpenLoopFullRange_na_0001 This is an engineering AOR without any pointing request. It can be scheduled also on non PACS ODs, preferentially inside the DTCP. If it is scheduled on a PACS OD, it must be scheduled either as the first AOR (before cooler recycling and/or orbit prologue) or as the very last AOR after the final orbit epilogue of that OD. 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) CYCLE016_PACS_FULL_1_20100526.tar New MCs - MC P52ASTR 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_H42ASTR_P52ASTR_S55ASTR_AO 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/HIFI> mkdir PACS_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle016_PACS_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the SPIRE directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H42_P49_S55_CAL folder. Next remove in the SPIRE & HIFI subfolders all files which were created when you ran the SPIRE duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H42ASTR_P48ASTR_S55ASTR_AO/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> ls CYCLE014_SPIRE_UPDATE_1_3_20100511.tar SPIRE_harness_duration_summary_20100512_11h28m24s.log SPIRE_cus_scripts.txt SPIRE_harness_duration_summary_20100512_15h50m08s.log SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml SPIRE_Duration.txt SPIRE_MC_ASTR_pv81_C014_55_CUS.def SPIRE_harness_duration_summary_20100512_11h23m32s.log SPIRE_Readme_C014_55.txt HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H42ASTR_P48ASTR_S55ASTR_AO/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0011_C014_42_CUS_CAL.xml importall.sh* CYCLE014_HIFI_FULL_2_20100512.tar HIFI_MC_ASTR_A0011_C014_42_CUS.def Summary_durations.txt default-durations.dat HIFI_MC_ASTR_A0011_C014_42.txt 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle016/CYCLE016_PACS_FULL_1_20100526.tar U develop/data/observingmodes/rp_cycles/cycle016/CYCLE016_PACS_FULL_1_20100526.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle016/CYCLE016_PACS_FULL_1_20100526.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/PACS/PACS_FULL_1> ls CYCLE016_PACS_FULL_1_20100526.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/PACS/PACS_FULL_1> tar -xvf CYCLE016_PACS_FULL_1_20100526.tar PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS.def PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS_CAL.xml PACS_AOR_C016_52.aor PACS_Duration_PACS_compare.txt PACS_Readme_C016_52.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/PACS/PACS_FULL_1> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt CYCLE016_PACS_FULL_1_20100526.tar PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS_CAL.xml develop/ PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS.def PACS_AOR_C016_52.aor PACS_Readme_C016_52.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle16/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C016_52.txt CYCLE016_PACS_FULL_1_20100526.tar PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS_CAL.xml PACS_AOR_C016_52.aor PACS_MC_ASTR_OT1_2010-05-26B_C016_52_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_H42ASTR_P52ASTR_S55ASTR_AO/PACS> May 27, 2010 9:49:43 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 9:49:44 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 9:49:45 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:49:45 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:49:45 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:49:45 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:49:45 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument May 27, 2010 9:49:53 AM 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_H42ASTR_P52ASTR_S55ASTR_AO/PACS> cus -f -m "clean PACS CUS from DB" -deleteall May 27, 2010 9:54:26 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 9:54:27 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 9:54:27 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:54:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:54:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:54:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:54:38 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall May 27, 2010 9:54:43 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 9:54:44 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 9:54:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:54:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:54:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:54:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:54:51 AM 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 52.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/PACS> cus -m "upload PACS_MC P52ASTR mission config" -import PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS.def -importcaltables PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS_CAL.xml May 27, 2010 9:56:28 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 9:56:29 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 9:56:29 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:56:29 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:56:29 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:56:30 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:56:55 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported May 27, 2010 9:56:55 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory May 27, 2010 9:56:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:56:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 9:56:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:56:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 9:57:00 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT1_2010-05-26B_C016_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_OT1_2010-05-26B_C016_52_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_H42ASTR_P52ASTR_S55ASTR_AO/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C016_52.aor /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/PACS> ls -ls total 11176 4 -rwxr-xr-- 1 hscphs2 herschel 1538 May 27 09:58 2createOBSMODtable4RP.sh* 5572 -rw-r--r-- 1 hscphs2 herschel 5693440 May 26 20:22 CYCLE016_PACS_FULL_1_20100526.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 May 27 10:00 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 84 May 27 09:59 msgPacsEng_ChopperOpenLoop_FullRange.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 May 27 10:00 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 May 27 10:00 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 May 27 10:01 msgPacsRangeSpec.txt 148 -rw-r--r-- 1 hscphs2 herschel 147417 May 26 20:03 PACS_AOR_C016_52.aor 4 -rw-r--r-- 1 hscphs2 herschel 1882 May 26 20:07 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 1882 May 27 10:01 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404091 May 26 20:01 PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS_CAL.xml 5020 -rw-r--r-- 1 hscphs2 herschel 5126639 May 26 20:01 PACS_MC_ASTR_OT1_2010-05-26B_C016_52_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5948 May 26 20:20 PACS_Readme_C016_52.txt 4 -rw-r--r-- 1 hscphs2 herschel 1212 May 27 09:59 tmp 4 -rw-r--r-- 1 hscphs2 herschel 411 May 27 09:59 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/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 MC P52ASTR 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_H42ASTR_P52ASTR_S55ASTR_AO/PACS> missetup -addconfig MC_H42ASTR_P52ASTR_S55ASTR_AO May 27, 2010 10:07:27 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 10:07:27 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 10:07:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:07:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:07:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:07:28 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:07:28 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" May 27, 2010 10:07:28 AM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H42ASTR_P52ASTR_S55ASTR_AO" 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_H42ASTR_P52ASTR_S55ASTR_AO/PACS> May 27, 2010 10:07:54 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 10:07:54 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 10:07:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:07:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:07:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:07:55 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:07:55 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument May 27, 2010 10:08:30 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H42ASTR_P52ASTR_S55ASTR_AO" May 27, 2010 10:08:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:08:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:08:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:08:44 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:09:26 AM 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(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_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> May 27, 2010 10:17:46 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 10:17:47 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 10:17:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:17:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:17:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:17:48 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:17:48 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument May 27, 2010 10:17:56 AM 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_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall May 27, 2010 10:18:20 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 10:18:21 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 10:18:21 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:18:21 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:18:21 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:18:21 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:18:30 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall May 27, 2010 10:18:34 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 10:18:35 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 10:18:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:18:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:18:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:18:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:18:41 AM 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 (H42_ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> cus -m "upload HIFI MC H42ASTR mission config" -import HIFI_MC_ASTR_A0011_C014_42_CUS.def -importcaltables HIFI_MC_ASTR_A0011_C014_42_CUS_CAL.xml May 27, 2010 10:19:50 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 10:19:51 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 10:19:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:19:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:19:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:19:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:20:05 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported May 27, 2010 10:20:05 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory May 27, 2010 10:20:06 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:20:06 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 10:20:06 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:20:06 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 10:20:11 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0011_C014_42_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_ASTR_A0011_C014_42_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_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> rm Summary_durations.txt rm: remove regular file `Summary_durations.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> ls -ls total 6300 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 11:33 cus-defdur.sh* 3128 -rw-r--r-- 1 hscphs2 herschel 3194880 May 12 10:37 CYCLE014_HIFI_FULL_2_20100512.tar 32 -rw-r--r-- 1 hscphs2 herschel 29199 May 12 10:35 default-durations.dat 1280 -rw-r--r-- 1 hscphs2 herschel 1303344 May 11 21:21 HIFI_MC_ASTR_A0011_C014_42_CUS_CAL.xml 1816 -rw-r--r-- 1 hscphs2 herschel 1854323 May 11 21:21 HIFI_MC_ASTR_A0011_C014_42_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1204 May 12 10:03 HIFI_MC_ASTR_A0011_C014_42.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 20:54 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29199 May 27 10:43 Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> diff default-durations.dat Summary_durations.txt Perfect! 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 H42ASTR 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_H42ASTR_P52ASTR_S55ASTR_AO/HIFI> May 27, 2010 11:02:50 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 11:02:51 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 11:02:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:02:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:02:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:02:51 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:02:51 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument May 27, 2010 11:03:16 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H42ASTR_P52ASTR_S55ASTR_AO" May 27, 2010 11:03:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:03:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:03:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:03:34 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:05:01 AM 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_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> May 27, 2010 11:05:42 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 11:05:43 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 11:05:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:05:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:05:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:05:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:05:43 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument May 27, 2010 11:07:09 AM 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_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall May 27, 2010 11:07:39 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 11:07:40 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 11:07:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:07:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:07:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:07:40 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:07:48 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall May 27, 2010 11:07:53 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 11:07:54 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 11:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:07:54 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:07:59 AM 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 55.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> cus -m "upload SPIRE MC_55ASTR mission config" -import SPIRE_MC_ASTR_pv81_C014_55_CUS.def -importcaltables SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml May 27, 2010 11:09:23 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 11:09:24 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 11:09:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:09:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:09:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:09:24 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:09:41 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported May 27, 2010 11:09:41 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory May 27, 2010 11:09:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:09:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:09:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:09:41 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:09:44 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by PACS: SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> ls -ls total 4684 2328 -rw-r--r-- 1 hscphs2 herschel 2375680 May 11 18:30 CYCLE014_SPIRE_UPDATE_1_3_20100511.tar 4 -rw-r--r-- 1 hscphs2 herschel 1912 May 27 11:10 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 May 11 18:14 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5085 May 11 18:14 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5085 May 12 11:28 SPIRE_harness_duration_summary_20100512_11h28m24s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5085 May 12 15:50 SPIRE_harness_duration_summary_20100512_15h50m08s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5085 May 27 11:14 SPIRE_harness_duration_summary_20100527_11h14m24s.log 276 -rw-r--r-- 1 hscphs2 herschel 276611 May 11 18:14 SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml 2036 -rw-r--r-- 1 hscphs2 herschel 2078073 May 11 18:14 SPIRE_MC_ASTR_pv81_C014_55_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 3203 May 11 18:27 SPIRE_Readme_C014_55.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20100527_11h14m24s.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 S55ASTR 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_H42ASTR_P52ASTR_S55ASTR_AO/SPIRE> May 27, 2010 11:20:02 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 11:20:03 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 11:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:20:03 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument May 27, 2010 11:20:20 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H42ASTR_P52ASTR_S55ASTR_AO" May 27, 2010 11:20:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:20:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:20:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:20:35 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:20:51 AM 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_H42ASTR_P52ASTR_S55ASTR_AO 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> May 27, 2010 11:23:33 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties May 27, 2010 11:23:33 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int May 27, 2010 11:23:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:23:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int May 27, 2010 11:23:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int May 27, 2010 11:23:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Running CDH.getObsProgrammes() May 27, 2010 11:23:39 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... May 27, 2010 11:23:39 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 33 May 27, 2010 11:23:39 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... May 27, 2010 11:23:39 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H42ASTR_P52ASTR_S55ASTR_AO" May 27, 2010 11:23:44 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 5331 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_H42ASTR_P52ASTR_S55ASTR_AO Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H42ASTR_P52ASTR_S55ASTR_AO Example of the last entry in the log: May 27, 2010 11:26:14 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P52ASTR_S55ASTR_AO/HifiSScanProcLoadChopNoRefGen.prop May 27, 2010 11:26:14 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P52ASTR_S55ASTR_AO/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P52ASTR_S55ASTR_AO> ls *.prop > MC_H42ASTR_P52ASTR_S55ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P52ASTR_S55ASTR_AO> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 13787 May 27 11:27 MC_H42ASTR_P52ASTR_S55ASTR_AO.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P52ASTR_S55ASTR_AO> cp MC_H42ASTR_P52ASTR_S55ASTR_AO.txt /home/hscphs2/icchsc/HSpot_files/ hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H42ASTR_P52ASTR_S55ASTR_AO> cd .. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_H42ASTR_P51ASTR_S55ASTR_AO.txt MC_H42ASTR_P52ASTR_S55ASTR_AO.txt If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. No new PACS script. Do not notify Eva & Jose 12. Final Jboss Activities Log into Jboss #2 herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02_old 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_H42ASTR_P52ASTR_S55ASTR_AO 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_H42ASTR_P52ASTR_S55ASTR_AO> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H42ASTR_P52ASTR_S55ASTR_AO/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit HCSS_PHS_TEST_herjbo02_0_6_6.props & [1] 3171 Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #MARK TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_H42ASTR_P48ASTR_S52ASTR_RP_100524 #hcss.phs.timeEstimatorVersion=MC_H43_P50_S56_CAL_100521 #hcss.phs.timeEstimatorVersion=MC_H42_P49_S55_CAL_100517 hcss.phs.timeEstimatorVersion=MC_H42ASTR_P52ASTR_S55ASTR_AO_100527 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H42ASTR_P48ASTR_S52ASTR_RP #hcss.ccm.mission.config = MC_H43_P50_S56_CAL #hcss.ccm.mission.config = MC_H42_P49_S55_CAL hcss.ccm.mission.config = MC_H42ASTR_P52ASTR_S55ASTR_AO #MARK DIRECTORIES #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H42ASTR_P48ASTR_S52ASTR_RP #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H43_P50_S56_CAL #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H42_P49_S55_CAL hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H42ASTR_P52ASTR_S55ASTR_AO Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.