Updating the CUS database for IMT at Astrium

Procedure

• to update the PACS EQM IMT database with the CUS procedure definitions
• to update the PACS EQM IMT database with the CUS uplink table definitions

• to recreate the CcsHandler template TCl scripts for the HPCSS

General:

Usually updates for the CUS database are received via email form where they have to be extracted to single files. The rest of this procedure descriptions assumes following file extensions.

• .txt for the CUS procedures (modes, blocks, ...)
• no extension (at least not .txt or .csv) for CUS uplink tables

• .csv for CcsHandler "AOT" calls definitions

All commands below assume that you are logged using the pacs account on host hos4-d and that the psetup configuration has been executed.

ssh -X pacs@hos4-d
psetup

All CUS patches are collected in the /home/pacs/cus directory tree.

Updating CUS procedures and tables

Go to the /home/pacs/cus and create a cus patch directory for today in the format patches_YYYYMMDD. When there is more than one patches append A,B ... to the date to distinguish them. Copy all new CUS procedures and uplink tables to this directory.

cd ~/cus
mkdir patches_YYYYMMDD
cd patches_YYYYMMDD
cp fromeSomewhere .

Assuming that all CUS procedures file names and only those end with .txt following command is ingesting them to the database.

cus -f -m"XXXth update for EQM IMT" -import *.txt 

Replace XXXth with the current ordinal number for this CUS update.

The same command is used to update the readonly database as well. Don't miss the parenthesis around the command otherwise your terminal session will be permamently configured to use this readonly database.

( readonlyCUS; cus -f -m"xxxth update for EQM IMT" -import *.txt ) 

Similar commands are used to ingest the uplink calibration tables.

cus -f -m "XXXth update for EQM IMT" -uploadcal tableFileName
( readonlyCUS; cus -f -m "XXXth update for EQM IMT" -uploadcal tableFileName )

Congratulation, it's done.

Upgrading TCL template scripts for the HPCSS:

Create a patch directory named CCS_template_scripts_update_YYYYMMDD. Go to this directory.

mkdir ~/cus/CCS_template_scripts_update_YYYYMMDD
cd ~/cus/CCS_template_scripts_update_YYYYMMDD

The way how to upgrade your TCL templates depends on the input from the operations group:

• voice or email describing changes to the requested observation parameters
• nice CSV files describing templates requests

• Helmut's Exel sheet file (not described here)

voice or email describing changes to the requested observation parameters

nice CSV files describing templates requests

BR It is very important to update to link pointing to the most recent createTemplates files. Otherwise future updates will get confusing.

ln -sf `pwd`/createTemplates ../createTemplates

Recreating TCL template scripts and comparing with a previous release

Create a patch directory named CCS_template_scripts_update_YYYYMMDD if not created already in the previous section. Go to this directory.

mkdir ~/cus/CCS_template_scripts_update_YYYYMMDD
cd ~/cus/CCS_template_scripts_update_YYYYMMDD

Either use the createTemplates created in the previous section or copy the one linked by the ~/cus/createTemplates to the current patch directory.

cp ~/cus/createTemplates .   #BUT only if NO createTemplates files is created in the previous section

Create all TCL templates files by executing the createTemplates script. This will last some minutes.

./createTemplates

Transferring TCL template scripts to the HPCSS