SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

Every time you enter in your machine, you have to setup the SHOE environment doing.

cd shoe/build
source setupFOOT.sh

Running the code using the executables

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

DecodedMC.root
DecodeMC_histo.root

The KalmanFilter tracking info are plotter in the results folder as .root and .png files.

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

Every time you enter in your machine, you have to setup the SHOE environment doing:

# starting from where you installed the software
cd shoe
source setupFOOT.sh
source /opt/rh/devtoolset-6/enable; source  /opt/exp_software/foot/root4foot.sh

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. GenFit compile
2. SHOE libraries compilation;
3. Level0 compilation;

GenFit compile

Setup the environment and go to the folder

source /opt/rh/devtoolset-6/enable; source  /opt/exp_software/foot/root4foot.sh

cd $FOOTMAIN/libs/GenFit

and follow the instructions in the file README.build

SHOE libraries compilation

Go to the SHOE libraries folder

cd $FOOTMAIN
source setupFOOT.sh
source /opt/rh/devtoolset-6/enable; source  /opt/exp_software/foot/root4foot.sh

make -j8

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

Level0 compilation and run

Go to the level0 folder and compile the code using the command:

cd $FOOTLEVEL0
make DecodeMC -j8

This will produce as output the DecodeMC executable. You can run it by doing:

./DecodeMC -in MCinputFile.root

Before running, have a look at the global parameters defined in the global configuration file:

nano $FOOTCONFIG/FootGlobal.par

(exit with ctrl-x).

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The SHOE-reconstuction code stores the information in an ntuple file and in ah histogram file:

DecodedMC.root
DecodeMC_histo.root

The KalmanFilter tracking info are plotter in the results folder as .root and .png files.

The reconstruction of data events

Still a long way to go...

Alessio Sarti - 2016-07-06

Schiccio Frank - 2017-07-03

Comments

<--/commentPlugin-->

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

Every time you enter in your machine, you have to setup the SHOE environment doing:

# starting from where you installed the software
cd shoe

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. GenFit compile
2. SHOE libraries compilation;
3. Level0 compilation;

GenFit compile

SHOE libraries compilation

Go to the SHOE libraries folder

Level0 compilation and run

Go to the level0 folder and compile the code using the command:

cd $FOOTLEVEL0

./DecodeMC -in MCinputFile.root

Before running, have a look at the global parameters defined in the global configuration file:

nano $FOOTCONFIG/FootGlobal.par

(exit with ctrl-x).

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The SHOE-reconstuction code stores the information in an ntuple file and in ah histogram file:

DecodedMC.root
DecodeMC_histo.root

The KalmanFilter tracking info are plotter in the results folder as .root and .png files.

The reconstruction of data events

Still a long way to go...

Developer instructions

Anyone who wants to develop its own part of the code and wants to add it back on a second time, should please follows the instrctions below:

1. Contact the code managers.
2. Download (git clone) of update (git pull) to the latest version of the code (master branch).
3. Create your new branch (git checkout -b branchName).
4. Work on your branch and commit regularly.
5. When your task is done and you wants to merge back to the main (master) branch, contact the code managers (or make a merge request on baltig page).

You can find more information in the following slides done at the SHOE tutorial in Bologna on 7-8th March 2018: Reconsturction slides & Ntuple descrition slides
I recall you can find the exercises solution in in the git branch "xxx02", to be compared with the tutorial stable branch "tutorial01".

-- Alessio Sarti - 2016-07-06 -- Schiccio Frank - 2017-07-03

Comments

<--/commentPlugin-->

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

Every time you enter in your machine, you have to setup the SHOE environment doing:

# starting from where you installed the software
cd shoe
source setupFOOT.sh

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. GenFit compile
2. SHOE libraries compilation;
3. Level0 compilation;

GenFit compile

Go to the folder

cd $FOOTMAIN/libs/GenFit

and follow the instructions in the file README.build

SHOE libraries compilation

Go to the SHOE libraries folder

cd $FOOTREF

and compile

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

Level0 compilation and run

Go to the level0 folder and compile the code using the command:

cd $FOOTLEVEL0
make DecodeMC

This will produce as output the DecodeMC executable. You can run it by doing:

./DecodeMC -in MCinputFile.root

Before running, have a look at the global parameters defined in the global configuration file:

nano $FOOTCONFIG/FootGlobal.par

(exit with ctrl-x).

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The SHOE-reconstuction code stores the information in an ntuple file and in ah histogram file:

DecodedMC.root
DecodeMC_histo.root

The KalmanFilter tracking info are plotter in the results folder as .root and .png files.

The reconstruction of data events

Still a long way to go...

1. Contact the code managers.
2. Download (git clone) of update (git pull) to the latest version of the code (master branch).
3. Create your new branch (git checkout -b branchName).
4. Work on your branch and commit regularly.
5. When your task is done and you wants to merge back to the main (master) branch, contact the code managers (or make a merge request on baltig page).

You can find more information in the following slides done at the SHOE tutorial in Bologna on 7-8th March 2018: Reconsturction slides & Ntuple descrition slides
I recall you can find the exercises solution in in the git branch "xxx02", to be compared with the tutorial stable branch "tutorial01".

Comments

<--/commentPlugin-->

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

Every time you enter in your machine, you have to setup the SHOE environment doing:

# starting from where you installed the software
cd shoe
source setupFOOT.sh

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. GenFit compile
2. SHOE libraries compilation;
3. Level0 compilation;

GenFit compile

Go to the folder

cd $FOOTMAIN/libs/GenFit

and follow the instructions in the file README.build

SHOE libraries compilation

Go to the SHOE libraries folder

cd $FOOTREF

and compile

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

Level0 compilation and run

Go to the level0 folder and compile the code using the command:

cd $FOOTLEVEL0
make DecodeMC

This will produce as output the DecodeMC executable. You can run it by doing:

./DecodeMC -in MCinputFile.root

Before running, have a look at the global parameters defined in the global configuration file:

nano $FOOTCONFIG/FootGlobal.par

(exit with ctrl-x).

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The SHOE-reconstuction code stores the information in an ntuple file and in ah histogram file:

DecodedMC.root
DecodeMC_histo.root

The KalmanFilter tracking info are plotter in the results folder as .root and .png files.

The reconstruction of data events

Still a long way to go...

-- Alessio Sarti - 2016-07-06 -- Schiccio Frank - 2017-07-03

Developer instructions

Anyone who wants to develop its own part of the code and wants to add it back on a second time, should please follows the instrctions below:

1. Contact the code managers.
2. Download (git clone) of update (git pull) to the latest version of the code (master branch).
3. Create your new branch (git checkout -b branchName).
4. Work on your branch and commit regularly.
5. When your task is done and you wants to merge back to the main (master) branch, contact the code managers (or make a merge request on baltig page).

Comments

<--/commentPlugin-->

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

Every time you enter in your machine, you have to setup the SHOE environment doing:

# starting from where you installed the software
cd shoe
source setupFOOT.sh

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. GenFit compile
2. SHOE libraries compilation;
3. Level0 compilation;

GenFit compile

Go to the folder

cd $FOOTMAIN/libs/GenFit

and follow the instructions in the file README.build

SHOE libraries compilation

Go to the SHOE libraries folder

cd $FOOTREF

and compile

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

Level0 compilation and run

Go to the level0 folder and compile the code using the command:

cd $FOOTLEVEL0
make DecodeMC

This will produce as output the DecodeMC executable. You can run it by doing:

./DecodeMC -in MCinputFile.root

Before running, have a look at the global parameters defined in the global configuration file:

nano $FOOTCONFIG/FootGlobal.par

(exit with ctrl-x).

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The SHOE-reconstuction code stores the information in an ntuple file and in ah histogram file:

DecodedMC.root
DecodeMC_histo.root

The KalmanFilter tracking info are plotter in the results folder as .root and .png files.

The reconstruction of data events

Still a long way to go...

-- Alessio Sarti - 2016-07-06 -- Schiccio Frank - 2017-07-03

Developer instructions

Anyone who wants to develop its own part of the code and wants to add it back on a second time, should please follows the instrctions below:

1. Contact the code managers.
2. Download (git clone) of update (git pull) to the latest version of the code (master branch).
3. Create your new branch (git checkout -b branchName).
4. Work on your branch and commit regularly.
5. When your task is done and you wants to merge back to the main (master) branch, contact the code managers (or make a merge request on baltig page).

Comments

<--/commentPlugin-->

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

Every time you enter in your machine, you have to setup the SHOE environment doing:

# starting from where you installed the software
cd shoe
source setupFOOT.sh

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. GenFit compile
2. SHOE libraries compilation;
3. Level0 compilation;

GenFit compile

Go to the folder

SHOE libraries compilation

Go to the SHOE libraries folder

cd $FOOTREF

and compile

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

Level0 compilation and run

Go to the level0 folder and compile the code using the command:

cd $FOOTLEVEL0
make DecodeMC

This will produce as output the DecodeMC executable. You can run it by doing:

./DecodeMC -in MCinputFile.root

Before running, have a look at the global parameters defined in the global configuration file:

nano $FOOTCONFIG/FootGlobal.par

(exit with ctrl-x).

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The SHOE-reconstuction code stores the information in an ntuple file and in ah histogram file:

DecodedMC.root
DecodeMC_histo.root

The KalmanFilter tracking info are plotter in the results folder as .root and .png files.

The reconstruction of data events

Still a long way to go...

-- Alessio Sarti - 2016-07-06 -- Schiccio Frank - 2017-07-03

Developer instructions

Anyone who wants to develop its own part of the code and wants to add it back on a second time, should please follows the instrctions below:

1. Contact the code managers.
2. Download (git clone) of update (git pull) to the latest version of the code (master branch).
3. Create your new branch (git checkout -b branchName).
4. Work on your branch and commit regularly.
5. When your task is done and you wants to merge back to the main (master) branch, contact the code managers (or make a merge request on baltig page).

Comments

<--/commentPlugin-->

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. GenFit compile
2. SHOE libraries compilation;
3. Level0 compilation;

GenFit compile

Go to the folder

SHOE libraries compilation

Level0 compilation and run

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The reconstruction of data events

Still a long way to go...

-- Alessio Sarti - 2016-07-06 -- Schiccio Frank - 2017-07-03

Developer instructions

Anyone who wants to develop its own part of the code and wants to add it back on a second time, should please follows the instrctions below:

1. Contact the code managers.
2. Download (git clone) of update (git pull) to the latest version of the code (master branch).
3. Create your new branch (git checkout -b branchName).
4. Work on your branch and commit regularly.
5. When your task is done and you wants to merge back to the main (master) branch, contact the code managers (or make a merge request on baltig page).

Comments

<--/commentPlugin-->

SHOE Reconstruction software (of the FOOT experiment)

Architecture of the SHOE-Reconstuction code

The part of SHOE dedicated to the event reconstracion is divided in 3 parts:

1. Libraries of general interest, containing the main classes used by the reconstruction (and in part by the generation) code. The GenFit external libraries are also here.
2. Level0 reconstruction code that is in charge of the interpretation of both MC and acquired data, digitization, alignment and clustering of the events and the track reconstruction.
3. HighLevel reconstruction that is in charge of the fragment identification and of the cross section measurement.

A breaf scheme of SHOE-reco follows.

Running SHOE

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Environment setup

SHOE compilation and run

The software compilatin proceeds in 2 steps:

1. SHOE libraries compilation;
2. Level0 compilation;

SHOE libraries compilation

Level0 compilation and run

Input Files

You can find the available MC samples lsted and described here. They are stored in the Bologna-tier3 site under: /home/FOOT-T3/battistfoott3/SimulatedData.

The current version of SHOE supports V12.4 simulated samples.

Output Files

The reconstruction of data events

Still a long way to go...

-- Alessio Sarti - 2016-07-06 -- Schiccio Frank - 2017-07-03

Comments

<--/commentPlugin-->

The reconstruction of data events

Comments

<--/commentPlugin-->

Twiki page of the FOOT reconstruction software

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Once the code has been downloaded the installation of the reconstruction software proceeds in two steps:

1. Framework libraries compilation
2. Reconstruction code compilation

Framework compilation

The framewoek libraries are kept inside the libs folder

source myLogin.sh

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

The reconstruction of MC simulation events

The MC simulation events production is documented in the simulation page. Once the events have been produced and a root file is available using the decoding tool (as explained in the simulation page) you can run the reconstruction algorithms that are performing the analysis of the MC information.

The software is kept inside the Reconstruction folder.

In a similar way to what is done for the data events we have organized the reconstruction of simulation events in two steps: level0 and fullrec levels.

L0 reconstruction

The code is kept under the level0 folder.

source myLogin.sh

and then compile the code using the command:

make DecodeMC

This will produce as output the DecodeMC executable.

The reconstruction of data events

The

-- Alessio Sarti - 2016-07-06

Comments

<--/commentPlugin-->

Twiki page of the FOOT reconstruction software

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Once the code has been downloaded the installation of the reconstruction software proceeds in two steps:

1. Framework libraries compilation
2. Reconstruction code compilation

Framework compilation

The framewoek libraries are kept inside the libs folder

To setup the environment variables you have to source the myLogin.sh(csh) scripts.

source myLogin.sh

Then you can compile the code from the libs/src directory issuing the make command

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

The reconstruction of MC simulation events

The MC simulation events production is documented in the simulation page. Once the events have been produced and a root file is available using the decoding tool (as explained in the simulation page) you can run the reconstruction algorithms that are performing the analysis of the MC information.

The software is kept inside the Reconstruction folder.

In a similar way to what is done for the data events we have organized the reconstruction of simulation events in two steps: level0 and fullrec levels.

L0 reconstruction

The code is kept under the level0 folder.

make DecodeMC

This will produce as output the DecodeMC executable.

The reconstruction of data events

The

-- Alessio Sarti - 2016-07-06

Comments

Twiki page of the FOOT reconstruction software

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Once the code has been downloaded the installation of the reconstruction software proceeds in two steps:

1. Framework libraries compilation
2. Reconstruction code compilation

Framework compilation

The framewoek libraries are kept inside the libs folder

To setup the environment variables you have to source the myLogin.sh(csh) scripts.

source myLogin.sh

Then you can compile the code from the libs/src directory issuing the make command

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

Alessio Sarti - 2016-07-06

Comments

<--/commentPlugin-->

Twiki page of the FOOT reconstruction software

Getting the code

The instructions on how to get the code can be found in the sotfware page.

Once the code has been downloaded the installation of the reconstruction software proceeds in two steps:

1. Framework libraries compilation
2. Reconstruction code compilation

Framework compilation

The framewoek libraries are kept inside the libs folder

To setup the environment variables you have to source the myLogin.sh(csh) scripts.

source myLogin.sh

Then you can compile the code from the libs/src directory issuing the make command

make

Then you can check out that the libraries are properly compiled and placed inside the libs/lib folder.

-- Alessio Sarti - 2016-07-06

Comments

<--/commentPlugin-->