EventDisplays: Difference between revisions
No edit summary |
|||
(25 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
This page details past and present event displays and a geometry display. Sophie Middleton is co-ordinating the current Event Display effort, there are several forms of Event Display currently usable, each is described below: | |||
==Geometry Browser== | ==Geometry Browser== | ||
[[File:Geometry viewer.gif|thumb|500px|alt=Geometry Viewer|Example of Geometry Viewer.]] | [[File:Geometry viewer.gif|thumb|500px|alt=Geometry Viewer|Example of Geometry Viewer.]] | ||
This [ | This [[GeometryBrowserTutorial|system]] displays the geometry built as part of the geant model of the detector. It does not display events. It has options for cutaways, as seen in the example. It also has the option to make some volumes transparent. | ||
<br clear=all> | <br clear=all> | ||
== TEveEventDisplay == | |||
[[File:gui.png|thumb|500px|alt=Geometry Viewer|Example of TEveEventDisplay along with GUI.]] | |||
[[File:upstream2.png|thumb|500px|alt=Geometry Viewer|Example of PS and TS in TEveEventDisplay along with MCTrajectory (red).]] | |||
A detailed TEve based display specialized for Mu2e is available, details are found here: [https://mu2ewiki.fnal.gov/wiki/TEveEventDisplay]. Development began in 2020 and the display is now at an advanced stage, for more information, or to contribute, contact Sophie Middleton who is coordinating the current Event Display effort. | |||
== Eve-7 Event Display == | |||
Eve-7 is an upgrade to the well-known TEve ROOT-based Event Display. An Eve-7 based Event Display specifically for Mu2e is available, details are found here: [https://mu2ewiki.fnal.gov/wiki/Eve7EventDisplay]. Development began in 2021, for more information, or to contribute, contact Sophie Middleton who is coordinating the current Event Display effort. | |||
==EventDisplay== | ==EventDisplay== | ||
[[File:EventDisplay.gif|thumb|500px|alt=EvenDisplay|Example of the EventDisplay display.]] | [[File:EventDisplay.gif|thumb|500px|alt=EvenDisplay|Example of the EventDisplay display.]] | ||
A display system from Ralf Ehrlich. Run from a module: | A display system from Ralf Ehrlich. Run from a module: | ||
mu2e -c EventDisplay/ | mu2e -c EventDisplay/fcl/EventDisplay.fcl -s .. | ||
Controls are in the display and quite intuitive. See also [https://mu2e-docdb.fnal.gov:440/cgi-bin/ShowDocument?docid=7905 doc-7905] and [https://mu2e-docdb.fnal.gov:440/cgi-bin/ShowDocument?docid=2371 doc-2371] | Controls are in the display and quite intuitive. See also [https://mu2e-docdb.fnal.gov:440/cgi-bin/ShowDocument?docid=7905 doc-7905] and [https://mu2e-docdb.fnal.gov:440/cgi-bin/ShowDocument?docid=2371 doc-2371] | ||
Line 42: | Line 54: | ||
=== | ===Navigate inside the event=== | ||
[[File:Stntuple-2D-print.png |thumb|500px|alt=Stntuple 2-D event display|Example of printout.]] | [[File:Stntuple-2D-print.png |thumb|500px|alt=Stntuple 2-D event display|Example of printout.]] | ||
This event display allows to inspect all the collection of reconstructed objects given in the Event. <code>MuHitDisplay</code> is run in interpreted mode within ROOT. To print all the informations we need we use the Class <code>TAnaDump</code>. An example of working flow follows: | This event display allows to inspect all the collection of reconstructed objects given in the Event. <code>MuHitDisplay</code> is run in interpreted mode within ROOT. To print all the informations we need we use the Class <code>Stntuple/mod/TAnaDump.cc</code> . An example of working flow follows: | ||
* <code>d=TAnaDump::Instance()</code>: this command instantiate a pointer to a TAnaDump object | * <code>d=TAnaDump::Instance()</code>: this command instantiate a pointer to a TAnaDump object | ||
* <code>d->print...</code>: now the user is ready to print out all the collection he wants! The only arguments necessary to use the <code>print...</code> functions are the name of the module instances. | * <code>d->print...</code>: now the user is ready to print out all the collection he wants! The only arguments necessary to use the <code>print...</code> functions are the name of the module instances. | ||
=== Stntuple 2-D=== | |||
=== | |||
To run this event display the user needs to add the instance of the <code>MuHitDisplay</code> in the <code>fcl</code> file in the <code>physics.filters</code> block and execute it in the end of the <code>trigger_path</code>. On the <code>Stntuple/fcl/prolog.fcl</code> an example of <code>MuHitDisplay</code> instance block is available. | To run this event display the user needs to add the instance of the <code>MuHitDisplay</code> in the <code>fcl</code> file in the <code>physics.filters</code> block and execute it in the end of the <code>trigger_path</code>. On the <code>Stntuple/fcl/prolog.fcl</code> an example of <code>MuHitDisplay</code> instance block is available. | ||
Line 58: | Line 68: | ||
<br clear=all> | <br clear=all> | ||
== | ==Old TEve Displays== | ||
[[File: | [[File:TEveMuratStntuple.png|thumb|500px|Example of an TEve display.]] | ||
Pasha Murat is working on a display based on TEve package (2017). | Pasha Murat has a working geometry display based on gdml and the Stntuple package. | ||
[https://sites.google.com/view/stntuple/stntuple-howtos/how-to-display-mu2e-geometry Stntuple directions] | |||
Pasha Murat is also working on a display for art file based on TEve package (2017). | |||
<br clear=all> | |||
==geant4 qt Event Display== | |||
[[File:Geant4QtExample.png|thumb|500px|Example of a geant4 qt display.]] | |||
Best document is a Krzysztof Genser's talk here: | |||
[https://mu2e-docdb.fnal.gov/cgi-bin/sso/ShowDocument?docid=3680 doc 3680]. | |||
This rather powerful tool is setup to mainly show the details of geometry and possibly tracks of one event, but not any reconstructed quantities. | |||
You must a build a personal version of Offline, and use the g4vis=qt g4mt=off trigger=off buildopts settings: | |||
<br /> | |||
<code> ./buildopts --g4vis=qt --g4mt=off --trigger=off</code> | |||
[[Category:Computing]] | |||
[[Category:Code]] |
Latest revision as of 22:07, 18 June 2021
This page details past and present event displays and a geometry display. Sophie Middleton is co-ordinating the current Event Display effort, there are several forms of Event Display currently usable, each is described below:
Geometry Browser
This system displays the geometry built as part of the geant model of the detector. It does not display events. It has options for cutaways, as seen in the example. It also has the option to make some volumes transparent.
TEveEventDisplay
A detailed TEve based display specialized for Mu2e is available, details are found here: [1]. Development began in 2020 and the display is now at an advanced stage, for more information, or to contribute, contact Sophie Middleton who is coordinating the current Event Display effort.
Eve-7 Event Display
Eve-7 is an upgrade to the well-known TEve ROOT-based Event Display. An Eve-7 based Event Display specifically for Mu2e is available, details are found here: [2]. Development began in 2021, for more information, or to contribute, contact Sophie Middleton who is coordinating the current Event Display effort.
EventDisplay
A display system from Ralf Ehrlich. Run from a module:
mu2e -c EventDisplay/fcl/EventDisplay.fcl -s ..
Controls are in the display and quite intuitive. See also doc-7905 and doc-2371
Stntuple 2-D
The Stntuple ntuple package includes also a module named MuHitDisplay
that provides an interactive 2D event display. By default, the module pops up a canvas with the Tracker X-Y and calorimeter views where are displayed:
- the reconstructed straw hits: black crosses
- the calorimeter clusters: red/magenta circles (red for those on the disk closer to the tracker) where the size is proportional to the reconstructed energy
- reconstructed tracks: blu line
In addition to that, the module prints put the information of the reconstructed tracks.
An additional controller canvas allows to exploit additional views of the detectors:
- Tracker: XY transverse and R-Z longitudinal
- Calorimeter XY
- Cosmic Ray Veto
The calorimeter and the tracker views allow the user to select a specific "Time Cluster" that was reconstructed in the event to seed the track search.
Tracker XY and RZ views
The two sets of event projection for the tracker (X-Y and R-Z) provide a complete representation of the reconstructed tracks within a given event. Both canvas allow to zoom specific region inside the canvas. The RZ view include also
Calorimeter XY view
The calorimeter XY view includes both disks. Each crystal is colored with a red-yellow proportional to the energy reconstructed. The right button of the cursor allows to inspect the crystal-hit information and have them printed in the Terminal.
This event display allows to inspect all the collection of reconstructed objects given in the Event. MuHitDisplay
is run in interpreted mode within ROOT. To print all the informations we need we use the Class Stntuple/mod/TAnaDump.cc
. An example of working flow follows:
d=TAnaDump::Instance()
: this command instantiate a pointer to a TAnaDump objectd->print...
: now the user is ready to print out all the collection he wants! The only arguments necessary to use theprint...
functions are the name of the module instances.
Stntuple 2-D
To run this event display the user needs to add the instance of the MuHitDisplay
in the fcl
file in the physics.filters
block and execute it in the end of the trigger_path
. On the Stntuple/fcl/prolog.fcl
an example of MuHitDisplay
instance block is available.
This package is maintained by P. Murat and G. Pezzullo.
From Pasha Murat and Giani Pezzullo as part of the Stntuple ntuple package.
Good for detailed examination of tracks and hits. See also doc-13916.
Old TEve Displays
Pasha Murat has a working geometry display based on gdml and the Stntuple package. Stntuple directions
Pasha Murat is also working on a display for art file based on TEve package (2017).
geant4 qt Event Display
Best document is a Krzysztof Genser's talk here: doc 3680.
This rather powerful tool is setup to mainly show the details of geometry and possibly tracks of one event, but not any reconstructed quantities.
You must a build a personal version of Offline, and use the g4vis=qt g4mt=off trigger=off buildopts settings:
./buildopts --g4vis=qt --g4mt=off --trigger=off