1. Delivery Note SPIRE Delivery note - 9th April 2010 Dear Colleagues of the HSC MPS Group, This e-mail is to notify you that I have just uploaded the SPIRE Routine Calibration CYCLE012 tar file onto the CVS server. The contents in the tar files are according to the HSC-ICC Interactions Document, and Larry's latest update. 1. Delivery file, directory & Mission Configuration issues (a) Cycle tar file name : CYCLE012_SPIRE_FULL_1_0_20100409.tar (b) CVS server directory : develop/data/observingmodes/rp_cycles/cycle012 2. Mission Configurations (a) Does this delivery include a new Calibration Mission configuration(s)? NO (b) Does this delivery include a new ASTR mission configurations(s)? YES (c) If the answer to point (b) is YES, then have you copied the cCCB@sciops.esa.int in this delivery email? YES 3. Operations Issues (a) Will any of these delivered observations generate a significant amount of Telecommands? Some individual observations generate up to 1000 TC. (b) Do you wish to have these calibration observations scheduled in the Real Time Science period of the DTCP? NO (e) ICC to add anything specific to this OD which HSC & MOC should be aware of. For HSC (and PACS): The times of the REDY/STBY scripts change with this MC. This ASTR MC fixes the problem with the Pmode (see SXR/readme for other changes). This delivery contains things for Rcal, final 7-pt jiggle obs, spec aot obs, SIAM checks.... Please acknowledge the receipt of this delivery to us. Kind regards, Sarah Take Note of the Tar File & the New MC name (for MPS email and for steps below) CYCLE012_SPIRE_FULL_1_0_20100409.tar New MC - MC S52ASTR (not named above). 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_H36ASTR_P47ASTR_S52ASTR_RP/ 4. Make the directories in the delivery directory and MC directory) hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12> ls HIFI/ logs/ PACS/ SPIRE/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/HIFI> mkdir SPIRE_FULL_1 This LOG file has been placed in the /logs directory and given the name Cycle012_SPIRE_FULL_1.log. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP> mkdir PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP> mkdir SPIRE hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP> mkdir HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP> mkdir logs hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP> ls HIFI/ logs/ PACS/ SPIRE/ 5. Copy across the contents of the HIFI directory from a previous mission_config subdirectory intothe equivalent subdirectories of the MC_H36ASTR_P47ASTR_S52ASTR_RP folder. Next remove in the PACS & SPIRE subfolders all files which were created when you ran the SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc. HIFI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> cp /home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S50ASTR_RP/HIFI/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> ls cus-defdur.sh* HIFI_default_summary.txt HIFI_MC_ASTR_A0006_C011_36.txt CYCLE011_HIFI_FULL_4_20100403.tar HIFI_MC_ASTR_A0006_C011_36_CUS_CAL.xml importall.sh* default-durations.dat HIFI_MC_ASTR_A0006_C011_36_CUS.def PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S50ASTR_RP/PACS/* . hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> ls 2createOBSMODtable4RP.sh* PACS_AOR_C011_44.aor PACS_Readme_C011_47.txt CYCLE011_PACS_FULL_4_20100322.tar PACS_Duration_PACS_compare.txt tmp msgPacsCal_PacsRangeSpec_PV.txt PACS_Duration_PACS.txt tmpobsmode msgPacsCal_WaveCalNoChop.txt PACS_MC_ASTR_CalPhase_2010-03-22B_C011_47_CUS_CAL.xml msgPacsRangeSpec.txt PACS_MC_ASTR_CalPhase_2010-03-22B_C011_47_CUS.def hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> rm msg* PACS_Duration_PACS.txt tmp* rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.txt'? y rm: remove regular file `msgPacsCal_WaveCalNoChop.txt'? y rm: remove regular file `msgPacsRangeSpec.txt'? y rm: remove regular file `PACS_Duration_PACS.txt'? y rm: remove regular file `tmp'? y rm: remove regular file `tmpobsmode'? y hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> ls 2createOBSMODtable4RP.sh* PACS_Duration_PACS_compare.txt PACS_Readme_C011_47.txt CYCLE011_PACS_FULL_4_20100322.tar PACS_MC_ASTR_CalPhase_2010-03-22B_C011_47_CUS_CAL.xml PACS_AOR_C011_44.aor PACS_MC_ASTR_CalPhase_2010-03-22B_C011_47_CUS.def 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_Cycle12/SPIRE/SPIRE_FULL_1> setenv CVSROOT :pserver:lorourke@cvs.rssd.esa.int:/services/repositories/HERSCHEL_CVS hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/SPIRE/SPIRE_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_Cycle12/SPIRE/SPIRE_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle012/CYCLE012_SPIRE_FULL_1_0_20100409.tar U develop/data/observingmodes/rp_cycles/cycle012/CYCLE012_SPIRE_FULL_1_0_20100409.tar hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/SPIRE/SPIRE_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle012/CYCLE012_SPIRE_FULL_1_0_20100409.tar . hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/SPIRE/SPIRE_FULL_1> ls CYCLE012_SPIRE_FULL_1_20100304.tar develop/ hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/SPIRE/SPIRE_FULL_1> tar -xvf CYCLE012_SPIRE_FULL_1_0_20100409.tar SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml SPIRE_MC_ASTR_pv77_C012_52_CUS.def SPIRE_AOR_C012_52_CAL.aor SPIRE_AOR_C012_52_ENG.aor SPIRE_CUS_THCP.py SPIRE_Duration.txt SPIRE_Readme_C012_52.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/SPIRE/SPIRE_FULL_1> ls CYCLE012_SPIRE_FULL_1_0_20100409.tar SPIRE_AOR_C012_52_ENG.aor SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml develop/ SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv77_C012_52_CUS.def SPIRE_AOR_C012_52_CAL.aor SPIRE_Duration.txt SPIRE_Readme_C012_52.txt hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle12/SPIRE/SPIRE_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE/ cp: omitting directory `develop' hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> ls CYCLE012_SPIRE_FULL_1_0_20100409.tar SPIRE_CUS_THCP.py SPIRE_MC_ASTR_pv77_C012_52_CUS.def SPIRE_AOR_C012_52_CAL.aor SPIRE_Duration.txt SPIRE_Readme_C012_52.txt SPIRE_AOR_C012_52_ENG.aor SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml 6(a) To import the new SPIRE delivery: #CUS var.hcss.instrument = SPIRE #var.hcss.instrument = PACS #var.hcss.instrument = HIFI hcss.cus.model = FLIGHT 6(b) Set the Instrument Model & check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> Apr 9, 2010 6:21:56 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:21:57 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:21:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:21:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:21:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:21:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:21:57 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 9, 2010 6:22:07 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Clean CUS & Cal and import old SPIRE MC hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall Apr 9, 2010 6:22:34 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:22:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:22:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:22:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:22:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:22:35 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:22:44 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall Apr 9, 2010 6:22:48 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:22:49 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:22:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:22:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:22:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:22:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:22:54 PM herschel.cus.gui.Cus infoMessage INFO: All calibration tables successfully deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> cus -m "upload SPIRE_MC_52ASTR mission config" -import SPIRE_MC_ASTR_pv77_C012_52_CUS.def -importcaltables SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml Apr 9, 2010 6:30:49 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:30:49 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:30:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:30:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:30:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:30:50 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:31:04 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 9, 2010 6:31:04 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 9, 2010 6:31:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:31:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:31:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:31:04 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:31:07 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml" 7. Run the duration script & perform a diff with the ICC_DUR file. Rename the supplied Duration file so that the python script will run hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP/SPIRE> python SPIRE_CUS_THCP.py hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> ls -ls total 5484 2728 -rw-r--r-- 1 hscphs2 herschel 2785280 Apr 9 18:19 CYCLE012_SPIRE_FULL_1_0_20100409.tar 136 -rw-r--r-- 1 hscphs2 herschel 131289 Apr 9 18:07 SPIRE_AOR_C012_52_CAL.aor 280 -rw-r--r-- 1 hscphs2 herschel 280090 Apr 9 18:07 SPIRE_AOR_C012_52_ENG.aor 4 -rw-r--r-- 1 hscphs2 herschel 1881 Apr 9 18:31 SPIRE_cus_scripts.txt 4 -rw-r--r-- 1 hscphs2 herschel 1174 Apr 9 18:17 SPIRE_CUS_THCP.py 8 -rw-r--r-- 1 hscphs2 herschel 4970 Apr 9 18:17 SPIRE_Duration.txt 8 -rw-rw-rw- 1 hscphs2 herschel 4970 Apr 9 18:35 SPIRE_harness_duration_summary_20100409_18h35m27s.log 268 -rw-r--r-- 1 hscphs2 herschel 269717 Apr 9 18:17 SPIRE_MC_ASTR_pv77_C012_52_CUS_CAL.xml 2032 -rw-r--r-- 1 hscphs2 herschel 2072931 Apr 9 18:17 SPIRE_MC_ASTR_pv77_C012_52_CUS.def 16 -rw-r--r-- 1 hscphs2 herschel 13193 Apr 9 18:17 SPIRE_Readme_C012_52.txt hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> diff SPIRE_Duration.txt SPIRE_harness_duration_summary_20100409_18h35m27s.log Perfect hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> missetup -addconfig MC_H36ASTR_P47ASTR_S52ASTR_RP Apr 9, 2010 6:05:48 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:05:49 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:05:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:05:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:05:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:05:49 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:05:49 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" Apr 9, 2010 6:05:50 PM herschel.ccm.tools.MissionSetup infoMessage INFO: Mission configuration "MC_H36ASTR_P47ASTR_S52ASTR_RP" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int" TAKE NOTE : Confirm the correct Mission Config Name has been created as shown in the last line above : CONFIRMED. COMMIT delivery and import hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/SPIRE> Apr 9, 2010 6:37:23 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:37:23 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:37:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:37:24 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument Apr 9, 2010 6:37:39 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H36ASTR_P47ASTR_S52ASTR_RP" Apr 9, 2010 6:37:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:37:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:37:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:37:55 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:38:14 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : If you have selected the correct Mission Configuration then you can confirm this in the cusgui log as shown above. THIS ENDS THE IMPORT OF THE OLD SPIRE INSTRUMENT MODEL INTO THE MISSION CONFIGURATION. Steps to import the old HIFI Instrument model into the MC Set Instrument Model = HIFI Check with CUSGUI Run the duration script for the HIFI instruments Import HIFI into the new Mission Configuration 7(a) Set Instrument Model = HIFI hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props & #CUS #var.hcss.instrument = SPIRE #var.hcss.instrument = PACS var.hcss.instrument = HIFI hcss.cus.model = FLIGHT 7(b) Check with CUSGUI hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> Apr 9, 2010 5:33:57 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 5:33:58 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 5:33:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:33:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:33:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:33:58 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:33:58 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 9, 2010 5:34:08 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : Instrument above must be HIFI if you want to work with the HIFI instrument model. - CONFIRMED!! 7(c) Clean the CUS & Cal tables from the instrument model hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall Apr 9, 2010 5:35:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 5:35:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 5:35:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:35:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:35:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:35:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:35:11 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall Apr 9, 2010 5:35:16 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 5:35:17 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 5:35:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:35:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:35:23 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 (H36ASTR). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> cus -m "upload HIFI H36ASTR mission config" -import HIFI_MC_ASTR_A0006_C011_36_CUS.def -importcaltables HIFI_MC_ASTR_A0006_C011_36_CUS_CAL.xml Apr 9, 2010 5:38:09 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 5:38:10 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 5:38:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:38:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:38:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:38:10 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:38:25 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Apr 9, 2010 5:38:25 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Apr 9, 2010 5:38:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:38:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 5:38:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:38:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 5:38:31 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "HIFI_MC_ASTR_A0006_C011_36_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_A0006_C011_36_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_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> ./cus-defdur.sh > summary_dur.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> ls -ls total 5264 4 -rwxr-xr-x 1 hscphs2 herschel 719 Mar 25 11:33 cus-defdur.sh* 2600 -rw-r--r-- 1 hscphs2 herschel 2652160 Apr 3 11:13 CYCLE011_HIFI_FULL_4_20100403.tar 32 -rw-r--r-- 1 hscphs2 herschel 29145 Mar 25 14:27 default-durations.dat 32 -rw-r--r-- 1 hscphs2 herschel 29145 Apr 3 17:46 HIFI_default_summary.txt 744 -rw-r--r-- 1 hscphs2 herschel 754371 Apr 3 10:44 HIFI_MC_ASTR_A0006_C011_36_CUS_CAL.xml 1812 -rw-r--r-- 1 hscphs2 herschel 1851345 Apr 3 10:43 HIFI_MC_ASTR_A0006_C011_36_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 1026 Apr 3 10:48 HIFI_MC_ASTR_A0006_C011_36.txt 4 -rwxr-xr-x 1 hscphs2 herschel 191 Feb 9 20:54 importall.sh* 32 -rw-r--r-- 1 hscphs2 herschel 29145 Apr 9 18:02 summary_dur.log hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> diff default-durations.dat summary_dur.log 135c135 < Duration of HIFILCUChecksumAndSetHKCloseObs with default parameters = 5 --- > Duration of HIFILCUChecksumAndSetHKCloseObs with default parameters = 1 394c394 < Duration of HifiEngSetFromNormal_IntoDissipative_II with default parameters = 46 --- > Duration of HifiEngSetFromNormal_IntoDissipative_II with default parameters = 42 Same differences as in previous import. Due to wrong default durations file. These values are correct. 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 H36ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. 7(g) Import HIFI into the new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/HIFI> Apr 9, 2010 6:06:25 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:06:26 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:06:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:06:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:06:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:06:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:06:26 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument Apr 9, 2010 6:06:56 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H36ASTR_P47ASTR_S52ASTR_RP" Apr 9, 2010 6:07:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:07:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:07:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:07:08 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:07:31 PM herschel.cus.gui.CusEditor exit INFO: Quitting. Steps to Import the New PACS Instrument model into the MC Set Instrument Model = PACS 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 = PACS #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_H36ASTR_P47ASTR_S52ASTR_RP/PACS> Apr 9, 2010 6:09:32 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:09:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:09:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:09:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:09:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:09:34 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:09:34 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 9, 2010 6:09:45 PM herschel.cus.gui.CusEditor exit INFO: Quitting. TAKE NOTE : CONFIRM THAT PACS IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!! 8(c) Clean the CUS & Cal tables from the instrument model Skip this bit. PACS CUS is stable. hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP/PACS> cus -f -m "clean PACS CUS from DB" -deleteall Mar 5, 2010 1:02:42 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Mar 5, 2010 1:02:43 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 5, 2010 1:02:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:02:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:02:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:02:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:02:55 PM herschel.cus.gui.Cus infoMessage INFO: All definitions have been deleted hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall Mar 5, 2010 1:03:00 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Mar 5, 2010 1:03:01 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 5, 2010 1:03:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:03:01 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:03:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:03:02 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:03:07 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_MOC7_201002011600 - CONFIRMED!! 8(d) Import the new Instrument CUS & Cal tables into the DB Import new Mission Configuration (Version 44.0). hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H31ASTR_P44ASTR_S50ASTR_RP/PACS> cus -m "upload PACS_MC_44ASTR mission config" -import PACS_MC_ASTR_CalPhase_2010-03-04A_C010_44_CUS.def -importcaltables PACS_MC_ASTR_CalPhase_2010-03-04A_C010_44_CUS_CAL.xml Mar 5, 2010 1:04:27 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Mar 5, 2010 1:04:28 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Mar 5, 2010 1:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:04:29 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:04:51 PM herschel.cus.gui.Cus infoMessage INFO: Definitions successfully imported Mar 5, 2010 1:04:51 PM herschel.cus.gui.Cus infoMessage INFO: Using current directory Mar 5, 2010 1:04:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:04:52 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Mar 5, 2010 1:04:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:04:53 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Mar 5, 2010 1:04:57 PM herschel.cus.gui.Cus infoMessage INFO: Calibration tables successfully imported from "PACS_MC_ASTR_CalPhase_2010-03-04A_C010_44_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_CalPhase_2010-03-04A_C010_44_CUS_CAL.xml CONFIRMED!! 8(e) Run the duration script for the PACS instrument model: Open duration script and point it to HCSS 2.0.1 hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C011_44.aor /home/hscphs2/.hcss/Uplink_Coord.props /home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> ls -ls total 10712 4 -rwxr-xr-- 1 hscphs2 herschel 1538 Mar 5 14:01 2createOBSMODtable4RP.sh* 5272 -rw-r--r-- 1 hscphs2 herschel 5386240 Mar 22 16:20 CYCLE011_PACS_FULL_4_20100322.tar 4 -rw-r--r-- 1 hscphs2 herschel 74 Apr 9 18:11 msgPacsCal_PacsRangeSpec_PV.txt 4 -rw-r--r-- 1 hscphs2 herschel 71 Apr 9 18:13 msgPacsCal_WaveCalNoChop.txt 0 -rw-r--r-- 1 hscphs2 herschel 63 Apr 9 18:12 msgPacsRangeSpec.txt 132 -rw-r--r-- 1 hscphs2 herschel 130563 Mar 12 15:52 PACS_AOR_C011_44.aor 4 -rw-r--r-- 1 hscphs2 herschel 1594 Mar 12 16:10 PACS_Duration_PACS_compare.txt 4 -rw-r--r-- 1 hscphs2 herschel 1594 Apr 9 18:13 PACS_Duration_PACS.txt 400 -rw-r--r-- 1 hscphs2 herschel 401435 Mar 22 16:06 PACS_MC_ASTR_CalPhase_2010-03-22B_C011_47_CUS_CAL.xml 4876 -rw-r--r-- 1 hscphs2 herschel 4978487 Mar 22 16:06 PACS_MC_ASTR_CalPhase_2010-03-22B_C011_47_CUS.def 4 -rw-r--r-- 1 hscphs2 herschel 2693 Mar 22 16:19 PACS_Readme_C011_47.txt 4 -rw-r--r-- 1 hscphs2 herschel 1271 Apr 9 18:11 tmp 4 -rw-r--r-- 1 hscphs2 herschel 467 Apr 9 18:11 tmpobsmode hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt Perfect. No differences! 8(f) If Durations are OK then COMMIT the Delivery with CUSGUI No new CUS. Don't commit. OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY In the Comment field, refer to PACS MC P44ASTR TAKE NOTE : It is very important that you commit the delivery as defined above. just import 8(g) Import PACS model into new Mission Configuration hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H36ASTR_P47ASTR_S52ASTR_RP/PACS> Apr 9, 2010 6:14:55 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:14:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:14:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:14:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:14:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:14:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:14:56 PM herschel.cus.gui.CusEditor chooseInstrument INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument Apr 9, 2010 6:15:36 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H36ASTR_P47ASTR_S52ASTR_RP" Apr 9, 2010 6:15:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:15:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:15:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:15:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:16:25 PM herschel.cus.gui.CusEditor exit INFO: Quitting. THIS ENDS THE IMPORT OF THE PACS 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_H31ASTR_P44ASTR_S52ASTR_RP Source the PHS Environment for 2.3.0_phs hscphs2@heropl02/home/hscphs2/otherSetups> source setHcssEnvironment_v2.3.0_phs hscphs2@heropl02/home/hscphs2/otherSetups> Apr 9, 2010 6:39:07 PM herschel.share.log.util.LogInitialiser init INFO: Initialising using local log configuation file /home/hscphs2/.hcss/userlogging.properties Apr 9, 2010 6:39:08 PM herschel.versant.store.ReplStoreFactoryImpl createStore INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int Apr 9, 2010 6:39:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:39:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int Apr 9, 2010 6:39:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Apr 9, 2010 6:39:09 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int Running CDH.getObsProgrammes() Apr 9, 2010 6:39:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observation programmes list... Apr 9, 2010 6:39:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs progs took: 31 Apr 9, 2010 6:39:09 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Loading observing modes list... Apr 9, 2010 6:39:09 PM herschel.versant.ccm.MissionImpl getMissionConfiguration INFO: Using configuration "MC_H36ASTR_P47ASTR_S52ASTR_RP" Apr 9, 2010 6:39:14 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: CDH: Getting obs modes took: 5233 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_H31ASTR_P44ASTR_S52ASTR_RP Exported all the HSpot files to this folder: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H31ASTR_P44ASTR_S52ASTR_RP Example of the last entry in the log: Apr 9, 2010 6:41:44 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H36ASTR_P47ASTR_S52ASTR_RP/HifiSScanProcLoadChopNoRefGen.prop Apr 9, 2010 6:41:44 PM herschel.phs.prophandler.gui.ProposalHandler message INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H36ASTR_P47ASTR_S52ASTR_RP/HifiMappingProcFSwitchOTFNoRefGen.prop 11. Do the Check for a new script for Eva Do the following: hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H36ASTR_P47ASTR_S52ASTR_RP> ls *.prop > & MC_H36ASTR_P47ASTR_S52ASTR_RP.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H36ASTR_P47ASTR_S52ASTR_RP> ls -ls *.txt 16 -rw-r--r-- 1 hscphs2 herschel 13704 Apr 9 18:47 MC_H36ASTR_P47ASTR_S52ASTR_RP.txt hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H36ASTR_P47ASTR_S52ASTR_RP> cp MC_H36ASTR_P47ASTR_S52ASTR_RP.txt /home/hscphs2/icchsc/HSpot_files/ Now do a diff between this new txt file and the one generated with the last Mission configuration. hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_H36ASTR_P47ASTR_S50ASTR_RP.txt MC_H36ASTR_P47ASTR_S52ASTR_RP.txt 319a320 > SpireEngBsmTuneChopSettingsGen.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 script. Notify Eva & Jose 12. Final Jboss Activities Log into Jboss #2 herjbo02.esac.esa.int/home/hsc_phs> source .minimal_herjbo02 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_H36ASTR_P47ASTR_S52ASTR_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_H36ASTR_P47ASTR_S52ASTR_RP> scp *.prop hsc_phs@herjbo02:/home/hsc_phs/fileHolder_ops_MC_H36ASTR_P47ASTR_S52ASTR_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 & CHIQUI TIME ESTIMATOR #hcss.phs.timeEstimatorVersion=MC_MAN_S7_100329 hcss.phs.timeEstimatorVersion=MC_H36ASTR_P47ASTR_S52ASTR_RP_100409 #hcss.phs.timeEstimatorVersion=MC_H35_P47_S51_PV_100403 #MARK & CHIQUI MISSION CONFIG #hcss.ccm.mission.config = MC_MAN_S7 hcss.ccm.mission.config = MC_H36ASTR_P47ASTR_S52ASTR_RP #hcss.ccm.mission.config = MC_H35_P47_S51_PV #MARK & CHIQUI DIRECTORIES #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_MAN_S7 hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H36ASTR_P47ASTR_S52ASTR_RP #hcss.phs.fileHolder=/home/hsc_phs/fileHolder_ops_MC_H35_P47_S51_PV Finally Restart the Test Jboss. > startJbossTest DONE. LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.