Page History
| Warning | ||
|---|---|---|
| ||
The tool has been generalized and externalized. The last releases of source code, documentation and pending issues are now available at the new TRAC server. The specific issues and features for FERMI are in the documentation guide called TSkim for FERMI, which should be more complete than information below. |
Use of the skimmer on Noric machines
...
| No Format |
|---|
/afs/slac/g/glast/ground/GLAST_EXT/$CMTCONFIG/5.10.00/root /afs/slac/g/glast/ground/GLAST_EXT/$CMTCONFIG/5.14.00g/root /afs/slac/g/glast/ground/GLAST_EXT/$CMTCONFIG/5.16.00-gl1/root /afs/slac/g/glast/ground/GLAST_EXT/$CMTCONFIG/5.18.0000c-gl1/root |
For simple kinds of data, such as merit tuples, using a different recent ROOT release should be ok.
If $ROOTSYS is not defined, the skimmer will search for $GLAST_EXT/ROOT/v5.1014.0000g/root. If $GLAST_EXT is not defined, it will be set to /afs/slac/g/glast/ground/GLAST_EXT/$CMTCONFIG. If $CMTCONFIG is not defined, it will be set to rh9_gcc32.
...
| No Format |
|---|
/afs/slac/g/glast/ground/DataServer/v5r10v6r1/bin/skimmer |
Of course, it is more confortable to define an alias for it in your Unix account setup files, or add the DataServer bin directory to the Unix PATH :
...
The kinds of trees which can be skimmed is currently hardcoded, and especially targetted to GLAST needs. For each of those tree, we expect a top main branch. Actually, we distinguish two sets of trees : the ones which only rely on predefined ROOT types and have a single level of branches under the main one (the tuple-like trees), and the others. The latter typically requires the loading of a dedicated data description library before the concrete skimming takes place. The last release v5r10 v7r0 should understand the following types :
...