Project

General

Profile

Paraview tips

Note that Adam's Geant-to-VTK tool can be found here: https://cdcvs.fnal.gov/redmine/projects/geanttovtk/wiki/Wiki

Select only decay muon

Test expression:

PN == "mu+" and PID == 1

E cut on particles

Test expression:

IKE > 500

which keeps only particles with E > 500 MeV

Only show trackers and calos in geometry

Only show detector region if the geometry is too slow for you (from Will):

Regular expression:

ModuleChamber|VacuumChamberCadMeshLV\[00\]|shortQuadLV\[00\]|VacuumChamberCadMeshLV\[06\]|shortQuadLV\[06\]|VacuumChamberCadMeshLV\[09\]|shortQuadLV\[09\]|station

Perfect Radius

Attached below is PerfectRadius.heprep.zip, open this up as you would load regular heprep formatted events and a track should load at 7112mm. Setting the colouring to Solid Colour, then editing it to be red with a Line Width of 5 (when in Wireframe representation) displays the magic radius nicely.

Simplified detector geometry

Will has made a simplified geometry that only shows trackers (+ vac chambers near them) and calos. If you are having trouble loading the full geometry (e.g. on laptops), you can use this instead.

The file is here: http://hep.ph.liv.ac.uk/~wturner/Files/TrackersAndCalos.zip

Unzip, and load the .vtm file.

Trouble-shooting

Different event trajectory attributes

The geant4 trajectory attributes are written to the event in the heprep file. When you use your own trajectory (as we are for the TrajectoryArtRecord), these attributes are used instead. Own own trajectory class should now provide the same info so this shouldn't make a different, but if you issues then run without trajectory saving using:

    TrackingAction : {
       name : "trackingAction" 
       StorePrimaryTrajectory           : false
       StorePrimaryDaughterTrajectories : false
       StoreOrphanTrajectories          : false
    }

If you see this problem let Tom know (I think it is fixed but let me know if not).

Errors when entering test expressions:

The following are known causes of getting an error message when entering a test expression:

  • A space or newline character at the end of your expression (often happens when copying from redmine)
  • Your test expression not matching any events

Draw 3D hit points from CSV file

1) Create a CSV file (at least x,y,z columns) with your hit positions
2) Open it in paraview
3) Open "Table to Points" filter
4) Select which column is for which axis
5) Click Apply
6) Close the table frame on the right
7) Click eye next to "TableToPoints1" in pipeline browser to unhide