Project

General

Profile

Actions

Feature #2118

open

Prepare the Command Line Interface of validator to parse rdRam

Added by Lafage Vincent about 13 years ago. Updated about 13 years ago.

Status:
New
Priority:
Low
Assigned To:
Target version:
-
Start date:
10/19/2011
Due date:
% Done:

0%

Estimated time:

Description

Now, parsing a rdRam command result
$CROCUS_SCRIPTS_PATH/getCmdRes.x -m $Minor -c $Channel -r/tmp/rdRamCrocusCmdRes${aEqId}.res > /tmp/rdRamCrocusOutput${aEqId}.out
$LC2_INSTALL/bin/crocus_validator -f $LC2_CONFIG/init${aEqId}.dat -c rdRam -k $TMP_CONFIG/rdRam${aEqId}.dat -r /tmp/rdRamCrocusCmdRes${aEqId}.res

fails producing tons of error

Manu::EvaluateOwnErrors: TestRamPedestal ManuID 1134 outside limits: 0 pedestals for 64 memory

as NO pedestals are loaded INTO validator memory…

$LC2_INSTALL/bin/crocus_file_generator -p 4 -c ldPed -k $DAQ_DETDB_LOCAL/MUONTRKPEDda.ped -f $LC2_CONFIG/init${aEqId}.dat -r $TMP_CONFIG/ldPed${aEqId}.dat

The ldPed file should be passed to validator either with -p (pedestal) or -m (memory) option

Actions

Also available in: Atom PDF