PiBeta Analyzer FAQs

How can I analyze several runs with one command ?

Use the -r switch together with a run number substitution in the input, output and configuration file names like:

analyzer -r 120 125 -i run%d.asc.gz -o res%d.rz -c cal%d.odb

I want to analyze a single file many times. How can I speed up this process?

Reading the .asc.gz file takes some time. It is much faster to read from a MIDAS binary file. You can convert a file easily with the analyzer:

analyzer -v -i run123.asc.gz -o run123.mid

Reading from run123.mid is then much faster.

The analyzer and ODBEdit don't start any more because of a strange ODB error.

The ODB can be screwed up if it gets overwritten by some code in the analyzer which has a bug. In such cases, it can happen that you see very strange behavior, including ODBEdit to refuse to start.

To solve the problem, the ODB has to be rebuild. For that purpose it is useful to have an ASCII image of the ODB. Usually this file is called init.odb. It is present in the standard analyzer directory. First remove the shared memory:

> rm ODB.SHM

and then reload the ODB from init.odb:

> odbedit
[local]/> load init.odb

When you do modifications to the ODB like adding new parameters or variables, you should update init.odb by issuing foolowing commands in ODBEdit:

[local]/> cd /             (to be sure that you are in the root dir)
[local]/> save init.odb

S. Ritt, 2 May 1997