Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2005-10-28 12:30:00 →
Size: 4658
Editor: pacs2
Comment:
← Revision 2 as of 2005-11-02 13:25:26 → ⇥
Size: 2191
Editor: ErichWiezorrek
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

----
Line 9: Line 7:

----

Author: Erich Wiezorrek[[BR]]
Version: 1.0[[BR]]
Date: October 28, 2205[[BR]]

----
Line 28: Line 16:
All 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.
Line 32: Line 27:
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 .
}}}
Line 33: Line 37:
Go to the directory where to place the input MIB files. Create the directory
if it doesn't exist (BUT is shall exist on our operational server).		 Assuming that all CUS procedures file names and only those end with ''.txt'' following command is ingesting them
to the database.
Line 36: Line 40:
cd ~/mib/raw cus -f -m"XXXth update for EQM IMT" -import *.txt
Line 38: Line 42:
Unzip the empty_mib_files.zip archive to make sure all necessary input files
for the MIBingestion exists.[[BR]]
Unzip the PACS_MIB_7_18.zip archive. When asked to overwrite files select the
option to overwrite all files.[[BR]]
On the operational server those archives are in the parent directory.		 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.
Line 44: Line 46:
unzip ../empty_mib_files.zip
unzip ../PACS_MIB_7_18.zip		 ( readonlyCUS; cus -f -m"xxxth update for EQM IMT" -import *.txt )
Line 47: Line 48:
Go to the parent directory and run MIBpreparation and MIBingestion.
Similar commands are used to ingest the uplink calibration tables.
Line 49: Line 51:
cd ..
preparemib ~/mib/raw ~/mib
ingestmib | & tee test.log		 cus -f -m "XXXth update for EQM IMT" -uploadcal tableFileName
( readonlyCUS; cus -f -m "XXXth update for EQM IMT" -uploadcal tableFileName )
Line 57: Line 58:
Line 59: Line 59:


Go to the directory where to place CUS files. Create the directory
if it doesn't exist (BUT is shall exist on our operational server).
{{{
cd ~/cus
}}}
Unzip the cus-definitions.zip archive which holds all initial CUS definitions
including the CUS tables..
{{{
unzip cus-definitions.zip
}}}
Load the TC definitions from the currently loaded MIB
{{{
cd ~/cus
cus -loadmib 1 <<EOF |& tee test.log
initial MIB version
EOF
}}}
Load the CUS tables
{{{
cat listOfCalibrationTables |xargs -t -i cus -m "Initial version" -uploadcal tables/\{\} \{\}
}}}
Load the CUS definitions (observing modes, building blocks, procedures)
{{{
cus -m "Initial version" -import registryDefinitions
}}}


Congratulation, it's done.


== Loading a MIB update ==


Go to the directory where to place the input MIB files. Create the directory
if it doesn't exist (BUT is shall exist on our operational server).
Remove all existing files ending with "*.dat".
{{{
cd ~/mib/raw
rm *.dat
}}}
Unzip the empty_mib_files.zip archive to make sure all necessary input files
for the MIBingestion exists.[[BR]]
Unzip the new PACS MIB archive. When asked to overwrite files select the
option to overwrite all files.[[BR]]
On the operational server the empty_mib_files.zip archive is in the
parent directory.
{{{
unzip ../empty_mib_files.zip
unzip yourPath/PACS_MIB_x_y.zip
}}}
Go to the parent directory and run MIBpreparation and MIBingestion.
{{{
cd ..
preparemib ~/mib/raw ~/mib
ingestmib | & tee test-PACS-MIB-x-y.log
}}}
If the MIB contains new TC definitions to be used by CUS those definitions
must be loaded by CUS.[[BR]]
The problem is to know the new MIB version number to be used during loading.
The "cus -listmibs" shall list MIB versions which have not been loaded yet.
If there is only a line printed "New mibs available" but no numbers this means
there are NO new MIBs.

In the statements below replace TBW with the MIB version number to be used
listed with the "cus -listmibs" command.
{{{
cd ~/cus
cus -listmibs
cus -loadmib TBW <<EOF |& tee test-TBW.log
MIB version TBW
EOF
}}}

Congratulation, it's done.



== Loading an update of CUS definitions (observation, building block, procedure): ==


Go to the directory where to place CUS files.[[BR]]
Create the directory a patch directory and step into this directory.[[BR]]
'''Don't''' use "patch1" but use a more verbose name.[[BR]]
{{{
cd ~/cus
mkdir patch1
cd patch1
}}}
Place the CUS definition text files in this directory.
{{{
cp whatever .
}}}

Loading the CUS tables if there are any updates.[[BR]]
Replace COMMENT with a real comment, FILE is the actual filename.
The TABLE name is optional if missing the filename is used.
{{{
cus -f -m "COMMENT" -uploadcal FILE [TABLE]
}}}

Load the CUS definitions (observing modes, building blocks, procedures) if
there are any updates.[[BR]]
Replace COMMENT with a real comment, FILE is the actual filename.
{{{
cus -f -m "COMMENT" -import FILE
}}}

Congratulation, it's done.

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.

Loading the initial CUS definitions:

Herschel: PACS/EQM_IMT_Procedures/CusUpdate_IMTatAstrium (last edited 2009-07-15 14:32:38 by localhost)