Project

General

Profile

Using the Cosmic Tracker » History » Version 8

« Previous - Version 8/10 (diff) - Next » - Current version
Muhammad Elnimr, 09/09/2014 12:27 PM


Using the Cosmic Tracker

#######################

Some indespensible information:

#######################
(1) What is a Hit/Cluster/Spacepoint/Track/......?
Look for the private members here:
https://cdcvs.fnal.gov/redmine/projects/lardata/repository/revisions/develop/entry/RecoBase/Hit.h
and others
Cluster.h
Track.h
....

(2) Michelle's getting started:
~mstancar/getting_started_*

(3) Twiki tutorial:
https://cdcvs.fnal.gov/redmine/projects/lbnecode/wiki/_Tutorial_
(4) Hot fix: commit changes to quickly LArSoft before anybody notices (and
without being on a branch):
Make sure all your modifications work/ready/tested/compiles with
the latest larsoft.
Check out the latest larsoft.
Copy your stuff over.
Do git add
commit -m 'some text'
push

(5) ...

##########################

LArSoft v02_05_02 or higher is needed.

###########################

#####

Running the anatree and trkanact:

#####

Look at standard_reco_lbne35t.fcl for the module names and other stuff
to run anatree and trkanact.

What you find in the fcl that you need to uncomment:

{
cluster: @local::standard_fuzzycluster
spacepts: @local::standard_spacepts
ct: @local::standard_cosmictracker
}

{
anatree: @local::anatree_anatree
trkana: @local::standard_trackanact
}

reco: [caldata, hitcheat, cluster, spacepts, ct]
ana:  [anatree]
ana2: [trkana]
end_paths:     [ ana,ana2, stream1]

and then run like this:

lar -c standard_reco_lbne35t.fcl -s someGeneratedFile.root

TO-DO: Currently the tracks are not stitched, if you want to stitch them just
run the stitch module right after the cosmictracker.

#####

Working with the anatree branch:

####

Be careful the anatree has different "sets" of leafs, lets say ones
belonging to tracks and ones belonging to hits (may be third belonging
to clusters). Lets say you wanna draw the x coordinate of track
spacepoints (trkx) so you need to not draw the entries belonging to
hits (-999 entries) since the tree is filled with hits and tracks at
the same time and definitely there are more hits than tracks in any
given event.
So you just do:

treename->Draw("trkx","trkx>-9999");

because if you do just:

treename->Draw("trkx");

you get all the entries with -999 (think of it as a static array with
empty elements filled with this big negative number).

#####

Working with the trkana branch:

####
Inside this branch you will find all the histograms made using the TrackAnaCT module
(https://cdcvs.fnal.gov/redmine/projects/larreco/repository/revisions/develop/entry/TrackFinder/TrackAnaCT_module.cc)