PACS Cycle 35 routine calibration delivery 1. Delivery Note PACS Delivery note - 17th February 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#35 tar file onto the CVS server. 1. Delivery file & directory (a) OD tar file name : CYCLE035_PACS_FULL_1_20110217.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle035, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 62 delivered with CYCLE035_PACS_FULL_1_20110217.tar shall be used. 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 on the SSOs asteroid 4 Vesta. 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.25.) * 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.4A&B, PACS RP Cal Plan, section 6.3 on gamma Dra monitor the photometer linearity and absolute flux calibration for chop/nod and scan map point source mode * RPPhotSpatial 3.1.4C, PACS RP Cal Plan, section 10.2 on 4 Vesta PACS Photometer PSF characterisation * RPSpecFlux 4.3.3A, PACS RP Cal Plan, section 6.8 on 4 Vesta 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 * RPSpecAOTVal 5.2.5B&C, PACS RP Cal Plan, section 10.12 on NGC 6946 verification of unchopped line spectroscopy bright mode * RPSpecAOTVal 5.2.5D, PACS RP Cal Plan, section 10.12 on NGC 6543 verification of unchopped line spectroscopy bright mode * 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 Engineering (to be scheduled on PACS OD 665) ================================================= RPElecEDAC_811A_5476A_0_na_0007 This AOR must be scheduled immediately before the final orbit epilogue of this OD. PACS Engineering (to be scheduled on PACS OD 678) ================================================= RPElecEDAC_811A_5476A_10_na_0006 This AOR must be scheduled immediately before the final orbit epilogue of this OD. PACS PHOT (to be scheduled on PACS PHOT/SPEC OD 677) ==================================================== RPPhotFlux_323A_cPS_106Jy_blu_c35_Vesta_03 RPPhotFlux_323B_sPS_070_106Jy_blu_c35_Vesta_03 RPPhotFlux_323B_sPS_110_106Jy_blu_c35_Vesta_03 RPPhotSpatial_314C_StdScan045_med_blu_Vesta_0001 RPPhotSpatial_314C_StdScan135_med_blu_Vesta_0001 RPPhotSpatial_314C_StdScan045_med_grn_Vesta_0001 RPPhotSpatial_314C_StdScan135_med_grn_Vesta_0001 These blocks shall be scheduled in the indicated sequence. They 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 any PACS PHOT OD) =============================================== RPPhotFlux_324A_cPS_2Jy_grn_gamDra_0003 RPPhotFlux_324B_sPS_070_2Jy_grn_gamDra_0003 RPPhotFlux_324B_sPS_110_2Jy_grn_gamDra_0003 These blocks shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS SPEC OD 665) =============================================== RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0034 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0034 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0034 RPSpecAOTVal_525D_nStdLSnCBrigh_A_2x2_NGC6543_1 RPSpecAOTVal_525D_nStdLSnCBrigh_B_2x2_NGC6543_1 RPSpecAOTVal_525B_nStdLSnCFaint_OICII_2x2_NGC6946_1 RPSpecAOTVal_525C_nStdLSnCBrigh_OICII_2x2_NGC6946_1 RPSpecAOTVal_525B_nStdLSnCFaint_OICII_2x2_NGC6946_2 RPSpecAOTVal_525C_nStdLSnCBrigh_OICII_2x2_NGC6946_2 The blocks shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on PACS PHOT/SPEC OD 677) ==================================================== RPSpecFlux_433A_StdRange_AbsFluxA_Vesta_0002 RPSpecFlux_433A_StdRange_AbsFluxB_Vesta_0002 RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0035 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0035 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0035 These blocks shall be scheduled in the indicated sequence. The observations done on Vesta 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) CYCLE035_PACS_FULL_1_20110217.tar New MC - P62CAL 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 5.1.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_v5.1.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_H67_P62_S62_CAL 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/HIFI> mkdir PACS_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle035_PACS_FULL_1.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_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_P62_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_P62_S62_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H67_P60_S62_CAL/SPIRE/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_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_P62_S62_CAL/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H67_P60_S62_CAL/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_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_P62_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_P62_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 6(a) Download & Untar the PACS delivery from the CVS into the delivery directory hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/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_Cycle35/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle035/CYCLE035_PACS_FULL_1_20110217.tar U develop/data/observingmodes/rp_cycles/cycle035/CYCLE035_PACS_FULL_1_20110217.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle035/CYCLE035_PACS_FULL_1_20110217.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/PACS/PACS_FULL_1> ls CYCLE035_PACS_FULL_1_20110217.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/PACS/PACS_FULL_1> tar -xvf CYCLE035_PACS_FULL_1_20110217.tar PACS_MC_OT1_2011-02-17A_C035_62_CUS.def PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml PACS_AOR_C035_62.aor PACS_Duration_PACS_compare.txt PACS_Readme_C035_62.txt 2createOBSMODtable4RP.sh hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/PACS/PACS_FULL_1> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt CYCLE035_PACS_FULL_1_20110217.tar PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml develop/ PACS_MC_OT1_2011-02-17A_C035_62_CUS.def PACS_AOR_C035_62.aor PACS_Readme_C035_62.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle35/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C035_62.txt CYCLE035_PACS_FULL_1_20110217.tar PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml PACS_AOR_C035_62.aor PACS_MC_OT1_2011-02-17A_C035_62_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_P62_S62_CAL/PACS> Feb 17, 2011 6:48:45 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 6:48:45 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 6:48:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:48:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:48:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:48:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:48:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:48:46 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:48:46 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 17, 2011 6:48:54 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_P62_S62_CAL/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Feb 17, 2011 6:49:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 6:49:15 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 6:49:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:49:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:49:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:49:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:49:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:49:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:49:22 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Feb 17, 2011 6:49:47 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 6:49:48 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 6:49:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:49:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:49:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:49:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:49:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:49:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:49:52 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 62.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS> cus -m "upload PACS MC P62CAL mission config" -import PACS_MC_OT1_2011-02-17A_C035_62_CUS.def -importcaltables PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml Feb 17, 2011 6:54:06 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 6:54:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 6:54:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:54:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:54:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:54:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:54:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:54:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:54:30 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Feb 17, 2011 6:54:30 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Feb 17, 2011 6:54:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:54:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:54:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:54:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:54:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:54:31 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 17, 2011 6:54:51 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_OT1_2011-02-17A_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 PACS: PACS_MC_OT1_2011-02-17A_C035_62_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 5.1.0 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C035_62.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/PACS> ls -ls total 11436 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Feb 17 18:55 2createOBSMODtable4RP.sh* 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Feb 17 18:55 2createOBSMODtable4RP.sh~* 5704 -rw-r--r-- 1 hscphs2 herschel 5826560 Feb 17 18:27 CYCLE035_PACS_FULL_1_20110217.tar 4 -rw-r--r-- 1 hscphs2 herschel 79 Feb 17 18:57 msgPacsCal_PacsLineSpec_unChopBL.txt 4 -rw-r--r-- 1 hscphs2 herschel 74 Feb 17 18:57 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 75 Feb 17 18:56 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Feb 17 18:56 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Feb 17 18:57 msgPacsRangeSpec.txt 152 -rw-r--r-- 1 hscphs2 herschel 151189 Feb 17 18:07 PACS_AOR_C035_62.aor 4 -rw-r--r-- 1 hscphs2 herschel 1784 Feb 17 18:12 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 1784 Feb 17 18:57 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404163 Feb 17 12:01 PACS_MC_OT1_2011-02-17A_C035_62_CUS_CAL.xml 5136 -rw-r--r-- 1 hscphs2 herschel 5245450 Feb 17 12:01 PACS_MC_OT1_2011-02-17A_C035_62_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 6819 Feb 17 18:24 PACS_Readme_C035_62.txt 4 -rw-r--r-- 1 hscphs2 herschel 1282 Feb 17 18:56 tmp 4 -rw-r--r-- 1 hscphs2 herschel 514 Feb 17 18:56 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_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 P62CAL 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_P62_S62_CAL/PACS> missetup -addconfig MC_H67_P62_S62_CAL Feb 17, 2011 6:59:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 6:59:24 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 6:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 6:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 6:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:59:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 6:59:24 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Feb 17, 2011 6:59:33 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H67_P62_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_P62_S62_CAL/PACS> Feb 17, 2011 6:59:59 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 6:59:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 7:00:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:00:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:00:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:00:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:00:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:00:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:00:00 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Feb 17, 2011 7:00:13 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P62_S62_CAL" Feb 17, 2011 7:00:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:00:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:00:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:00:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:00:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:00:25 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:00:25 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 17, 2011 7:01:04 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the new HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(a) 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_H67_P62_S62_CAL/HIFI> Feb 17, 2011 7:02:28 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 7:02:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 7:02:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:02:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:02:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:02:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:02:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:02:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:02:29 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Feb 17, 2011 7:02:53 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!! Skip this. We already have the correct CUS... 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Jan 25, 2011 3:04:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jan 25, 2011 3:04:00 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 25, 2011 3:04:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:04:00 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:04:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:04:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:04:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:04:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:04:06 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Jan 25, 2011 3:04:26 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jan 25, 2011 3:04:27 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 25, 2011 3:04:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:04:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:04:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:04:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:04:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:04:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:04:31 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 (H65Cal). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/HIFI> cus -m "upload HIFI MC65Cal mission config" -import HIFI_MC_R074_FULL_65_0_CUS.def -importcaltables HIFI_MC_R074_FULL_65_0_CUS_CAL.xml Jan 25, 2011 3:07:14 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jan 25, 2011 3:07:15 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 25, 2011 3:07:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:07:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:07:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:07:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:07:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:07:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:07:33 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 25, 2011 3:07:33 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 25, 2011 3:07:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:07:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:07:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:07:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:07:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:07:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:07:34 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 25, 2011 3:07:42 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_R074_FULL_65_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_P62_S62_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C033_65 next AOR file = HIFI_AOR_C033_65 -- mode HifiEng_Chopper_FT2_COP -- mode HifiEng_Chopper_Response_time_COP -- mode HifiEng_WBS_FT_COP -- mode HifiPointProcDBS_FCal -- mode HifiPointProcDBS -- mode HifiPointProcLoadChopNoRef_FCal -- mode HifiPointProcLoadChopNoRef -- mode HifiPointModeDBS -- mode HifiPointModeFastDBS -- mode HifiPointModeFSwitch -- mode HifiPointModeFSwitchNoRef -- mode HifiPointModeLoadChop -- mode HifiPointModeLoadChopNoRef -- mode HifiPointModePositionSwitch -- 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 HifiEng_WBS_FT_COP with default parameters = 1388 Total duration of HifiPointProcDBS_FCal with default parameters = 160 Total duration of HifiPointProcDBS with default parameters = 158 Total duration of HifiPointProcLoadChopNoRef_FCal with default parameters = 126 Total duration of HifiPointProcLoadChopNoRef with default parameters = 124 Total duration of HifiPointModeDBS with default parameters = 158 Total duration of HifiPointModeFastDBS with default parameters = 146 Total duration of HifiPointModeFSwitch with default parameters = 181 Total duration of HifiPointModeFSwitchNoRef with default parameters = 157 Total duration of HifiPointModeLoadChop with default parameters = 148 Total duration of HifiPointModeLoadChopNoRef with default parameters = 124 Total duration of HifiPointModePositionSwitch with default parameters = 140 Total duration of HifiSScanModeDBS with default parameters = 387 Total duration of HifiSScanModeFastDBS with default parameters = 339 Total duration of HifiSScanModeFSwitch with default parameters = 501 Total duration of HifiSScanModeFSwitchNoRef with default parameters = 418 Total duration of HifiSScanModeLoadChop with default parameters = 351 Total duration of HifiSScanModeLoadChopNoRef with default parameters = 286 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/HIFI> ls -ls total 11180 5584 -rw-r--r-- 1 hscphs2 herschel 5703680 Jan 21 09:29 CYCLE033_HIFI_FULL_1_20110120.tar 4 -rwxr-xr-x 1 hscphs2 herschel 2697 Jan 20 20:59 duration_cal.sh* 56 -rw-r--r-- 1 hscphs2 herschel 52922 Jan 21 08:55 HIFI_AOR_C033_65.aor 4 -rw-r--r-- 1 hscphs2 herschel 1452 Jan 20 20:59 HIFI_DUR_C033_65.txt 2172 -rw-r--r-- 1 hscphs2 herschel 2214705 Jan 20 19:00 HIFI_MC_R074_FULL_65_0_CUS_CAL.xml 3352 -rw-r--r-- 1 hscphs2 herschel 3422110 Jan 20 19:00 HIFI_MC_R074_FULL_65_0_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 4075 Jan 21 09:24 HIFI_Readme_C033_65.txt 4 -rw-r--r-- 1 hscphs2 herschel 1452 Jan 21 10:30 summary_HIFI_AOR_C033_65.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/HIFI> diff HIFI_DUR_C033_65.txt summary_HIFI_AOR_C033_65.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 H65CAL TAKE NOTE : It is very important that you commit the delivery as defined above. Re-join here... 7(g) Import HIFI into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/HIFI> Feb 17, 2011 7:04:33 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 7:04:34 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 7:04:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:04:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:04:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:04:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:04:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:04:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:04:35 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Feb 17, 2011 7:04:48 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P62_S62_CAL" Feb 17, 2011 7:05:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:05:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:05:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:05:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:05:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:05:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:05:01 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Feb 17, 2011 7:05: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_P62_S62_CAL/SPIRE> Feb 17, 2011 7:06:33 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 17, 2011 7:06:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 17, 2011 7:06:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:06:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 17, 2011 7:06:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:06:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 17, 2011 7:06:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:06:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 17, 2011 7:06:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Feb 17, 2011 7:06:47 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! Skip this. We already have the correct CUS... 8(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Jan 25, 2011 3:27:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jan 25, 2011 3:27:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 25, 2011 3:27:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:27:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:27:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:27:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:27:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:27:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:27:09 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jan 25, 2011 3:27:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jan 25, 2011 3:27:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 25, 2011 3:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:27:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:27:33 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 61.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/SPIRE> cus -m "upload SPIRE MC_61ASTR mission config as CAL" -import SPIRE_MC_ASTR_pv87_C028_61_CUS.def -importcaltables SPIRE_MC_ASTR_pv87_C028_61_CUS_CAL.xml Jan 25, 2011 3:30:29 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jan 25, 2011 3:30:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 25, 2011 3:30:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:30:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:30:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:30:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:30:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:30:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:30:43 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jan 25, 2011 3:30:43 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jan 25, 2011 3:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:30:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:30:43 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 25, 2011 3:30:46 PM 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_H67_P62_S62_CAL/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/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 Jan 25 15:32 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 Jan 25 15:36 SPIRE_harness_duration_summary_20110125_15h36m35s.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_H67_P62_S62_CAL/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20110125_15h36m35s.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 as CAL. TAKE NOTE : It is very important that you commit the delivery as defined above. Re-join here... 8(g) Import SPIRE model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H67_P62_S62_CAL/SPIRE> Jan 25, 2011 3:40:05 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jan 25, 2011 3:40:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jan 25, 2011 3:40:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:40:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:40:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:40:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:40:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:40:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:40:06 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jan 25, 2011 3:40:23 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P62_S62_CAL" Jan 25, 2011 3:40:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:40:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jan 25, 2011 3:40:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:40:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jan 25, 2011 3:40:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:40:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Jan 25, 2011 3:40:34 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId INFO: Creating new IdRegistry entry idreg_productIdRegistry Jan 25, 2011 3:40:50 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_P62_S62_CAL 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> propHandler & [1] 4161 [1] + Running propHandler hscphs2@heropl02/home/hscphs2/otherSetups> Feb 18, 2011 8:38:13 AM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Feb 18, 2011 8:38:14 AM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Feb 18, 2011 8:38:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 18, 2011 8:38:15 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Feb 18, 2011 8:38:16 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 18, 2011 8:38:16 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Feb 18, 2011 8:38:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Feb 18, 2011 8:38:17 AM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int Running CDH.getObsProgrammes() Feb 18, 2011 8:38:17 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Feb 18, 2011 8:38:17 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 30 Feb 18, 2011 8:38:17 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Feb 18, 2011 8:38:17 AM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H67_P62_S62_CAL" Feb 18, 2011 8:40:02 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 104634 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_P62_S62_CAL Example of the last entry in the log: Feb 18, 2011 8:47:14 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H67_P62_S62_CAL/HifiEng_Fast_LCU_HK_COPGen.prop Feb 18, 2011 8:47:14 AM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H67_P62_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_P62_S62_CAL> ls *.prop > & MC_H67_P62_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P62_S62_CAL> ls -ls *.txt 20 -rw-r--r-- 1 hscphs2 herschel 18135 Feb 18 08:48 MC_H67_P62_S62_CAL.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H67_P62_S62_CAL> cp MC_H67_P62_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_P60_S62_CAL.txt MC_H67_P62_S62_CAL.txt 181a182 > PacsCal_PacsLineSpec_unChopBLGen.prop 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. Notify Eva & Jose 12. Final Jboss Activities Log into Jboss #2 herjbo02.esac.esa.int/home/hsc_phs> source .minimal PHS: Operationss instance 650 PHS: Astronomers instance 650 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_P62_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_P62_S62_CAL> scp *.prop hsc_phs@herjbo02.esac.esa.int:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H67_P62_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_H66ASTR_P60ASTR_S61ASTR_RP_110121 hcss.phs.timeEstimatorVersion=MC_H67_P62_S62_CAL-1100218 #hcss.phs.timeEstimatorVersion=MC_H65_P61_S61_GYROTEST-110125 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H66ASTR_P60ASTR_S61ASTR_RP hcss.ccm.mission.config = MC_H67_P62_S62_CAL #hcss.ccm.mission.config = MC_H65_P61_S61_GYRO #MARK DIRECTORIES #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H66ASTR_P60ASTR_S61ASTR_RP hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H67_P62_S62_CAL #hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H65_P61_S61_GYRO Finally Restart the Test Jboss. herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations Starting instance phs-operations [1] 27451 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 ========================================================================= 09:13:17,124 INFO [Server] Starting JBoss (MX MicroKernel)... 09:13:17,125 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106) 09:13:17,125 INFO [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6 09:13:17,126 INFO [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/ 09:13:17,126 INFO [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/ 09:13:17,126 INFO [Server] Patch URL: null 09:13:17,126 INFO [Server] Server Name: phs-operations 09:13:17,126 INFO [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations 09:13:17,129 INFO [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/ 09:13:17,129 INFO [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data 09:13:17,129 INFO [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp 09:13:17,129 INFO [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/ 09:13:17,130 INFO [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/ 09:13:17,130 INFO [Server] Root Deployment Filename: jboss-service.xml 09:13:17,131 INFO [Server] Starting General Purpose Architecture (GPA)... 09:13:17,310 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 09:13:17,310 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 09:13:17,310 INFO [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386 09:13:17,695 INFO [Server] Core system initialized 09:13:19,089 INFO [ServiceBindingManager] Initializing store 09:13:19,090 INFO [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml 09:13:19,348 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.