PACS Cycle 38 routine calibration delivery 1. Delivery Note PACS Delivery note - 29th March 2011 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of the PACS RP calibration cycle#38 tar file onto the CVS server. 1. Delivery file & directory (a) OD tar file name : CYCLE038_PACS_FULL_1_20110329.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle038, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES 2. Mission Configurations (a) Does this delivery include a new Calibration mission configuration? YES (b) Does this delivery include a new ASTR mission configuration? NO 3. Operations Issues (TC,HPSDB,SIAM,Real Time Science) (a) Will any of these delivered observations generate a significant amount of telecommands? NO (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? NO (c) ICC to add anything specific which HSC & MOC should be aware of The delivery contains AORs of three SSOs, two asteroids 2 Pallas, 4 Vesta, one planet Neptune. 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.40.) * RPPhotFlux 3.2.1A&B, PACS RP Cal Plan, section 6.2 on gamma Dra monitor absolute flux calibration reproducibility of the photometer * RPPhotFlux 3.2.3A&B, PACS RP Cal Plan, section 6.3 on 4 Vesta calibration of flux non-linearity of photometer * RPPhotFlux 3.2.4B, PACS RP Cal Plan, section 6.3 on Neptune monitor the photometer linearity and absolute flux calibration for scan map point source mode * RPPhotFlux 6.3.1A, PACS RA Cal Plan, section 10.6 on 2 Pallas Herschel/Planck cross calibration * RPSpecWave 4.2.1A, PACS RP Cal Plan, section 6.6 on NGC 5643 spectrometer wavelength calibration * RPSpecFlux 4.3.3A, PACS RP Cal Plan, section 6.8 on Neptune monitor the spectrometer linearity and absolute flux calibration at key wavelengths * 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.10A, PACS RP Cal Plan, section 10.11 on Neptune spectrometer PSF and flatfield generation at key wavelengths * RPSpecFlux 6.1.1A&B, PACS RP Cal Plan, section 10.10 on 2 Pallas PACS PHOT/SPEC cross calibration, chopped and unchopped SED scan * 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): PACS Engineering ================ RPElecEDAC_811A_5476A_0_na_0010 This AOR must be scheduled immediately before the orbit epilogue of the first full contiguous PACS period of this cycle (probably OD 717). PACS Engineering ================ RPElecEDAC_811A_5476A_10_na_0009 This AOR must be scheduled immediately before the orbit epilogue of the last full contiguous PACS period of this cycle (probably OD 720 or DTCP 721). PACS PHOT (to be scheduled on any PACS PHOT OD) =============================================== RPPhotFlux_321A_cPS_repro_blu_gamDra_0027 RPPhotFlux_321B_sPS_070_repro_blu_gamDra_0027 RPPhotFlux_321B_sPS_110_repro_blu_gamDra_0027 RPPhotFlux_323A_cPS_159Jy_blu_c38_Vesta_03 RPPhotFlux_323B_sPS_070_159Jy_blu_c38_Vesta_03 RPPhotFlux_323B_sPS_110_159Jy_blu_c38_Vesta_03 RPPhotFlux_323A_cPS_90Jy_grn_c38_Vesta_03 RPPhotFlux_323B_sPS_070_90Jy_grn_c38_Vesta_03 RPPhotFlux_323B_sPS_110_90Jy_grn_c38_Vesta_03 The blocks shall be scheduled in the indicated sequence. PACS PHOT (to be scheduled on PACS PHOT/SPEC OD 716) ==================================================== RPPhotFlux_324A_cPS_200Jy_red_Neptune_0003 RPPhotFlux_324B_sPS_070_200Jy_red_Neptune_0003 RPPhotFlux_324B_sPS_110_200Jy_red_Neptune_0003 RPPhotFlux_324A_cPS_200Jy_grn_Neptune_0003 RPPhotFlux_324B_sPS_070_200Jy_grn_Neptune_0003 RPPhotFlux_324B_sPS_110_200Jy_grn_Neptune_0003 This block shall be scheduled in the indicated sequence. The observations on Neptune should be the last PACS PHOT observations on that OD, to be scheduled right before the PACS SPEC observations on the same target. The PACS PHOT observations should finish with a photometer orbit epilogue with the internal calibration sources kept on. PACS PHOT (to be scheduled on PACS PHOT/SPEC OD 720) ==================================================== RPPhotFlux_631A_sPS_070_Planck_blu_Pallas_0002 RPPhotFlux_631A_sPS_110_Planck_blu_Pallas_0002 RPPhotFlux_631A_sPS_070_Planck_grn_Pallas_0002 RPPhotFlux_631A_sPS_110_Planck_grn_Pallas_0002 This block shall be scheduled in the indicated sequence. The observations on Pallas should be the last PACS PHOT observations on that OD, to be scheduled right before the PACS SPEC observations on the same target. The PACS PHOT observations should finish with a photometer orbit epilogue with the internal calibration sources kept on. PACS SPEC (to be scheduled on any PACS SPEC OD) =============================================== RPSpecWave_421A_StdLS_NGC6543_A_0016 RPSpecWave_421A_StdLS_NGC6543_B_0016 This block shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on any PACS SPEC OD) =============================================== RPSpecFlux_4310A_nStd_25x25RCp_00_w55B2A_Neptune_01 RPSpecFlux_4310A_nStd_25x25RCp_00_w68B2A_Neptune_01 RPSpecFlux_4310A_nStd_25x25RCp_00_w68B3A_Neptune_01 RPSpecFlux_4310A_nStd_25x25RCp_00_w73B2B_Neptune_01 RPSpecFlux_4310A_nStd_25x25RCp_00_w84B2B_Neptune_01 RPSpecFlux_4310A_nStd_25x25RCp_00_w94B2B_Neptune_01 The order of this block does not need to be maintained. They can even be spread out across different ODs. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 716) ==================================================== RPSpecFlux_433A_StdRange_AbsFluxA_Neptune_0002 RPSpecFlux_433A_StdRange_AbsFluxB_Neptune_0002 RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0039 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0039 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0039 These blocks shall be scheduled in the indicated sequence. The observations done on Neptune should be the first PACS SPEC observations on that OD, to be scheduled right after the PACS PHOT observations on the same target. The PACS SPEC observations should begin with a spectrometer orbit prologue with the internal calibration sources kept on. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 720) ==================================================== RPSpecFlux_611A_StdSED_sedb2a_Pallas_0003 RPSpecFlux_611A_StdSED_sedb2b_Pallas_0003 RPSpecFlux_611A_StdSED_sedb3a_Pallas_0003 This block shall be scheduled in the indicated sequence. The observations done on Pallas should be the first PACS SPEC observations on that OD, to be scheduled right after the PACS PHOT observations on the same target. The PACS SPEC observations should begin with a spectrometer orbit prologue with the internal calibration sources kept on. Please acknowledge the receipt of the e-mail and the delivery. Best regards, Markus. Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE038_PACS_FULL_1_20110329.tar New MC - P63CAL 2. Software used for import + Source the Environment (if not already done!!) [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Mar 29 15:18:27 2011 from herl21.net4.lan HCSS Version: 6.0.2 PHS Version: 5.3.0 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 3. What is the Mission Configuration Name going to be?? MC_H67_P63_S62_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/HIFI> mkdir PACS_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle038_PACS_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL> 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_H67_P63_S62_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_H67_P63_S62_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H67_P60_S62_CAL/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> ls CYCLE035_SPIRE_FULL_1_0_20110214.tar SPIRE_Duration.txt SPIRE_AOR_C035_62_CAL.aor SPIRE_harness_duration_summary_20110215_10h07m26s.log SPIRE_AOR_C035_62_ENG.aor SPIRE_MC_pv88_C035_62_CUS_CAL.xml SPIRE_cus_scripts.txt SPIRE_MC_pv88_C035_62_CUS.def SPIRE_CUS_THCP.py SPIRE_Readme_C035_62.txt HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H67_P60_S62_CAL/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> ls CYCLE034_HIFI_FULL_1_20110202.tar HIFI_DUR_C034_67.txt HIFI_Readme_C034_67.txt duration_cal.sh* HIFI_MC_R076_FULL_67_0_CUS_CAL.xml Summary_durations.txt HIFI_AOR_C034_67.aor HIFI_MC_R076_FULL_67_0_CUS.def summary_HIFI_AOR_C034_67.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> rm summary_HIFI_AOR_C034_67.log rm: remove regular file `summary_HIFI_AOR_C034_67.log'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> ls CYCLE034_HIFI_FULL_1_20110202.tar HIFI_AOR_C034_67.aor HIFI_MC_R076_FULL_67_0_CUS_CAL.xml HIFI_Readme_C034_67.txt duration_cal.sh* HIFI_DUR_C034_67.txt HIFI_MC_R076_FULL_67_0_CUS.def Summary_durations.txt 6(a) Download & Untar the PACS delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> cvs login Logging in to :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS CVS password: hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle038/CYCLE038_PACS_FULL_1_20110329.tar U develop/data/observingmodes/rp_cycles/cycle038/CYCLE038_PACS_FULL_1_20110329.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle038/CYCLE038_PACS_FULL_1_20110329.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> ls CYCLE038_PACS_FULL_1_20110329.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> tar -xvf CYCLE038_PACS_FULL_1_20110329.tar PACS_MC_OT1_2011-03-15A_C038_63_CUS.def PACS_MC_OT1_2011-03-15A_C038_63_CUS_CAL.xml PACS_AOR_C038_63.aor PACS_Duration_PACS_compare.txt PACS_Readme_C038_63.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt CYCLE038_PACS_FULL_1_20110329.tar PACS_MC_OT1_2011-03-15A_C038_63_CUS_CAL.xml develop/ PACS_MC_OT1_2011-03-15A_C038_63_CUS.def PACS_AOR_C038_63.aor PACS_Readme_C038_63.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle38/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C038_63.txt CYCLE038_PACS_FULL_1_20110329.tar PACS_MC_OT1_2011-03-15A_C038_63_CUS_CAL.xml PACS_AOR_C038_63.aor PACS_MC_OT1_2011-03-15A_C038_63_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_H67_P63_S62_CAL/PACS> Mar 29, 2011 5:03:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:03:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:03:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:03:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:03:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:03:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:03:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:03:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:03:52 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Mar 29, 2011 5:04:07 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_H67_P63_S62_CAL/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Mar 29, 2011 5:04:32 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:04:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:04:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:04:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:04:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:04:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:04:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:04:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:04:42 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Mar 29, 2011 5:05:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:05:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:05:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:05:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:05:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:05:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:05:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:05:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:05:22 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 63.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS> cus -m "upload PACS MC P63CAL mission config" -import PACS_MC_OT1_2011-03-15A_C038_63_CUS.def -importcaltables PACS_MC_OT1_2011-03-15A_C038_63_CUS_CAL.xml Mar 29, 2011 5:06:59 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:07:00 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:07:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:07:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:07:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:07:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:07:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:07:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:07:25 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Mar 29, 2011 5:07:25 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Mar 29, 2011 5:07:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:07:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:07:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:07:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:07:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:07:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:07:26 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 29, 2011 5:07:31 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_OT1_2011-03-15A_C038_63_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_OT1_2011-03-15A_C038_63_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 6.0.2 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C038_63.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS> ls -ls total 11420 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Mar 29 17:10 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Mar 29 17:10 2createOBSMODtable4RP.sh~* 5692 -rw-r--r-- 1 hscphs2 herschel 5816320 Mar 29 15:41 CYCLE038_PACS_FULL_1_20110329.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Mar 29 17:12 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 77 Mar 29 17:13 msgPacsCal_Spec_Chopped_Raster.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Mar 29 17:11 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 62 Mar 29 17:13 msgPacsLineSpec.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Mar 29 17:12 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Mar 29 17:12 msgPacsRangeSpec.txt 144 -rw-r--r-- 1 hscphs2 herschel 139521 Mar 29 15:17 PACS_AOR_C038_63.aor 4 -rw-r--r-- 1 hscphs2 herschel 2394 Mar 29 15:21 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2394 Mar 29 17:13 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404163 Mar 28 17:49 PACS_MC_OT1_2011-03-15A_C038_63_CUS_CAL.xml 5136 -rw-r--r-- 1 hscphs2 herschel 5245502 Mar 28 17:49 PACS_MC_OT1_2011-03-15A_C038_63_CUS.def 12 -rw-r--r-- 1 hscphs2 herschel 8801 Mar 29 15:36 PACS_Readme_C038_63.txt 4 -rw-r--r-- 1 hscphs2 herschel 1437 Mar 29 17:11 tmp 4 -rw-r--r-- 1 hscphs2 herschel 585 Mar 29 17:11 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/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 P63CAL 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_H67_P63_S62_CAL/PACS> missetup -addconfig MC_H67_P63_S62_CAL Mar 29, 2011 5:25:19 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:25:20 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:25:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:25:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:25:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:25:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:25:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:25:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:25:21 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Mar 29, 2011 5:25:24 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H67_P63_S62_CAL" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Add the commited CUS to the new MC hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/PACS> Mar 29, 2011 5:29:53 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:29:54 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:29:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:29:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:29:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:29:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:29:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:29:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:29:55 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Mar 29, 2011 5:31:22 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P63_S62_CAL" Mar 29, 2011 5:31:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:31:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:31:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:31:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:31:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:31:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:31:39 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 29, 2011 5:31:53 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H67_P63_S62_CAL Mar 29, 2011 5:32:02 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(a) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> kedit Uplink_Coord_1_2.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_H67_P63_S62_CAL/HIFI> Mar 29, 2011 5:34:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:34:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:34:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:34:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:34:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:34:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:34:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:34:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:34:09 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Mar 29, 2011 5:34:31 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Mar 29, 2011 5:35:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:35:07 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:35:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:35:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:35:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:35:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:35:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:35:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:35:16 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Mar 29, 2011 5:35:39 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:35:39 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:35:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:35:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:35:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:35:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:35:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:35:40 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:35:45 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 7(d) Import the new Instrument CUS & Cal tables into the DB Import old Mission Configuration (H67Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> cus -m "upload HIFI MC67Cal mission config" -import HIFI_MC_R076_FULL_67_0_CUS.def -importcaltables HIFI_MC_R076_FULL_67_0_CUS_CAL.xml Mar 29, 2011 5:37:21 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:37:22 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:37:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:37:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:37:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:37:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:37:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:37:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:37:44 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Mar 29, 2011 5:37:44 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Mar 29, 2011 5:37:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:37:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:37:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:37:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:37:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:37:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:37:45 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 29, 2011 5:37:52 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R076_FULL_67_0_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by HIFI: HIFI_MC_R074_FULL_65_0_CUS_CAL.xml CONFIRMED!! 7(e) Run the duration script for the HIFI instrument Run the duration script delivered hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C034_67 next AOR file = HIFI_AOR_C034_67 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiSScanModeDBS -- mode HifiSScanModeFastDBS -- mode HifiSScanModeFSwitch -- mode HifiSScanModeFSwitchNoRef -- mode HifiSScanModeLoadChop -- mode HifiSScanModeLoadChopNoRef Total duration of HifiEng_Chopper_FT2_COP with default parameters = 114 Total duration of HifiEng_Chopper_Response_time_COP with default parameters = 44 Total duration of HifiSScanModeDBS with default parameters = 386 Total duration of HifiSScanModeFastDBS with default parameters = 338 Total duration of HifiSScanModeFSwitch with default parameters = 500 Total duration of HifiSScanModeFSwitchNoRef with default parameters = 417 Total duration of HifiSScanModeLoadChop with default parameters = 350 Total duration of HifiSScanModeLoadChopNoRef with default parameters = 285 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> ls -ls total 11400 5692 -rw-r--r-- 1 hscphs2 herschel 5816320 Feb 2 10:36 CYCLE034_HIFI_FULL_1_20110202.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Feb 2 10:25 duration_cal.sh* 40 -rw-r--r-- 1 hscphs2 herschel 34893 Feb 1 17:38 HIFI_AOR_C034_67.aor 4 -rw-r--r-- 1 hscphs2 herschel 584 Feb 2 10:29 HIFI_DUR_C034_67.txt 2300 -rw-r--r-- 1 hscphs2 herschel 2344567 Feb 2 10:31 HIFI_MC_R076_FULL_67_0_CUS_CAL.xml 3352 -rw-r--r-- 1 hscphs2 herschel 3423201 Feb 2 10:31 HIFI_MC_R076_FULL_67_0_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 2672 Feb 2 10:34 HIFI_Readme_C034_67.txt 0 -rw-r--r-- 1 hscphs2 herschel 0 Feb 15 09:50 Summary_durations.txt 4 -rw-r--r-- 1 hscphs2 herschel 584 Mar 29 17:39 summary_HIFI_AOR_C034_67.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/HIFI> diff HIFI_DUR_C034_67.txt summary_HIFI_AOR_C034_67.log No differences. 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY In the Comment field, refer to HIFI MC H67CAL 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_H67_P63_S62_CAL/HIFI> Mar 29, 2011 5:42:32 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:42:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:42:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:42:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Mar 29, 2011 5:42:55 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P63_S62_CAL" Mar 29, 2011 5:43:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:43:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:43:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:43:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:43:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:43:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:43:11 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 29, 2011 5:43:25 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H67_P63_S62_CAL Mar 29, 2011 5:52:44 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P63_S62_CAL" Mar 29, 2011 5:52:46 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the Old SPIRE Instrument model into the MC Set Instrument Model = SPIRE Check with CUSGUI Run the duration script for the PACS instrument Import into the new Mission Configuration 8(a) Set Instrument Model = SPIRE #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> Mar 29, 2011 5:55:11 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:55:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:55:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:55:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:55:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:55:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:55:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:55:13 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:55:13 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Mar 29, 2011 5:55:20 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Mar 29, 2011 5:55:50 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:55:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:55:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:55:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:55:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:55:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:55:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:55:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:55:59 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Mar 29, 2011 5:56:22 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:56:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:56:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:56:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:56:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:56:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:56:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:56:23 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:56:27 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted TAKE NOTE : OPEN UP CUSGUI & VERIFY IT IS EMPTY i.e. No Cus scripts & No Parameter tables - VERIFIED!!! TAKE NOTE : Check HPSDB in the CUSGUI Session = hpsdb_MOC9_201003161700 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import old SPIRE Mission Configuration (Version 62.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> cus -m "upload SPIRE MC_62CAL mission config" -import SPIRE_MC_pv88_C035_62_CUS.def -importcaltables SPIRE_MC_pv88_C035_62_CUS_CAL.xml Mar 29, 2011 5:57:48 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 5:57:49 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 5:57:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:57:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:57:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:57:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:57:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:57:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:58:05 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Mar 29, 2011 5:58:05 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Mar 29, 2011 5:58:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:58:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 5:58:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:58:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 5:58:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:58:05 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 5:58:05 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 29, 2011 5:58:10 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_pv88_C035_62_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_pv88_C035_62_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> ls -ls total 4908 2440 -rw-r--r-- 1 hscphs2 herschel 2488320 Feb 14 17:40 CYCLE035_SPIRE_FULL_1_0_20110214.tar 44 -rw-r--r-- 1 hscphs2 herschel 38179 Feb 14 17:28 SPIRE_AOR_C035_62_CAL.aor 8 -rw-r--r-- 1 hscphs2 herschel 6401 Feb 14 17:29 SPIRE_AOR_C035_62_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 2023 Mar 29 17:58 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Feb 14 17:35 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5451 Feb 14 17:35 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Feb 15 10:07 SPIRE_harness_duration_summary_20110215_10h07m26s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5451 Mar 29 18:03 SPIRE_harness_duration_summary_20110329_18h03m53s.log 276 -rw-r--r-- 1 hscphs2 herschel 278093 Feb 14 17:35 SPIRE_MC_pv88_C035_62_CUS_CAL.xml 2100 -rw-r--r-- 1 hscphs2 herschel 2140684 Feb 14 17:35 SPIRE_MC_pv88_C035_62_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5618 Feb 14 17:37 SPIRE_Readme_C035_62.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P63_S62_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110329_18h03m53s.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 S62CAL. 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_H67_P63_S62_CAL/SPIRE> Mar 29, 2011 6:06:44 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 6:06:45 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 6:06:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 6:06:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 6:06:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 6:06:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 6:06:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 6:06:45 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 6:06:45 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Mar 29, 2011 6:07:09 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P63_S62_CAL" Mar 29, 2011 6:07:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 6:07:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 6:07:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 6:07:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 6:07:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 6:07:22 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 6:07:22 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Mar 29, 2011 6:07:55 PM herschel.cus.gui.CusEditor messageDialog FINE: Instrument model created in MC_H67_P63_S62_CAL Mar 29, 2011 6:08:02 PM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. 9.Link PropHandler to the new MC & Start PropHandler to confirm Linked Prophandler to the new Mission Config by updating the Uplink_Coord.props file in .hcss directory #Mission Configuration hcss.ccm.mission.config = MC_H67_P63_S62_CAL [mkidger@herl38 ~]$ ssh -X hscphs2@heropl02 hscphs2@heropl02's password: Last login: Tue Mar 29 16:41:19 2011 from herl23.net4.lan HCSS Version: 6.0.2 PHS Version: 5.3.0 hscphs2@heropl02/home/hscphs2> propHandler & [1] 5185 [1] + Running propHandler hscphs2@heropl02/home/hscphs2> Mar 29, 2011 6:10:18 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties Mar 29, 2011 6:10:19 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 29, 2011 6:10:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 6:10:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 29, 2011 6:10:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 6:10:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 29, 2011 6:10:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Mar 29, 2011 6:10:19 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Running CDH.getObsProgrammes() Mar 29, 2011 6:10:20 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Mar 29, 2011 6:10:20 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 29 Mar 29, 2011 6:10:20 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Mar 29, 2011 6:10:20 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P63_S62_CAL" Mar 29, 2011 6:10:24 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 4407 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: Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H67_P63_S62_CAL Example of the last entry in the log: Mar 29, 2011 6:13:18 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H67_P63_S62_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Mar 29, 2011 6:13:18 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H67_P63_S62_CAL/HifiManCmdSetIntoDissipativeGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P63_S62_CAL> ls *.prop > & MC_H67_P63_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P63_S62_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18135 Mar 29 18:14 MC_H67_P63_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P63_S62_CAL> cp MC_H67_P63_S62_CAL.txt /home/hscphs2/icchsc/HSpot_files/ Now do a diff between this new txt file and the one generated with the last Mission configuration. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_H67_P62_S62_CAL.txt MC_H67_P63_S62_CAL.txt If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. One new PACS scripts. Do not notify Eva & Jose 12. Final Jboss Activities Log into Jboss #2 herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 661 PHS: Astronomers instance 659 PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss Stop the Test Jboss : herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations set old=/home/hsc_phs chdir /herschel/software/phs/jboss/jboss/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1699 /herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar java 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> cd /herschel/data/files/phs/mcs herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H67_P63_S62_CAL copied HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P63_S62_CAL> scp *.prop hsc_phs@herjbo02.esac.esa.int:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H67_P63_S62_CAL/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit phs-operations.props & [1] 27391 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_H72ASTR_P60ASTR_S61ASTR_AO_110304 #hcss.phs.timeEstimatorVersion=MC_H71_P62_S62_CAL-110315-BAD hcss.phs.timeEstimatorVersion=MC_H67_P63_S62_CAL-1100329 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H72ASTR_P60ASTR_S61ASTR_AO #hcss.ccm.mission.config = MC_H71_P62_S62_CAL hcss.ccm.mission.config = MC_H67_P63_S62_CAL #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H72ASTR_P60ASTR_S61ASTR_AO #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H71_P62_S62_CAL hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H67_P63_S62_CAL Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 13967 herjbo02.esac.esa.int/home/hsc_phs/.hcss> ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /herschel/software/phs/jboss/jboss JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar ========================================================================= 18:27:25,394 INFO [Server] Starting JBoss (MX MicroKernel)... 18:27:25,395 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 18:27:25,395 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 18:27:25,396 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 18:27:25,396 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 18:27:25,396 INFO [Server] Patch URL: null 18:27:25,396 INFO [Server] Server Name: phs-operations 18:27:25,396 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 18:27:25,399 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 18:27:25,399 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 18:27:25,399 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 18:27:25,400 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 18:27:25,400 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 18:27:25,400 INFO [Server] Root Deployment Filename: jboss-service.xml 18:27:25,401 INFO [Server] Starting General Purpose Architecture (GPA)... 18:27:25,620 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 18:27:25,621 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 18:27:25,621 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 18:27:26,147 INFO [Server] Core system initialized 18:27:27,720 INFO [ServiceBindingManager] Initializing store 18:27:27,720 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 18:27:27,991 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.