proof

1. Introduction
2. Dataset definition
   1. Using a TFileCollection
   2. Using a TDSet
   3. Using a TChain
3. TProof::Process API
   1. Cycle-driven processing
   2. Data-driven processing
      1. Processing

PEAC is a set of tools to facilitate setting up a full featured analysis facility on set of machines or a multi-core machine.

Current PEAC documentation can be found at http://mon1.saske.sk/peac/doc/peac-main/ .

In this section we will have a first look at PROOF processing starting from simple generations of random numbers. Historically this is not the way all this was developed, but we think it is easier to understand the various components starting from this use case.

1. TSelector framework
2. Filling a 1D histogram with random numbers

1. TSelector framework

Each user gets a working area on each node of the cluster. This area is called sandbox. The default location on a local machine is $HOME/.proof (on PROOF-Lite $HOME/.proof/path-from-where-we-started). However, on eal clusters the administrator decides where the user sandboxes will be created. You can find out the location of the sandbox with Print().

1. The sandbox
2. The working directory

1. The sandbox

TProof is the interface class to the PROOF session. Everything done in the PROOF session is done using the methods of the TProof class.
TProof has many methods which we will encountered while trying to use PROOF. We start with two of them which allow to examine the session:

In this section we describe how to start a PROOF session in a few relevant cases:

1. Start a session in a PROOF-enabled facility
   1. Controlling the number of workers
2. Start a PROOF-Lite session
3. gProof

1. Start a session in a PROOF-enabled facility

We start with reminding the relevant terminology used in the PROOF context:

This page is meant to collect answers to frequently raised issues. By its nature this page will be in continuous evolution.

Starting with version 5.32/00 it is possible to easily create a PAR file to read the content of data stored into a ROOT file. This is done via TFile::MakeProject, exploiting the fact that ROOT files are self-describing and contain enough information to read what is stored. The method MakeProject of TFile has been augmented with the possibility to store the relevant information in form of a PAR file.