Page History

...

Instead of the file above, if the user knows about it, he can provide the data code release with the variable SK_EXPECTED_RELEASE, and a set of directories where to search for the shared libraries, defined by SK_LIBRARY_DIRS (which has a default value relevant for SLAC site). The latter is a ':' set of directories paths. SK_EXPECTED_RELEASE should have the form <main_package>/<main_package>-<release>, as one can see in the example above. The exact names of the libraries for a given data type ar currently hardcoded, and described in the guide /Skimmer at SLAC/. For example, For each <dir> element in SK_LIBRARY_DIRS, and a given <main_package> and a given <release>, the skimmer will look for <dir>/<main_package>/<main_package>-<release>/lib/libcommonRootData.so.

...

If the events have been cut (thanks to SK_INPUT_EVENT_LIST or SK_TCUT) and SK_OUTPUT_CEL is defined, no deep copy of data will take place. Instead, the skimmer will create a ROOT CEL file which is giving the list of valid files and entries for each relevant data type. In this case, the pruning of branches will not be applied. The relevant data types are the ones which have a branch giving the run id and a branch giving the event id. For other data types, the usual merging of files will take place, even if SK_OUTPUT_CEL is defined, because the CEL format does not support yet such kind of data.

...