PACSE Cycle 29 ASTR MC & engineering set-up delivery 1. Delivery Note PACS Delivery note - 23rd November 2010 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of the PACS RP calibration cycle#29 tar file onto the CVS server, including a new Astronomer Mission Configuration. 1. Delivery file & directory (a) OD tar file name : CYCLE029_PACS_FULL_1_20101123.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle029, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 59.0 2. Mission Configurations (a) Does this delivery include a new Calibration mission configuration? YES PACS-3137: EDAC mapping of the addresses of single memory failures into the configurable HK. (b) Does this delivery include a new ASTR mission configuration? YES high level SCR for cCCB: PHS-1578 (New Astronomer Mission Configuration PACS_MC_ASTR_OT1_2010-11-23A_C029_59) SPRs affecting ASTR backend PACS-3169 (PacsRangeSpec) 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 observations on 2 SSOs, namely planet Uranus and asteroid 3 Juno. Please note, that Uranus is located inside the default avoidance constraint of Jupiter and that its constraint enabling must be set to false. The delivery contains for the first time a no-pointing engineering observation to read the addresses affected by single memory failures and corrected by the onboard EDACs. For the time being, this engineering AOR will be submitted by PACS-ICC once per calibration cycle for scheduling on PACS ODs. Since start address or offset of this address reading will likely change with time (only 10 addresses can be read out), the PACS-ICC will maintain the AORs follwoing feedback from the PACS-ICC trend analysis. 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 1.00.) * RPPhotFlux 3.2.4A&B, PACS RP Cal Plan, section 6.3 on alpha Boo - monitor the photometer linearity and absolute flux calibration for chop/nod and mini scan map point source modes. * RPPhotFlux 3.2.4A, PACS RP Cal Plan, section 6.3 on Juno - monitor the photometer linearity and absolute flux calibration for chop/nod point source mode (complemented by Herschel-Planck cross-calibration scan maps on same target). * RPPhotFlux 6.3.1A, PACS RP Cal Plan, section 10.6 on asteroid Juno - Herschel-Planck cross-calibration synchronized with Planck sightings. * RPSpecFlux 4.3.3B, PACS RP Cal Plan, section 6.8 on Uranus - monitor linearity with flux of the spectrometer and absolute flux calibration against external sources at key wavelengths in unchopped mode; also cross-calibration with chopped mode. * RPSpecFlux 4.3.4A, PACS RP Cal Plan, section 6.7 on HD 161796 - monitor absolute flux calibration reproducibility of the spectrometer. * RPSpecFlux 4.3.8B, PACS RP Cal Plan, section 6.9 on Uranus - monitor the relative spectral response function of the spectrometer in unchopped mode; also cross-calibration with chopped mode. * RPSpecFlux 6.1.1A, PACS RP Cal Plan, section 10.9 on Juno - PACS spectrometer vs. photometer cross-calibration on point sources, spectrometer SED mode calibration. * RPSpecFlux 7.2.1A, PACS RP Cal Plan, section 7.3 on PACS dark field - half-year telescope background assessment with the spectrometer close to seasonal solar illumination maximum (around OD 590). * RPElecEDAC 8.1.1A, PACS RP Cal Plan, section 7.4 no pointing - monitor the EDAC addresses of single memory failures. Scheduling instructions per OD (from Readme file) (f) AOR distribution according to ODs and PACS sub-instruments: PACS PHOT (to be scheduled on any PACS PHOT OD) =============================================== RPPhotFlux_324A_cPS_20Jy_blu_alfBoo_0002 RPPhotFlux_324B_sPS_070_20Jy_blu_alfBoo_0002 RPPhotFlux_324B_sPS_110_20Jy_blu_alfBoo_0002 RPPhotFlux_324A_cPS_10Jy_grn_alfBoo_0002 RPPhotFlux_324B_sPS_070_10Jy_grn_alfBoo_0002 RPPhotFlux_324B_sPS_110_10Jy_grn_alfBoo_0002 This block shall be scheduled in the indicated sequence. PACS PHOT (to be scheduled on shared PACS PHOT/SPEC OD 593) =========================================================== RPPhotFlux_324A_cPS_10Jy_grn_Juno_0002 RPPhotFlux_631A_sPS_070_10Jy_grn_Juno_0001 RPPhotFlux_631A_sPS_110_10Jy_grn_Juno_0001 RPPhotFlux_324A_cPS_20Jy_blu_Juno_0002 RPPhotFlux_631A_sPS_070_20Jy_blu_Juno_0001 RPPhotFlux_631A_sPS_110_20Jy_blu_Juno_0001 This block shall be scheduled in the indicated sequence, immediately before the PACS photometer orbit epilogue. PACS SPEC (to be scheduled on shared PACS PHOT/SPEC OD 593) =========================================================== RPSpecFlux_611A_StdSED_sedb2a_Juno_0001 RPSpecFlux_611A_StdSED_sedb2b_Juno_0001 RPSpecFlux_611A_StdSED_sedb3a_Juno_0001 This block shall be scheduled in the indicated sequence, just after the PACS spectrometer orbit prologue. PACS SPEC (to be scheduled on PACS SPEC OD 589) =============================================== RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0026 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0026 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0026 This block shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS SPEC OD 590) =============================================== RPSpecFlux_721A_StdSED_sedb2a_s_DarkField_0003 RPSpecFlux_721A_StdSED_sedb2b_s_DarkField_0003 RPSpecFlux_721A_StdSED_sedb3a_s_DarkField_0003 RPSpecFlux_721A_StdSED_sedb2a_m_DarkField_0003 RPSpecFlux_721A_StdSED_sedb2b_m_DarkField_0003 RPSpecFlux_721A_StdSED_sedb3a_m_DarkField_0003 RPSpecFlux_721A_StdSED_sedb2a_l_DarkField_0003 RPSpecFlux_721A_StdSED_sedb2b_l_DarkField_0003 RPSpecFlux_721A_StdSED_sedb3a_l_DarkField_0003 RPSpecFlux_433B_StdRange_UnchopFluxB2A_Uranus_01 RPSpecFlux_433B_StdRange_UnchopFluxB2A_UranusOff_01 RPSpecFlux_433B_StdRange_UnchopFluxB2B_Uranus_01 RPSpecFlux_433B_StdRange_UnchopFluxB2B_UranusOff_01 RPSpecFlux_433B_StdRange_UnchopFluxB3A_Uranus_01 RPSpecFlux_433B_StdRange_UnchopFluxB3A_UranusOff_01 RPSpecFlux_438B_StdSED_nochop_sedb2a_Uranus_0001 RPSpecFlux_438B_StdSED_nochop_sedb2a_UranusOff_0001 RPSpecFlux_438B_StdSED_nochop_sedb2b_Uranus_0001 RPSpecFlux_438B_StdSED_nochop_sedb2b_UranusOff_0001 RPSpecFlux_438B_StdSED_nochop_sedb3a_Uranus_0001 RPSpecFlux_438B_StdSED_nochop_sedb3a_UranusOff_0001 Each block shall be scheduled in the indicated sequence. PACS Engineering (to be scheduled on PACS OD 589) ================================================= RPElecEDAC_811A_5476A_0_na_0001 This AOR must be scheduled immediately before the final orbit epilogue of this 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) CYCLE029_PACS_FULL_1_20101123.tar New MC - MC P59ASTR 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 4.5.0 (Always use the most recent HCSS Software version) PHS SOFTWARE = 5.1.4_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_v4.5.0 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_H62ASTR_P59ASTR_S62ASTR_RP 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle27> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle27/HIFI> mkdir PACS_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle027_PACS_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H60ASTR_P58ASTR_S60ASTR_RP> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the SPIRE & HIFI directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H62ASTR_P59ASTR_S61ASTR_RP 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_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H62ASTR_P58ASTR_S61ASTR_RP/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> ls CYCLE028_SPIRE_FULL_1_0_20101108.tar SPIRE_harness_duration_summary_20101109_15h38m18s.log SPIRE_AOR_C028_61_CAL.aor SPIRE_harness_duration_summary_20101123_09h34m04s.log SPIRE_AOR_C028_61_ENG.aor SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_ASTR_pv87_C028_61_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C028_61.txt SPIRE_Duration.txt HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H62ASTR_P58ASTR_S61ASTR_RP/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0023_C027_62_CUS_CAL.xml importall.sh* CYCLE027_HIFI_FULL_2_20101027.tar HIFI_MC_ASTR_A0023_C027_62_CUS.def Summary_durations.txt default-durations.dat HIFI_MC_ASTR_A0023_C027_62.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> rm Summary_durations.txt rm: remove regular file `Summary_durations.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0023_C027_62_CUS_CAL.xml importall.sh* CYCLE027_HIFI_FULL_2_20101027.tar HIFI_MC_ASTR_A0023_C027_62_CUS.def default-durations.dat HIFI_MC_ASTR_A0023_C027_62.txt 6(a) Download & Untar the delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> cvs login Logging in to :pserver:lorourke@cvs.rssd.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle029/CYCLE029_PACS_FULL_1_20101123.tar U develop/data/observingmodes/rp_cycles/cycle029/CYCLE029_PACS_FULL_1_20101123.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle029/CYCLE029_PACS_FULL_1_20101123.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> ls CYCLE029_PACS_FULL_1_20101123.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> tar -xvf CYCLE029_PACS_FULL_1_20101123.tar PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS.def PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS_CAL.xml PACS_AOR_C029_59.aor PACS_Duration_PACS_compare.txt PACS_Readme_C029_59.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> ls 2createOBSMODtable4RP.sh* PACS_AOR_C029_59.aor PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS.def CYCLE029_PACS_FULL_1_20101123.tar PACS_Duration_PACS_compare.txt PACS_Readme_C029_59.txt develop/ PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS_CAL.xml hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle29/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C029_59.txt CYCLE029_PACS_FULL_1_20101123.tar PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS_CAL.xml PACS_AOR_C029_59.aor PACS_MC_ASTR_OT1_2010-11-23A_C_59_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_H62ASTR_P59ASTR_S61ASTR_RP/PACS> Nov 23, 2010 6:13:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 23, 2010 6:13:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 23, 2010 6:13:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:13:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:13:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:13:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:13:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:13:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:13:06 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Nov 23, 2010 6:13:15 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_H62ASTR_P59ASTR_S61ASTR_RP/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Nov 23, 2010 6:13:46 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 23, 2010 6:13:46 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 23, 2010 6:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:13:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:13:52 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Nov 23, 2010 6:14:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 23, 2010 6:14:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 23, 2010 6:14:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:14:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:14:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:14:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:14:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:14:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:14:20 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 59.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/PACS> cus -m "upload PACS_MC P59ASTR mission config" -import PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS.def -importcaltables PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS_CAL.xml Nov 23, 2010 6:18:10 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 23, 2010 6:18:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 23, 2010 6:18:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:18:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:18:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:18:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:18:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:18:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:18:31 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Nov 23, 2010 6:18:31 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Nov 23, 2010 6:18:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:18:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:18:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:18:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:18:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:18:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:18:31 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Nov 23, 2010 6:18:35 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT1_2010-11-23A_C_59_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-11-23A_C_59_CUS_CAL.xml CONFIRMED!! 6(e) Run the duration script for the PACS instrument model: Point duration script to latest HCSS version... hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C029_59.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/PACS> ls -ls total 11340 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Nov 23 18:22 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Nov 23 18:22 2createOBSMODtable4RP.sh~* 5652 -rw-r--r-- 1 hscphs2 herschel 5775360 Nov 23 16:24 CYCLE029_PACS_FULL_1_20101123.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Nov 23 18:23 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Nov 23 18:24 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Nov 23 18:22 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Nov 23 18:24 msgPacsRangeSpec.txt 184 -rw-r--r-- 1 hscphs2 herschel 180726 Nov 23 15:58 PACS_AOR_C029_59.aor 4 -rw-r--r-- 1 hscphs2 herschel 2517 Nov 23 16:05 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2517 Nov 23 18:24 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404088 Nov 23 15:58 PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS_CAL.xml 5064 -rw-r--r-- 1 hscphs2 herschel 5171295 Nov 23 15:58 PACS_MC_ASTR_OT1_2010-11-23A_C_59_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 7604 Nov 23 16:22 PACS_Readme_C029_59.txt 4 -rw-r--r-- 1 hscphs2 herschel 1591 Nov 23 18:22 tmp 4 -rw-r--r-- 1 hscphs2 herschel 559 Nov 23 18:22 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/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 P59ASTR 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_H62ASTR_P59ASTR_S61ASTR_RP/PACS> missetup -addconfig MC_H62ASTR_P59ASTR_S61ASTR_RP Nov 23, 2010 6:26:24 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 23, 2010 6:26:25 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 23, 2010 6:26:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:26:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:26:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:26:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:26:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:26:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:26:25 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Nov 23, 2010 6:26:26 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H62ASTR_P59ASTR_S61ASTR_RP" 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_H62ASTR_P59ASTR_S61ASTR_RP/PACS> Nov 23, 2010 6:26:43 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 23, 2010 6:26:44 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 23, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:26:44 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Nov 23, 2010 6:26:58 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H62ASTR_P59ASTR_S61ASTR_RP" Nov 23, 2010 6:27:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:27:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 23, 2010 6:27:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:27:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 23, 2010 6:27:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:27:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 23, 2010 6:27:10 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Nov 23, 2010 6:28:32 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(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_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> Nov 24, 2010 8:55:55 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 8:55:55 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 8:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:55:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:55:56 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Nov 24, 2010 8:56:07 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_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Nov 24, 2010 8:56:30 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 8:56:30 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 8:56:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:56:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:56:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:56:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:56:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:56:31 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:56:38 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Nov 24, 2010 8:57:22 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 8:57:22 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 8:57:22 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:57:22 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:57:22 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:57:22 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:57:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:57:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:57:26 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 old Mission Configuration (H60_ASTR) hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> cus -m "upload HIFI MC H62ASTR mission config" -import HIFI_MC_ASTR_A0023_C027_62_CUS.def -importcaltables HIFI_MC_ASTR_A0023_C027_62_CUS_CAL.xml Nov 24, 2010 8:58:56 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 8:58:57 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 8:58:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:58:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:58:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:58:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:58:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:58:57 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:59:09 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Nov 24, 2010 8:59:09 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Nov 24, 2010 8:59:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:59:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 8:59:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:59:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 8:59:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:59:09 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 8:59:09 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Nov 24, 2010 8:59:14 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0023_C027_62_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_A0023_C027_62_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_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> ls -ls total 6416 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 2010 cus-defdur.sh* 3188 -rw-r--r-- 1 hscphs2 herschel 3256320 Oct 27 16:42 CYCLE027_HIFI_FULL_2_20101027.tar 32 -rw-r--r-- 1 hscphs2 herschel 29693 Oct 27 08:38 default-durations.dat 1276 -rw-r--r-- 1 hscphs2 herschel 1300356 Oct 27 08:38 HIFI_MC_ASTR_A0023_C027_62_CUS_CAL.xml 1876 -rw-r--r-- 1 hscphs2 herschel 1915498 Oct 27 08:38 HIFI_MC_ASTR_A0023_C027_62_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1072 Oct 27 09:14 HIFI_MC_ASTR_A0023_C027_62.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 2010 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29693 Nov 24 09:20 Summary_durations.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/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 H62ASTR 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_H62ASTR_P59ASTR_S61ASTR_RP/HIFI> Nov 24, 2010 9:26:00 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 9:26:00 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 9:26:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:26:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:26:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:26:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:26:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:26:01 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:26:01 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Nov 24, 2010 9:26:27 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H62ASTR_P59ASTR_S61ASTR_RP" Nov 24, 2010 9:26:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:26:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:26:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:26:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:26:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:26:39 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:26:39 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Nov 24, 2010 9:26:58 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_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> Nov 24, 2010 9:47:55 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 9:47:56 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 9:47:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:47:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:47:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:47:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:47:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:47:56 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:47:56 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Nov 24, 2010 9:52:15 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_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Nov 24, 2010 9:52:42 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 9:52:43 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 9:52:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:52:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:52:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:52:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:52:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:52:43 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:52:48 AM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Nov 24, 2010 9:53:58 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 9:53:58 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 9:53:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:53:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 9:53:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:53:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 9:53:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:53:59 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 9:54:02 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 new SPIRE Mission Configuration (Version 61.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> cus -m "upload SPIRE MC_61ASTR mission config" -import SPIRE_MC_ASTR_pv87_C028_61_CUS.def -importcaltables SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml Nov 24, 2010 10:10:02 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 10:10:03 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 10:10:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:10:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:10:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:10:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:10:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:10:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:10:15 AM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Nov 24, 2010 10:10:15 AM herschel.cus.gui.Cus infoMessage INFO: Using current directory Nov 24, 2010 10:10:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:10:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:10:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:10:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:10:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:10:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:10:15 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Nov 24, 2010 10:10:20 AM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv87_C028_61_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_pv87_C028_61_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> ls -ls total 5120 2540 -rw-r--r-- 1 hscphs2 herschel 2590720 Nov 8 22:55 CYCLE028_SPIRE_FULL_1_0_20101108.tar 92 -rw-r--r-- 1 hscphs2 herschel 88159 Nov 8 22:01 SPIRE_AOR_C028_61_CAL.aor 60 -rw-r--r-- 1 hscphs2 herschel 56528 Nov 8 22:02 SPIRE_AOR_C028_61_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2023 Nov 24 10:11 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Nov 8 22:47 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5451 Nov 8 22:47 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Nov 9 15:38 SPIRE_harness_duration_summary_20101109_15h38m18s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Nov 23 09:34 SPIRE_harness_duration_summary_20101123_09h34m04s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Nov 24 10:15 SPIRE_harness_duration_summary_20101124_10h15m02s.log 276 -rw-r--r-- 1 hscphs2 herschel 276744 Nov 8 22:48 SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml 2100 -rw-r--r-- 1 hscphs2 herschel 2140168 Nov 8 22:48 SPIRE_MC_ASTR_pv87_C028_61_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8934 Nov 8 22:50 SPIRE_Readme_C028_61.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20101124_10h15m02s.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 S61ASTR 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_H62ASTR_P59ASTR_S61ASTR_RP/SPIRE> Nov 24, 2010 10:19:22 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 10:19:23 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 10:19:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:19:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:19:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:19:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:19:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:19:23 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:19:23 AM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Nov 24, 2010 10:19:52 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H62ASTR_P59ASTR_S61ASTR_RP" Nov 24, 2010 10: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 Nov 24, 2010 10:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:20:03 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:20:03 AM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Nov 24, 2010 10:20:40 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_H62ASTR_P59ASTR_S61ASTR_RP Source the PHS Environment for 5.1.4_phs hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v5.1.4_phs hscphs2@heropl02/home/hscphs2/otherSetups> Nov 24, 2010 10:22:37 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Nov 24, 2010 10:22:38 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Nov 24, 2010 10:22:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:22:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Nov 24, 2010 10:22:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:22:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Nov 24, 2010 10:22:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Nov 24, 2010 10:22:38 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Running CDH.getObsProgrammes() Nov 24, 2010 10:22:38 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Nov 24, 2010 10:22:38 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 24 Nov 24, 2010 10:22:38 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Nov 24, 2010 10:22:38 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H62ASTR_P59ASTR_S61ASTR_RP" Nov 24, 2010 10:22:42 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 4168 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_H62ASTR_P59ASTR_S61ASTR_RP Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H62ASTR_P59ASTR_S61ASTR_RP Example of the last entry in the log: Nov 24, 2010 10:25:42 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H62ASTR_P59ASTR_S61ASTR_RP/HifiSScanProcLoadChopNoRefGen.prop Nov 24, 2010 10:25:42 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H62ASTR_P59ASTR_S61ASTR_RP/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H62ASTR_P59ASTR_S61ASTR_RP> ls *.prop > MC_H62ASTR_P59ASTR_S61ASTR_RP.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H62ASTR_P59ASTR_S61ASTR_RP> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 14114 Nov 24 10:31 MC_H62ASTR_P59ASTR_S61ASTR_RP.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H62ASTR_P59ASTR_S61ASTR_RP> cp MC_H62ASTR_P59ASTR_S61ASTR_RP.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_H62ASTR_P58ASTR_S61ASTR_RP.txt MC_H62ASTR_P59ASTR_S61ASTR_RP.txt 171a172 > PacsEng_Pacs_EDAC_to_DMC_HKGen.prop If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. 1 new PACS script 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_H62ASTR_P59ASTR_S61ASTR_RP 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_P48ASTR_S55ASTR_RP> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H62ASTR_P59ASTR_S61ASTR_RP/ 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_H62ASTR_P58ASTR_S61ASTR_RP_101109 hcss.phs.timeEstimatorVersion=MC_H62ASTR_P59ASTR_S61ASTR_RP_101124 #hcss.phs.timeEstimatorVersion=MC_H61_P58_S60_CAL_101102 #hcss.phs.timeEstimatorVersion=MC_H57_P57_S59_GYRO-100922 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H62ASTR_P58ASTR_S61ASTR_RP hcss.ccm.mission.config = MC_H62ASTR_P59ASTR_S61ASTR_RP #hcss.ccm.mission.config = MC_H61_P58_S60_CAL #hcss.ccm.mission.config = MC_H57_P57_S59_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H62ASTR_P58ASTR_S61ASTR_RP hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H62ASTR_P59ASTR_S61ASTR_RP #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H61_P58_S60_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.