PACS Cycle 19 Calibration delivery 1. Delivery Note PACS Delivery note - 6th July 2010 Dear HSC Colleagues, This e-mail is to notify you that PACS ICC has just uploaded the delivery of the PACS RP cycle#19 tar file onto the CVS server, including a new ASTR MC. Due to summer holidays of PACS CUS key personnel, we provide the ASTR MC updates, related to the pre-released unchopped spectroscopy modes, with this delivery to have it available right in time for the implementation into the official community HSpot software, whenever HSC plans this after the lift of the freeze until the OT1 proposal submission deadline. 1. Delivery file & directory (a) OD tar file name : CYCLE019_PACS_FULL_1_20100706.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle019, CVS Version 1.1 (c) Does this delivery include a new Mission configuration? YES, Version 55.0 2. Mission Configurations (a) Does this delivery include a new Calibration mission configuration? YES (b) Does this delivery include a new ASTR mission configuration? YES high level SCR for cCCB: PHS-1486 (New Astronomer Mission Configuration PACS_MC_ASTR_OT1_2010-07-06B_C019_55) SPRs affecting ASTR backend PHS-1472 (unchopped PacsLineSpec) PHS-1477 (unchopped PacsRangeSpec) 3. Operations Issues (TC,HPSDB,SIAM,Real Time Science) (a) Will any of these delivered observations generate a significant amount of telecommands? NO (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? NO (c) ICC to add anything specific which HSC & MOC should be aware of The delivery contains observations on 2 SSOs, namely asteroids 2 Pallas and 704 Interamnia. The PACS photometer program on this 2 asteroids is in support of Herschel-Planck cross-calibration and must be scheduled for synchronisation reasons on OD 446, which is planned to be a parallel mode OD. However, it was several times confirmed at the Schedule Planning Meeting, that it will be feasible to incorporate the PACS observations on this OD. The delivery contains the following PACS RP calibration blocks: (for an overview, please see PACS Routine Phase Calibration Plan, PICC-MA-PL-002. Section numbers refer to the currently released issue 0.80.) * RPPhotBol 1.1.1bisA, PACS RP Cal Plan, section 6.1 on Arp 220 - monitor the bolometer responsivity and noise (reduced set of settings wrt. full PV characterization one year ago) * RPPhotFlux 3.2.4A, PACS RP Cal Plan, section 6.3 on Pallas - monitor the photometer linearity and absolute flux calibration for chop/nod point source mode (complemented by Herschel-Planck cross-calibration scan maps on same target) * RPPhotFlux 3.2.8A, PACS RP Cal Plan, section 6.4 on Arp 220 - monitor the photometer flat-field on external sources * RPPhotFlux 6.3.1A, PACS RP Cal Plan, section 10.5 on asteroids Pallas and Interamnia - Herschel- Planck cross-calibration synchronized with Planck sightings * RPSpecFlux 4.3.3A, PACS RP Cal Plan, section 6.9 on Pallas - monitor linearity with flux of the spectrometer and absolute flux calibration against external sources at key wavelengths * RPSpecFlux 4.3.4A, PACS RP Cal Plan, section 6.8 on HD 161796 - monitor absolute flux calibration reproducibility of the spectrometer Scheduling instructions per OD (from Readme file) (f) AOR distribution according to ODs and PACS sub-instruments: PACS PHOT (to be scheduled on OD 446) Herschel-Planck cross-calibration program with time constraint ===================================== RPPhotFlux_324A_cPS_200Jy_blu_Pallas_0002 RPPhotFlux_631A_sPS_070_Planck_blu_Pallas_0001 RPPhotFlux_631A_sPS_110_Planck_blu_Pallas_0001 RPPhotFlux_324A_cPS_50Jy_red_Pallas_0002 RPPhotFlux_631A_sPS_070_Planck_grn_Pallas_0001 RPPhotFlux_631A_sPS_110_Planck_grn_Pallas_0001 RPPhotFlux_631A_sPS_070_Planck_blu_Interamnia_0001 RPPhotFlux_631A_sPS_110_Planck_blu_Interamnia_0001 RPPhotFlux_631A_sPS_070_Planck_grn_Interamnia_0001 RPPhotFlux_631A_sPS_110_Planck_grn_Interamnia_0001 Each block shall be scheduled in the indicated sequence. PACS PHOT (to be scheduled on ODs 452, 453, 454) ================================================ RPPhotBol_111bisA_nStdRaster_bluInitDrct_Arp220_001 RPPhotBol_111bisA_nStdRaster_blu22Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_blu24Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_blu26Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_blu28Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_FinDrct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_grnInitDrct_Arp220_001 RPPhotBol_111bisA_nStdRaster_grn22Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_grn24Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_grn26Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_grn28Drct_Arp220_0001 RPPhotBol_111bisA_nStdRaster_FinDrct_Arp220_0002 RPPhotFlux_328A_StdScan_FlatField_blu_Arp220_0002 RPPhotFlux_328A_StdScan_FlatField_grn_Arp220_0002 Each block shall be scheduled in the indicated sequence. PACS SPEC (to be scheduled on OD 454) ===================================== RPSpecFlux_434A_nStdRange_RepFluxB2A_HD161796_0014 RPSpecFlux_434A_nStdRange_RepFluxB2B_HD161796_0014 RPSpecFlux_434A_nStdRange_RepFluxB3A_HD161796_0014 RPSpecFlux_433A_StdRange_AbsFluxA_Pallas_0001 RPSpecFlux_433A_StdRange_AbsFluxB_Pallas_0001 Each block shall be scheduled in the indicated sequence. Please acknowledge receipt of the e-mail and the delivery. Kind regards, Ulrich Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE019_PACS_FULL_1_20100706.tar New MC - MC P55_ASTR . 2. Software used for import + Source the Environment (if not already done!!) HCSS SOFTWARE = 2.0.1 (Always use the most recent HCSS Software version) PHS SOFTWARE = 2.3.0_PHS (Always use the most recent PHS Software version) Herjbo02 - HCSS_PHS_TEST_herjbo02_0_6_6.props file & source .minimal_herjbo02 : PHS: Using BUILDNUM 534 & PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 Machines used : - heropl02 - hscphs2 for the uplink co-ord part - heropl02 - hscphs2 for the PropHandler - heropl01 - hscmps1 for the MPS - herjbo02 - hsc_phs account Source the Environment before you proceed to step 3. hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v2.0.1 TAKE NOTE : If there is a newer HCSS software version in the otherSetups directory then source that new version. 3. What is the Mission Configuration Name going to be?? MC_H50ASTR_P55ASTR_S55ASTR_RP 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle19> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle19/HIFI> mkdir PACS_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle019_PACS_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the SPIRE directory from a previous mission_config subdirectory into the equivalent subdirectories of the MC_H42_P49_S55_CAL folder. Next remove in the SPIRE & HIFI subfolders all files which were created when you ran the SPIRE duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. SPIRE hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H42ASTR_P48ASTR_S55ASTR_RP/SPIRE/* . hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> ls CYCLE014_SPIRE_UPDATE_1_3_20100511.tar SPIRE_harness_duration_summary_20100512_11h28m24s.log SPIRE_cus_scripts.txt SPIRE_harness_duration_summary_20100512_15h50m08s.log SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml SPIRE_Duration.txt SPIRE_MC_ASTR_pv81_C014_55_CUS.def SPIRE_harness_duration_summary_20100512_11h23m32s.log SPIRE_Readme_C014_55.txt HIFI hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H50ASTR_P54ASTR_S55ASTR_RP/HIFI/* . hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> ls cus-defdur.sh* HIFI_MC_ASTR_A0017_C019_50_CUS_CAL.xml importall.sh* CYCLE019_HIFI_FULL_2_20100703.tar HIFI_MC_ASTR_A0017_C019_50_CUS.def summary_HIFI_AOR_C019_50.log default-durations.dat HIFI_MC_ASTR_A0017_C019_50.txt 6(a) Download & Untar the delivery from the CVS into the new mission_config directory (& the delivery directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle19/PACS/PACS_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle19/PACS/PACS_FULL_1> cvs login CVS password: hscphs2@heropl01/home/hscphs2/icchsc/delivery/Calibration_Cycle19/PACS/PACS_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle019/CYCLE019_PACS_FULL_1_20100706.tar U develop/data/observingmodes/rp_cycles/cycle019/CYCLE019_PACS_FULL_1_20100706.tar hscphs2@heropl01/home/hscphs2/icchsc/delivery/Calibration_Cycle19/PACS/PACS_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle019/CYCLE019_PACS_FULL_1_20100706.tar . hscphs2@heropl01/home/hscphs2/icchsc/delivery/Calibration_Cycle19/PACS/PACS_FULL_1> ls CYCLE019_PACS_FULL_1_20100706.tar develop/ hscphs2@heropl01/home/hscphs2/icchsc/delivery/Calibration_Cycle19/PACS/PACS_FULL_1> tar -xvf CYCLE019_PACS_FULL_1_20100706.tar PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS.def PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS_CAL.xml PACS_AOR_C019_55.aor PACS_Duration_PACS_compare.txt PACS_Readme_C019_55.txt 2createOBSMODtable4RP.sh hscphs2@heropl01/home/hscphs2/icchsc/delivery/Calibration_Cycle19/PACS/PACS_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS/ cp: omitting directory `develop' hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C019_55.txt CYCLE019_PACS_FULL_1_20100706.tar PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS_CAL.xml PACS_AOR_C019_55.aor PACS_MC_ASTR_OT1_2010-07-06B_C019_55_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@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> Jul 7, 2010 6:04:15 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:04:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:04:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:04:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:04:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:04:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:04:16 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jul 7, 2010 6:06:29 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@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Jul 7, 2010 6:06:52 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:06:53 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:06:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:06:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:06:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:06:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:07:00 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Jul 7, 2010 6:07:30 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:07:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:07:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:07:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:07:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:07:31 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:07:34 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 55.0). hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> cus -m "upload PACS_MC P55ASTR mission config" -import PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS.def -importcaltables PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS_CAL.xml Jul 7, 2010 6:10:28 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:10:29 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:10:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:10:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:10:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:10:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:10:52 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jul 7, 2010 6:10:52 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jul 7, 2010 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:10:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:10:59 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by PACS: PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS_CAL.xml CONFIRMED!! 6(e) Run the duration script for the PACS instrument model: Open duration script (2createOBSMODtable4RP.sh) and point it to HCSS 2.0.1 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C019_55.aor /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> ls -ls total 11180 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Jul 7 18:14 2createOBSMODtable4RP.sh* 5572 -rw-r--r-- 1 hscphs2 herschel 5693440 Jul 6 15:15 CYCLE019_PACS_FULL_1_20100706.tar 4 -rw-r--r-- 1 hscphs2 herschel 77 Jul 7 18:16 msgPacsCal_PacsPhotoDACSlowScan.txt 4 -rw-r--r-- 1 hscphs2 herschel 74 Jul 7 18:16 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 85 Jul 7 18:16 msgPacsCal_Phot_highGainBiasDirect_Fix.txt 0 -rw-r--r-- 1 hscphs2 herschel 59 Jul 7 18:15 msgPacsPhoto.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Jul 7 18:16 msgPacsRangeSpec.txt 144 -rw-r--r-- 1 hscphs2 herschel 141173 Jul 6 15:06 PACS_AOR_C019_55.aor 4 -rw-r--r-- 1 hscphs2 herschel 2112 Jul 6 15:10 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 2112 Jul 7 18:16 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 404091 Jul 6 12:17 PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS_CAL.xml 5024 -rw-r--r-- 1 hscphs2 herschel 5130838 Jul 6 12:17 PACS_MC_ASTR_OT1_2010-07-06B_C019_55_CUS.def 8 -rw-r--r-- 1 hscphs2 herschel 5830 Jul 6 15:12 PACS_Readme_C019_55.txt 4 -rw-r--r-- 1 hscphs2 herschel 1587 Jul 7 18:15 tmp 4 -rw-r--r-- 1 hscphs2 herschel 693 Jul 7 18:15 tmpobsmode hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! 6(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS MC P55ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. Now create the MC in the database hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> missetup -addconfig MC_H50ASTR_P55ASTR_S55ASTR_RP Jul 7, 2010 6:21:28 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:21:28 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:21:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:21:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:21:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:21:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:21:29 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Jul 7, 2010 6:21:29 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H50ASTR_P55ASTR_S55ASTR_RP" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Add the commited CUS to the new MC hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/PACS> Jul 7, 2010 6:21:49 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:21:50 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:21:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:21:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:21:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:21:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:21:50 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Jul 7, 2010 6:23:40 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H50ASTR_P55ASTR_S55ASTR_RP" Jul 7, 2010 6:23:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:23:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:23:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:23:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:24:56 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(b) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> Jul 7, 2010 6:26:08 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:26:09 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:26:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:26:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:26:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:26:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:26:09 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jul 7, 2010 6:26:17 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@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Jul 7, 2010 6:26:43 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:26:44 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:26:44 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:26:54 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Jul 7, 2010 6:27:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:27:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:27:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:27:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:27:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:27:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:27:06 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 old Instrument CUS & Cal tables into the DB Import old Mission Configuration (H50_ASTR) hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> cus -m "upload HIFI MC H50ASTR mission config" -import HIFI_MC_ASTR_A0017_C019_50_CUS.def -importcaltables HIFI_MC_ASTR_A0017_C019_50_CUS_CAL.xml Jul 7, 2010 6:28:20 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:28:20 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:28:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:28:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:28:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:28:21 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:28:33 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jul 7, 2010 6:28:33 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jul 7, 2010 6:28:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:28:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:28:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:28:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:28:37 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0017_C019_50_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by HIFI: HIFI_MC_ASTR_A0017_C019_50_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_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> rm Summary_durations.txt rm: remove regular file `Summary_durations.txt'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> ./cus-defdur.sh > Summary_durations.txt hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> ls -ls total 6388 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 11:33 cus-defdur.sh* 3160 -rw-r--r-- 1 hscphs2 herschel 3225600 Jul 3 11:08 CYCLE019_HIFI_FULL_2_20100703.tar 32 -rw-r--r-- 1 hscphs2 herschel 29317 Jul 2 16:40 default-durations.dat 1280 -rw-r--r-- 1 hscphs2 herschel 1303501 Jul 2 16:40 HIFI_MC_ASTR_A0017_C019_50_CUS_CAL.xml 1840 -rw-r--r-- 1 hscphs2 herschel 1879781 Jul 2 16:40 HIFI_MC_ASTR_A0017_C019_50_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1036 Jul 3 11:01 HIFI_MC_ASTR_A0017_C019_50.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 20:54 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29317 Jul 7 18:52 Summary_durations.txt 32 -rw-r--r-- 1 hscphs2 herschel 29317 Jul 5 11:51 summary_HIFI_AOR_C019_50.log hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> diff summary_HIFI_AOR_C019_50.log Summary_durations.txt Perfect! No differences, 7(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY In the Comment field, refer to HIFI MC H50ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. 7(g) Import HIFI into the new Mission Configuration hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/HIFI> Jul 7, 2010 6:55:36 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:55:37 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:55:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:55:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:55:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:55:37 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:55:37 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Jul 7, 2010 6:55:54 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H50ASTR_P55ASTR_S55ASTR_RP" Jul 7, 2010 6:56:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:56:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:56:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:56:11 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:57:01 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 Reset the OBDB/STPF properties 8(a) Set Instrument Model = SPIRE #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT Check with CUSGUI hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> Jul 7, 2010 6:57:40 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:57:40 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:57:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:57:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:57:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:57:41 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:57:41 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jul 7, 2010 6:58:29 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@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Jul 7, 2010 6:58:53 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:58:54 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:58:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:58:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:58:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:58:54 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:59:02 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Jul 7, 2010 6:59:11 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 6:59:12 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 6:59:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:59:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 6:59:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:59:12 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 6:59:16 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 55.0). hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> cus -m "upload SPIRE MC_55ASTR mission config" -import SPIRE_MC_ASTR_pv81_C014_55_CUS.def -importcaltables SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml Jul 7, 2010 7:00:14 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 7:00:14 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 7:00:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:00:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:00:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:00:15 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:00:30 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Jul 7, 2010 7:00:30 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Jul 7, 2010 7:00:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:00:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:00:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:00:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:00:33 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml" TAKE NOTE : The file referred to at the end import message shall correspond to the file that was delivered by PACS: SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the SPIRE instrument model: hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> ls -ls total 4684 2328 -rw-r--r-- 1 hscphs2 herschel 2375680 May 11 18:30 CYCLE014_SPIRE_UPDATE_1_3_20100511.tar 4 -rw-r--r-- 1 hscphs2 herschel 1912 Jul 7 19:01 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 May 11 18:14 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 5085 May 11 18:14 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 5085 May 12 11:28 SPIRE_harness_duration_summary_20100512_11h28m24s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5085 May 12 15:50 SPIRE_harness_duration_summary_20100512_15h50m08s.log 8 -rw-rw-rw- 1 hscphs2 herschel 5085 Jul 7 19:05 SPIRE_harness_duration_summary_20100707_19h05m34s.log 276 -rw-r--r-- 1 hscphs2 herschel 276611 May 11 18:14 SPIRE_MC_ASTR_pv81_C014_55_CUS_CAL.xml 2036 -rw-r--r-- 1 hscphs2 herschel 2078073 May 11 18:14 SPIRE_MC_ASTR_pv81_C014_55_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 3203 May 11 18:27 SPIRE_Readme_C014_55.txt hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20100707_19h05m34s.log Perfect. No differences! 8(f) If Durations are OK then COMMIT the Delivery with CUSGUI OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE SPIRE DELIVERY In the Comment field, refer to SPIRE MC S55ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. 8(g) Import SPIRE model into new Mission Configuration hscphs2@heropl01/home/hscphs2/icchsc/mission_config/MC_H50ASTR_P55ASTR_S55ASTR_RP/SPIRE> Jul 7, 2010 7:07:30 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 7:07:31 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 7:07:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:07:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:07:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:07:32 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:07:32 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Jul 7, 2010 7:07:51 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H50ASTR_P55ASTR_S55ASTR_RP" Jul 7, 2010 7:08:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:08:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:08:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:08:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:08:27 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_H50ASTR_P55ASTR_S55ASTR_RP Source the PHS Environment for 5.0.5_phs hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v5.0.5_phs hscphs2@heropl01/home/hscphs2/otherSetups> Jul 7, 2010 7:10:16 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Jul 7, 2010 7:10:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Jul 7, 2010 7:10:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:10:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Jul 7, 2010 7:10:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Jul 7, 2010 7:10:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Running CDH.getObsProgrammes() Jul 7, 2010 7:10:17 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Jul 7, 2010 7:10:17 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 30 Jul 7, 2010 7:10:17 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Jul 7, 2010 7:10:17 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H50ASTR_P55ASTR_S55ASTR_RP" Jul 7, 2010 7:10:22 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 4655 TAKE NOTE : The PropHandler Terminal log above shows that it is correctly pointing to the new Mission Configuration : CONFIRMED!! 10. Export the Hspot Files from PropHandler In PropHandler, select the Calibration pull down menu and export the HSpot files. TAKE NOTE : When the new window opens showing all the properties files, check that you have property files for SPIRE, PACS & HIFI. CONFIRMED!! Select all the files and in the new window that opens, create a new directory in /home/hscphs2/icchsc/HSpot_files/ Called the same as the Mission Confifguration: MC_H50ASTR_P55ASTR_S55ASTR_RP Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H50ASTR_P55ASTR_S55ASTR_RP Example of the last entry in the log: Jul 7, 2010 7:12:16 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H50ASTR_P55ASTR_S55ASTR_RP/HifiSScanProcLoadChopNoRefGen.prop Jul 7, 2010 7:12:16 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H50ASTR_P55ASTR_S55ASTR_RP/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl01/home/hscphs2/icchsc/HSpot_files/MC_H50ASTR_P55ASTR_S55ASTR_RP> ls *.prop > MC_H50ASTR_P55ASTR_S55ASTR_RP.txt hscphs2@heropl01/home/hscphs2/icchsc/HSpot_files/MC_H50ASTR_P55ASTR_S55ASTR_RP> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 13787 Jul 7 19:13 MC_H50ASTR_P55ASTR_S55ASTR_RP.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H50ASTR_P55ASTR_S55ASTR_RP> cp MC_H50ASTR_P55ASTR_S55ASTR_RP.txt /home/hscphs2/icchsc/HSpot_files/ hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H50ASTR_P55ASTR_S55ASTR_RP> cd .. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_H50ASTR_P54ASTR_S55ASTR_RP.txt MC_H50ASTR_P55ASTR_S55ASTR_RP.txt If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva. No new PACS script. Do not notify Eva & Jose 12. Final Jboss Activities Log into Jboss #2 herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02_old PHS: Using BUILDNUM 578 PHS: Using JBOSS_HOME /usr/local/software/jboss/jboss-3.2.6_0_6_5 Stop the Test Jboss : herjbo02.esac.esa.int/home/hsc_phs> stopJbossTest set old=/home/hsc_phs chdir /usr/local/software/jboss/jboss-3.2.6_0_6_5/bin if ( -f .keybind ) echo .keybind exists if ( -f .exrc ) echo .exrc exists ./shutdown.sh -s jnp://localhost:1199 Shutdown message has been posted to the server. Server shutdown may take a while - check logfiles for completion Create a directory which contains the name of the new MC : herjbo02.esac.esa.int/home/hsc_phs> mkdir fileHolder_ops_MC_H50ASTR_P55ASTR_S55ASTR_RP copied HSpot files from the HSpot_files directory on hscphs2 to this directory TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H50ASTR_P55ASTR_S55ASTR_RP> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H50ASTR_P55ASTR_S55ASTR_RP/ Next update the properties file: herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit HCSS_PHS_TEST_herjbo02_0_6_6.props & [1] 3171 Update each of the fields below in the Properties file : TAKE NOTE : Double check that this is done correctly!! #MARK TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_H48ASTR_P54ASTR_S55ASTR_RP_100623 hcss.phs.timeEstimatorVersion=MC_H50ASTR_P55ASTR_S55ASTR_RP_100707 #hcss.phs.timeEstimatorVersion=MC_H47_P54_S56_CAL_100623 #hcss.phs.timeEstimatorVersion=MC_H49_P54_S56_CAL_100707 #MARK MISSION CONFIG #hcss.ccm.mission.config = MC_H48ASTR_P54ASTR_S55ASTR_RP hcss.ccm.mission.config = MC_H50ASTR_P55ASTR_S55ASTR_RP #hcss.ccm.mission.config = MC_H47_P54_S56_CAL #hcss.ccm.mission.config = MC_H49_P54_S56_CAL #MARK DIRECTORIES #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H48ASTR_P54ASTR_S55ASTR_RP hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H50ASTR_P55ASTR_S55ASTR_RP #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H47_P54_S56_CAL #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H49_P54_S56_CAL Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.