HIFI Cycle 42 Cal delivery

HIFI  Delivery note - 25th May 2011

Dear HSC Colleagues,

This e-mail is to notify you that HIFI ICC has just delivered the CAL Mission Configuration
for cycle 42, uploading the tar file containing the delivery of HIFI observations for cycle 42
onto the CVS server.

1. Delivery file, directory:

a) OD tar file names:
- CYCLE042_HIFI_FULL_1_20110525.tar
b) CVS server directory:
- develop/data/observingmodes/rp_cycles/cycle042

2. Mission Configurations:

a) Does this delivery include a new Calibration Mission configuration?
Yes
b) Does this delivery include a new Astro Mission configuration?
Yes

3. Operations Issues
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?
Not a requirement.
c) ICC to add anything specific to this OD which HSC & MOC should be  aware of:
Instructions are in the Readme file.
This Mission Configuration need OBSW 6.5.3.

Please acknowledge receipt of the e-mail and the delivery.

Best regards,
Max

Take Note of the Tar File & the New MC name (for MPS email and for steps below)
CYCLE042_HIFI_FULL_1_20110525.tar 

New MC 

- Use MC H79Cal 


2. Software used for import + Source the Environment (if not already done!!)

[mkidger@herl38 ~]$ ssh -X hscphs2@heropl02
hscphs2@heropl02's password: 
Last login: Wed May 25 12:27:38 2011 from herl38.net4.lan
HCSS Version: 7.0.0
PHS Version: 5.3.2

Herjbo02 -  HCSS_PHS_TEST_herjbo02_0_6_6.props file & source
.minimal: PHS: Using BUILDNUM 534 & PHS: Using JBOSS_HOME
/usr/local/software/jboss/jboss-3.2.6_0_6_5

Machines used :
- heropl02 - hscphs2 for the uplink co-ord part
- heropl02 - hscphs2 for the PropHandler
- heropl01 - hscmps1 for the MPS
- herjbo02 - hsc_phs account


3. What is the Mission Configuration Name going to be??

MC_H79_P66_S63_CAL


4. Make the directories in the delivery directory and MC directory)

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42> ls
HIFI/  logs/  PACS/  SPIRE/

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI> mkdir HIFI_FULL_1

This LOG file has been placed in the /logs directory and given the name 

Cycle042_HIFI_FULL_1.log

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL> mkdir PACS

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL> mkdir SPIRE

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL> mkdir HIFI

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL> mkdir logs

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL> ls
HIFI/  logs/  PACS/  SPIRE/


5. Copy across the contents of the PACS directory from a previous
mission_config subdirectory into the equivalent subdirectories of the MC_H79_P66_S63_CAL folder.

Next remove in the subfolders all files which were created when
you ran the HIFI, SPIRE & PACS duration files e.g. tmp, SPIRE_cus_scipts, SPIRE_harness etc etc.

PACS

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> cp /home/hscphs2/icchsc/mission_config/MC_H78ASTR_P66ASTR_S63ASTR_AO/PACS/* .

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> rm tmp* msg* PACS_Duration_PACS.txt
rm: remove regular file `tmp'? y
rm: remove regular file `tmpobsmode'? y
rm: remove regular file `msgPacsCal_PacsRangeSpec_PV.txt'? y
rm: remove regular file `msgPacsCal_PacsSpecSlewCal35_Flex.txt'? y
rm: remove regular file `msgPacsEng_Pacs_EDAC_to_DMC_HK.txt'? y
rm: remove regular file `msgPacsLineSpec.txt'? y
rm: remove regular file `msgPacsPhoto.txt'? y
rm: remove regular file `msgPacsRangeSpec.txt'? y
rm: remove regular file `PACS_Duration_PACS.txt'? y

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> ls
2createOBSMODtable4RP.sh*          PACS_Duration_PACS_compare.txt
2createOBSMODtable4RP.sh~*         PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml
CYCLE040_PACS_FULL_1_20110428.tar  PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def
PACS_AOR_C040_66.aor               PACS_Readme_C040_66.txt


SPIRE

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> cp /home/hscphs2/icchsc/mission_config/MC_H78ASTR_P66ASTR_S63ASTR_AO/SPIRE/* .

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> ls
SPIRE_MC_ASTR_pv89_C042_1_CAL.def  SPIRE_MC_ASTR_pv89_C042_1_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_Cycle42/HIFI> setenv CVSROOT :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI> cvs login
Logging in to :pserver:lorourke@hercvs01.esac.esa.int:2401/services/repositories/HERSCHEL_CVS
CVS password: 

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI/HIFI_FULL_1> cvs co develop/data/observingmodes/rp_cycles/cycle042/CYCLE042_HIFI_FULL_1_20110525.tar
U develop/data/observingmodes/rp_cycles/cycle042/CYCLE042_HIFI_FULL_1_20110525.tar

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI/HIFI_FULL_1> cp develop/data/observingmodes/rp_cycles/cycle042/CYCLE042_HIFI_FULL_1_20110525.tar .

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI/HIFI_FULL_1> ls
CYCLE042_HIFI_FULL_1_20110525.tar  develop/

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI/HIFI_FULL_1> tar -xvf CYCLE042_HIFI_FULL_1_20110525.tar 
duration_cal.sh
HIFI_AOR_C042_79.aor
HIFI_AOR_C042_80.aor
HIFI_DUR_C042_79.txt
HIFI_MC_R086_FULL_79_0_CUS_CAL.xml
HIFI_MC_R086_FULL_79_0_CUS.def
HIFI_Readme_C042_79.txt

hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI/HIFI_FULL_1> ls
CYCLE042_HIFI_FULL_1_20110525.tar  HIFI_AOR_C042_76.aor                HIFI_MC_R083_FULL_77_0_CUS.def
develop/                           HIFI_AOR_C042_77.aor                HIFI_Readme_C042_77.txt
duration_cal.sh*                   HIFI_DUR_C042_77.txt
HIFI_AOR_C042_75.aor               HIFI_MC_R083_FULL_77_0_CUS_CAL.xml


hscphs2@heropl02/home/hscphs2/icchsc/delivery/Calibration_Cycle42/HIFI/HIFI_FULL_1> cp * /home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/HIFI/

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/HIFI> ls
CYCLE042_HIFI_FULL_1_20110525.tar  HIFI_AOR_C042_80.aor                HIFI_MC_R086_FULL_79_0_CUS.def
duration_cal.sh*                   HIFI_DUR_C042_79.txt                HIFI_Readme_C042_79.txt
HIFI_AOR_C042_79.aor               HIFI_MC_R086_FULL_79_0_CUS_CAL.xml


6(b) To import the old PACS delivery:

#CUS
#var.hcss.instrument = SPIRE
var.hcss.instrument = PACS
#var.hcss.instrument = HIFI
hcss.cus.model = FLIGHT


Check with CUSGUI

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> May 25, 2011 2:52:37 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 2:52:38 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 2:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 2:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 2:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 2:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 2:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 2:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 2:52:38 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 2:52:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 2:52:39 PM herschel.cus.gui.CusEditor chooseInstrument
INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument
May 25, 2011 2:53:14 PM herschel.cus.gui.CusEditor exit
INFO: Quitting.

TAKE NOTE : CONFIRM THAT PACS IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!!


6(c) Clean the CUS & Cal tables from the instrument model

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> cus -f -m "clean PACS CUS from DB" -deleteall
May 25, 2011 2:53:37 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 2:53:38 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 2:53:39 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 2:53:49 PM herschel.cus.gui.Cus infoMessage
INFO: All definitions have been deleted

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> cus -f -m "clean PACS CAL from DB" -caldeleteall
May 25, 2011 2:55:25 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 2:55:25 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 2:55:26 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 2:55:32 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 old Mission Configuration (Version 66.0).

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props 

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> cus -m "upload PACS_MC_66ASTR mission configuration as CAL" -import PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def -importcaltables PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml
May 25, 2011 3:01:34 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:01:35 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:01:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:02:05 PM herschel.cus.gui.Cus infoMessage
INFO: Definitions successfully imported
May 25, 2011 3:02:05 PM herschel.cus.gui.Cus infoMessage
INFO: Using current directory
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:02:06 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId
INFO: Creating new IdRegistry entry idreg_productIdRegistry
May 25, 2011 3:02:35 PM herschel.cus.gui.Cus infoMessage
INFO: Calibration tables successfully imported from "PACS_MC_ASTR_OT2_2011-04-28A_C040_66_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_OT2_2011-04-28A_C040_66_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 7.0.0

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> ./2createOBSMODtable4RP.sh PACS PACS_AOR_C040_66.aor /home/hscphs2/.hcss/Uplink_Coord_1_2.props /home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> ls -ls
total 11668
   4 -rwxr-xr-- 1 hscphs2 herschel    1538 May 25 15:08 2createOBSMODtable4RP.sh*
   4 -rwxr-xr-- 1 hscphs2 herschel    1538 May 25 15:08 2createOBSMODtable4RP.sh~*
5812 -rw-r--r-- 1 hscphs2 herschel 5939200 Apr 28 15:59 CYCLE040_PACS_FULL_1_20110428.tar
   4 -rw-r--r-- 1 hscphs2 herschel      74 May 25 15:14 msgPacsCal_PacsRangeSpec_PV.txt
   4 -rw-r--r-- 1 hscphs2 herschel      80 May 25 15:15 msgPacsCal_PacsSpecSlewCal35_Flex.txt
   4 -rw-r--r-- 1 hscphs2 herschel      75 May 25 15:11 msgPacsEng_Pacs_EDAC_to_DMC_HK.txt
   0 -rw-r--r-- 1 hscphs2 herschel      62 May 25 15:14 msgPacsLineSpec.txt
   0 -rw-r--r-- 1 hscphs2 herschel      59 May 25 15:13 msgPacsPhoto.txt
   0 -rw-r--r-- 1 hscphs2 herschel      63 May 25 15:14 msgPacsRangeSpec.txt
 208 -rw-r--r-- 1 hscphs2 herschel  205638 Apr 28 15:27 PACS_AOR_C040_66.aor
   4 -rw-r--r-- 1 hscphs2 herschel    3927 Apr 28 15:39 PACS_Duration_PACS_compare.txt
   4 -rw-r--r-- 1 hscphs2 herschel    3927 May 25 15:15 PACS_Duration_PACS.txt
 400 -rw-r--r-- 1 hscphs2 herschel  404163 Apr 28 15:02 PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS_CAL.xml
5200 -rw-r--r-- 1 hscphs2 herschel 5308486 Apr 28 15:02 PACS_MC_ASTR_OT2_2011-04-28A_C040_66_CUS.def
  12 -rw-r--r-- 1 hscphs2 herschel    9415 Apr 28 15:55 PACS_Readme_C040_66.txt
   4 -rw-r--r-- 1 hscphs2 herschel    2321 May 25 15:11 tmp
   4 -rw-r--r-- 1 hscphs2 herschel     989 May 25 15:11 tmpobsmode

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> diff PACS_Duration_PACS_compare.txt PACS_Duration_PACS.txt

Perfect. No differences!


6(f) If Durations are OK then COMMIT the Delivery with CUSGUI

OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE PACS DELIVERY

In the Comment field, refer to PACS MC P66ASTR as CAL


TAKE NOTE : It is very important that you commit the delivery as defined above.


Now create the MC in the database

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> missetup -addconfig MC_H79_P66_S63_CAL
May 25, 2011 3:23:32 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:23:33 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:23:33 PM herschel.ccm.tools.MissionSetup infoMessage
INFO: 
Using database "hsc_ops_operations_tm_1@herdb02.esac.esa.int"
May 25, 2011 3:24:00 PM herschel.ccm.tools.MissionSetup infoMessage
INFO: Mission configuration "MC_H79_P66_S63_CAL" created in database "hsc_ops_operations_tm_1@herdb02.esac.esa.int"

Add the commited CUS to the new MC

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/PACS> May 25, 2011 3:25:58 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:25:59 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:25:59 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:26:00 PM herschel.cus.gui.CusEditor chooseInstrument
INFO: Using instrument command set from PACS, specified by property hcss.cus.instrument
May 25, 2011 3:26:23 PM herschel.versant.ccm.MissionImpl getMissionConfiguration
INFO: Using configuration "MC_H79_P66_S63_CAL"
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:26:47 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId
INFO: Creating new IdRegistry entry idreg_productIdRegistry
May 25, 2011 3:26:56 PM herschel.cus.gui.CusEditor messageDialog
FINE: Instrument model created in MC_H79_P66_S63_CAL
May 25, 2011 3:27:07 PM herschel.cus.gui.CusEditor exit
INFO: Quitting.


Steps to import the new HIFI  Instrument model into the MC
Set Instrument Model = HIFI 
Check with CUSGUI
Run the duration script for the HIFI  instruments
Import HIFI into the new Mission Configuration


7(a) Set Instrument Model = HIFI

hscphs2@heropl02/home/hscphs2/.hcss> emacs Uplink_Coord.props &


#CUS
#var.hcss.instrument = SPIRE
#var.hcss.instrument = PACS
var.hcss.instrument = HIFI
hcss.cus.model = FLIGHT


Check with CUSGUI

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/HIFI> May 25, 2011 3:28:12 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:28:13 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:28:14 PM herschel.cus.gui.CusEditor chooseInstrument
INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument
May 25, 2011 3:28:39 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_H79_P66_S63_CAL/HIFI> cus -f -m "clean HIFI CUS from DB" -deleteall
May 25, 2011 3:32:55 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:32:56 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:32:56 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:33:11 PM herschel.cus.gui.Cus infoMessage
INFO: All definitions have been deleted

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/HIFI> cus -f -m "clean HIFI CAL from DB" -caldeleteall
May 25, 2011 3:33:34 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:33:36 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:33:36 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:33:42 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 new Mission Configuration (H79Cal).

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/HIFI> cus -m "upload HIFI MC79Cal mission config" -import HIFI_MC_R086_FULL_79_0_CUS.def -importcaltables HIFI_MC_R086_FULL_79_0_CUS_CAL.xml
May 25, 2011 3:34:50 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:34:51 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:34:51 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.cus.gui.Cus infoMessage
INFO: Definitions successfully imported
May 25, 2011 3:35:18 PM herschel.cus.gui.Cus infoMessage
INFO: Using current directory
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:35:18 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId
INFO: Creating new IdRegistry entry idreg_productIdRegistry
May 25, 2011 3:35:27 PM herschel.cus.gui.Cus infoMessage
INFO: Calibration tables successfully imported from "HIFI_MC_R086_FULL_79_0_CUS_CAL.xml"

TAKE NOTE : The file referred to at the end import message shall correspond
 to the file that was delivered by HIFI: HIFI_MC_R086_FULL_79_0_CUS_CAL.xml

CONFIRMED!!


7(e) Run the duration script for the HIFI instrument

Run the duration script delivered

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/HIFI> ./duration_cal.sh HIFI_AOR_C042_79
next AOR file = HIFI_AOR_C042_79
-- mode HifiEng_Chopper_FT2_COP
-- mode HifiEng_Chopper_Response_time_COP
-- mode HifiEng_Diplexer_Response_time_COP
-- mode HifiEng_FPU_FT_IVC_COP
-- mode HifiEng_HRS_FT_COP
-- mode HifiEng_LO_FT_IVC_COP
-- mode HifiEng_WBS_FT_COP

Total duration of HifiEng_Chopper_FT2_COP with default parameters  = 114
Total duration of HifiEng_Chopper_Response_time_COP with default parameters  = 44
Total duration of HifiEng_Diplexer_Response_time_COP with default parameters  = 85
Total duration of HifiEng_FPU_FT_IVC_COP with default parameters  = 65
Total duration of HifiEng_HRS_FT_COP with default parameters  = 1101
Total duration of HifiEng_LO_FT_IVC_COP with default parameters  = 227
Total duration of HifiEng_WBS_FT_COP with default parameters  = 1388

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/HIFI> diff HIFI_DUR_C042_79.txt summary_HIFI_AOR_C042_79.log

No differences.


7(f) If Durations are OK then COMMIT the Delivery with CUSGUI

OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE HIFI DELIVERY

In the Comment field, refer to HIFI MC H79CAL

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_H79_P66_S63_CAL/HIFI> May 25, 2011 3:39:04 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:39:06 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:39:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:39:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:39:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:39:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:39:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:39:06 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:39:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:39:07 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:39:07 PM herschel.cus.gui.CusEditor chooseInstrument
INFO: Using instrument command set from HIFI, specified by property hcss.cus.instrument
May 25, 2011 3:40:01 PM herschel.versant.ccm.MissionImpl getMissionConfiguration
INFO: Using configuration "MC_H79_P66_S63_CAL"
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:40:24 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId
INFO: Creating new IdRegistry entry idreg_productIdRegistry
May 25, 2011 3:40:36 PM herschel.cus.gui.CusEditor messageDialog
FINE: Instrument model created in MC_H79_P66_S63_CAL
May 25, 2011 3:40:49 PM herschel.cus.gui.CusEditor exit
INFO: Quitting.


Steps to Import the Old SPIRE Instrument model into the MC

Set Instrument Model = SPIRE
Check with CUSGUI
Run the duration script for the PACS instrument
Import into the new Mission Configuration


8(a) Set Instrument Model = SPIRE 

#CUS
var.hcss.instrument = SPIRE
#var.hcss.instrument = PACS
#var.hcss.instrument = HIFI
hcss.cus.model = FLIGHT


Check with CUSGUI

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> May 25, 2011 3:46:14 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:46:15 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:46:16 PM herschel.cus.gui.CusEditor chooseInstrument
INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument
May 25, 2011 3:46:39 PM herschel.cus.gui.CusEditor exit
INFO: Quitting.


TAKE NOTE : CONFIRM THAT SPIRE IS THE INSTRUMENT MODEL IN THE CUSGUI OUTPUT : CONFIRMED!!!!


8(c) Clean the CUS & Cal tables from the instrument model

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> cus -f -m "clean SPIRE CUS from DB" -deleteall
May 25, 2011 3:48:56 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:48:57 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:48:57 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:49:05 PM herschel.cus.gui.Cus infoMessage
INFO: All definitions have been deleted

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> cus -f -m "clean SPIRE CAL from DB" -caldeleteall
May 25, 2011 3:49:29 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:49:30 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:49:30 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:49:35 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 63.0).

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> cus -m "upload SPIRE MC_63ASTR mission config as CAL" -import SPIRE_MC_ASTR_pv89_C042_1_CUS.def -importcaltables SPIRE_MC_ASTR_pv89_C042_1_CAL.def
May 25, 2011 3:51:26 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 3:51:27 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 3:51:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:51:27 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:51:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:51:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:51:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:51:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:51:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:51:28 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:51:47 PM herschel.cus.gui.Cus infoMessage
INFO: Definitions successfully imported
May 25, 2011 3:51:47 PM herschel.cus.gui.Cus infoMessage
INFO: Using current directory
May 25, 2011 3:51:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:51:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 3:51:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:51:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 3:51:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:51:47 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 3:51:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:51:48 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 3:51:48 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId
INFO: Creating new IdRegistry entry idreg_productIdRegistry
May 25, 2011 3:51:53 PM herschel.cus.gui.Cus infoMessage
INFO: Calibration tables successfully imported from "SPIRE_MC_ASTR_pv89_C042_1_CAL.def"

TAKE NOTE : The file referred to at the end import message shall correspond
 to the file that was delivered by SPIRE: SPIRE_MC_ASTR_pv89_C042_1_CAL.def
CONFIRMED!!


8(e) Run the duration script for the SPIRE instrument model:

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> python SPIRE_CUS_THCP.py

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> ls -ls
total 15228
7592 -rw-r--r-- 1 hscphs2 herschel 7756432 May 17 09:06 All_SPIRE_MC_S63ASTR.aor
2600 -rw-r--r-- 1 hscphs2 herschel 2652160 May 23 14:26 CYCLE042_SPIRE_FULL_1_0_20110523.tar
 140 -rw-r--r-- 1 hscphs2 herschel  135192 May 23 13:27 SPIRE_AOR_C042_63_CAL.aor
  52 -rw-r--r-- 1 hscphs2 herschel   48434 May 23 13:28 SPIRE_AOR_C042_63_ENG.aor
   4 -rw-r--r-- 1 hscphs2 herschel    2063 May 25 15:53 SPIRE_cus_scripts.txt
   4 -rw-r--r-- 1 hscphs2 herschel    1174 May 23 13:57 SPIRE_CUS_THCP.py
   8 -rw-r--r-- 1 hscphs2 herschel    5534 May 23 14:04 SPIRE_Duration.txt
   8 -rw-rw-rw- 1 hscphs2 herschel    5534 May 23 15:37 SPIRE_harness_duration_summary_20110523_15h37m04s.log
   8 -rw-rw-rw- 1 hscphs2 herschel    5534 May 25 15:59 SPIRE_harness_duration_summary_20110525_15h59m19s.log
 280 -rw-r--r-- 1 hscphs2 herschel  278985 May 16 18:20 SPIRE_MC_ASTR_pv89_C042_1_CAL.def
2120 -rw-r--r-- 1 hscphs2 herschel 2159201 May 16 18:20 SPIRE_MC_ASTR_pv89_C042_1_CUS.def
 280 -rw-r--r-- 1 hscphs2 herschel  278985 May 23 13:57 SPIRE_MC_ASTR_pv89_C042_63_CUS_CAL.xml
2120 -rw-r--r-- 1 hscphs2 herschel 2159201 May 23 13:57 SPIRE_MC_ASTR_pv89_C042_63_CUS.def
  12 -rw-r--r-- 1 hscphs2 herschel    8669 May 23 14:19 SPIRE_Readme_C042_63.txt

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> diff  SPIRE_Duration.txt SPIRE_harness_duration_summary_20110525_15h59m19s.log

Perfect. No differences!


8(f) If Durations are OK then COMMIT the Delivery with CUSGUI

OPENED CUSGUI & COMMITTED (REGISTRY/COMMIT) THE SPIRE DELIVERY

In the Comment field, refer to SPIRE MC S62Cal.

TAKE NOTE : It is very important that you commit the delivery as defined above.


8(g) Import SPIRE model into new Mission Configuration

hscphs2@heropl02/home/hscphs2/icchsc/mission_config/MC_H79_P66_S63_CAL/SPIRE> May 25, 2011 4:06:15 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 4:06:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 4:06:17 PM herschel.cus.gui.CusEditor chooseInstrument
INFO: Using instrument command set from SPIRE, specified by property hcss.cus.instrument
May 25, 2011 4:06:30 PM herschel.versant.ccm.MissionImpl getMissionConfiguration
INFO: Using configuration "MC_H79_P66_S63_CAL"
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 4:06:43 PM herschel.versant.ccm.IdRegistryCommitThread findOrCreateId
INFO: Creating new IdRegistry entry idreg_productIdRegistry
May 25, 2011 4:06:51 PM herschel.cus.gui.CusEditor messageDialog
FINE: Instrument model created in MC_H79_P66_S63_CAL
May 25, 2011 4:07:01 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_H79_P66_S63_CAL

[mkidger@herl38 ~]$ ssh -X hscphs2@heropl02
hscphs2@heropl02's password: 
Last login: Wed May 25 14:33:08 2011 from herl23.net4.lan
HCSS Version: 7.0.0
PHS Version: 5.3.2

Enable gyro pointing...

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H73_P65_S62_GYRO> setenv HCSS_PROPS /home/hscphs2/.hcss/gyro_enable.props 

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H79_P66_S63_CAL> May 25, 2011 4:21:15 PM herschel.share.log.util.LogInitialiser init
INFO: Initialising using local log configuration file /home/hscphs2/.hcss/userlogging.properties
May 25, 2011 4:21:16 PM herschel.versant.store.ReplStoreFactoryImpl createStore
INFO: Creating ObjectStore: hsc_ops_operations_tm_1@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n2@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n3@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RO-Access for node: hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n4@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Using RW-Access for node: hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
May 25, 2011 4:21:17 PM herschel.versant.store.replication.ReplicatingTransaction connectToRemoteDatabase
INFO: Connection established to hsc_ops_operations_tm_1_n5@herdb02.esac.esa.int
Running CDH.getObsProgrammes()
May 25, 2011 4:21:17 PM herschel.phs.prophandler.gui.ProposalHandler message
INFO: Loading observation programmes list...
May 25, 2011 4:21:17 PM herschel.phs.prophandler.gui.ProposalHandler message
INFO:  
CDH: Getting obs progs took: 30
May 25, 2011 4:21:17 PM herschel.phs.prophandler.gui.ProposalHandler message
INFO: Loading observing modes list...
May 25, 2011 4:21:17 PM herschel.versant.ccm.MissionImpl getMissionConfiguration
INFO: Using configuration "MC_H79_P66_S63_CAL"
May 25, 2011 4:21:22 PM herschel.phs.prophandler.gui.ProposalHandler message
INFO:  
CDH: Getting obs modes took: 4728


TAKE NOTE : The PropHandler Terminal log above shows that it is correctly 
pointing to the new Mission Configuration : CONFIRMED!!
 

10. Export the Hspot Files from PropHandler

In PropHandler, select the Calibration pull down menu and export the HSpot 
files.

TAKE NOTE : When the new window opens showing all the properties files, check
 that you have property files for SPIRE, PACS & HIFI. CONFIRMED!!

Select all the files and in the new window that opens, create a new 
directory in

/home/hscphs2/icchsc/HSpot_files/

Called the same as the Mission Confifguration: 

Exported all the HSpot files to this folder:

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> mkdir MC_H79_P66_S63_CAL

Example of the last entry in the log:
May 25, 2011 4:24:47 PM herschel.phs.prophandler.gui.ProposalHandler message
INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H79_P66_S63_CAL/HifiEng_Fast_LCU_HK_COPGen.prop
May 25, 2011 4:24:47 PM herschel.phs.prophandler.gui.ProposalHandler message
INFO: Writing calibration prop file:/home/hscphs2/icchsc/HSpot_files/MC_H79_P66_S63_CAL/HifiManCmdSetIntoDissipativeGen.prop


11. Do the Check for a new script for Eva

Do the following:

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H79_P66_S63_CAL> ls *.prop > & MC_H79_P66_S63_CAL.txt

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H79_P66_S63_CAL> ls -ls *.txt
20 -rw-r--r-- 1 hscphs2 herschel 18246 May 25 16:26 MC_H79_P66_S63_CAL.txt

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H79_P66_S63_CAL> cp MC_H79_P66_S63_CAL.txt /home/hscphs2/icchsc/HSpot_files/

Now do a diff between this new txt file and the one generated with the last Mission configuration.

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files> diff MC_H77_P64_S62_CAL.txt MC_H79_P66_S63_CAL.txt
180a181
> PacsCal_PacsLineSpecGyroGen.prop
186a188
> PacsCal_PacsPhotoGyroGen.prop
505a508
> SpireSpectro_Cal_ScannedSmecCrossRasterGen.prop


If there is a difference inform Eva, Jose of the result. If there is NO difference then no need to inform Eva.

No new HIFI script.
Do not notify Eva & Jose


12. Final Jboss Activities

Log into Jboss #2

[mkidger@herl38 ~]$ ssh -X hsc_phs@herjbo02
hsc_phs@herjbo02's password: 
Last login: Wed May 25 16:10:08 2011 from herl28.net4.lan

herjbo02.esac.esa.int/tmp> cd

herjbo02.esac.esa.int/home/hsc_phs> source .minimal
PHS: Operationss instance 664
PHS: Astronomers instance 664
PHS: Using JBOSS_HOME /herschel/software/phs/jboss/jboss

Stop the Operations Jboss :

herjbo02.esac.esa.int/home/hsc_phs> stopJbossPhsOperations 
set old=/home/hsc_phs
chdir /herschel/software/phs/jboss/jboss/bin
if ( -f .keybind ) echo .keybind exists
if ( -f .exrc ) echo .exrc exists
./shutdown.sh -s jnp://localhost:1699
/herschel/software/phs/jboss/jboss/bin/shutdown.jar:/herschel/software/phs/jboss/jboss/client/jnet.jar
java
Shutdown message has been posted to the server.
Server shutdown may take a while - check logfiles for completion


herjbo02.esac.esa.int/home/hsc_phs> cd /herschel/data/files/phs/mcs

Create a directory which contains the name of the new MC :

herjbo02.esac.esa.int/herschel/data/files/phs/mcs> mkdir fileHolder_ops_MC_H79_P66_S63_CAL


copied HSpot files from the HSpot_files directory on hscphs2 to this directory

TAKE NOTE : You should perform this copy from the HSpot files folder on hscphs2. - DONE : SEE BELOW

hscphs2@heropl02/home/hscphs2/icchsc/HSpot_files/MC_H79_P66_S63_CAL> scp *.prop hsc_phs@herjbo02:/herschel/data/files/phs/mcs/fileHolder_ops_MC_H79_P66_S63_CAL/

Next update the properties file:

herjbo02.esac.esa.int/home/hsc_phs/.hcss> kedit phs-operations.props &

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_H78ASTR_P66ASTR_S63ASTR_AO_110517
#hcss.phs.timeEstimatorVersion=MC_H77_P64_S62_CAL-110427
hcss.phs.timeEstimatorVersion=MC_H79_P66_S63_CAL-110525
#hcss.phs.timeEstimatorVersion=MC_H73_P65_S62_GYRO-110408

#MARK MISSION CONFIG
#hcss.ccm.mission.config = MC_H78ASTR_P66ASTR_S63ASTR_AO
#hcss.ccm.mission.config = MC_H77_P64_S62_CAL
hcss.ccm.mission.config = MC_H79_P66_S63_CAL
#hcss.ccm.mission.config = MC_H73_P65_S62_GYRO

#MARK DIRECTORIES
#hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H78ASTR_P66ASTR_S63ASTR_AO
#hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H77_P64_S62_CAL
hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H79_P66_S63_CAL
#hcss.phs.fileHolder=/herschel/data/files/phs/mcs/fileHolder_ops_MC_H73_P65_S62_GYRO

Finally Restart the Test Jboss.

herjbo02.esac.esa.int/home/hsc_phs/.hcss> startJbossPhsOperations 
Starting instance phs-operations
[1] 16267

herjbo02.esac.esa.int/home/hsc_phs/.hcss> =========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /herschel/software/phs/jboss/jboss

  JAVA: /herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/bin/java

  JAVA_OPTS: -server -Xms1024m -Xmx3072m -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh

  CLASSPATH: /herschel/software/phs/jboss/jboss/bin/run.jar:/herschel/software/external/java/jdk1.6.0_17/jdk1.6.0_17-i586/lib/tools.jar

=========================================================================

16:36:17,023 INFO  [Server] Starting JBoss (MX MicroKernel)...
16:36:17,038 INFO  [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106)
16:36:17,039 INFO  [Server] Home Dir: /herschel/software/phs/jboss/jboss-3.2.6
16:36:17,039 INFO  [Server] Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/
16:36:17,039 INFO  [Server] Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/lib/
16:36:17,039 INFO  [Server] Patch URL: null
16:36:17,039 INFO  [Server] Server Name: phs-operations
16:36:17,039 INFO  [Server] Server Home Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations
16:36:17,042 INFO  [Server] Server Home URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/
16:36:17,042 INFO  [Server] Server Data Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/data
16:36:17,043 INFO  [Server] Server Temp Dir: /herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/tmp
16:36:17,043 INFO  [Server] Server Config URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/conf/
16:36:17,043 INFO  [Server] Server Library URL: file:/herschel/software/phs/jboss/jboss-3.2.6/server/phs-operations/lib/
16:36:17,043 INFO  [Server] Root Deployment Filename: jboss-service.xml
16:36:17,045 INFO  [Server] Starting General Purpose Architecture (GPA)...
16:36:17,659 INFO  [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.
16:36:17,659 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc.
16:36:17,659 INFO  [ServerInfo] OS-System: Linux 2.6.18-238.1.1.el5,i386
16:36:18,098 INFO  [Server] Core system initialized
16:36:20,448 INFO  [ServiceBindingManager] Initializing store
16:36:20,448 INFO  [ServiceBindingManager] Using StoreURL: file:/herschel/software/phs/jboss/jboss-3.2.6/docs/bindings.xml
16:36:20,960 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml

DONE.

LOGOUT OF THE JBOSS MACHINE. YOU ARE FINISHED WITH THIS LOG FILE.