Page History

...

• mpd = MeV per DAC

• thold.  = threholdsthresholds

These files are in $LATCalibRoot/CAL/CU06.

...

But if we're unavailable, then log on to noric (or whatever machine your rdb MySQL system is) and type rdbGUI-new.

There is documentation, see

http://www.slac.stanford.edu/exp/glast/ground/software/notes/rdbGui/rdbGui-use.shtml^{Image Added}

Older but still of some merit is the following.

http://www.slac.stanford.edu/exp/glast/ground/software/calibration/docs/mysqlDirect.shtml&nbsp^{Image Added};

Once you've mastered rdbGUI and you've added your file names to the metadata database, triple check your entries. It is very important that vstart be consistent with the data you want (re-)processed. If your calibrations are to supersede older calibrations, that is, render the old ones obsolete, then YOU MUST CHANGE THE PROC_LEVEL FROM PROD TO SUPSED for the old file names.

If you have spaces, typos, invisible characters in your file names, it will CRASH THE PIPELINE so when you update the rdb database, send e-mail to francesco.longo@ts.infn.it  focke@slac.stanford.edu   borgland@slac.stanford.edu

Okay, it won't actually crash the whole pipeline, just those jobs that look for non-existing calibration files, but warning the pipeline caretakers that you have made a change will help them be alert to why many jobs are suddenly failing...

How to find out which calibration constants were used ?

...