frog is hosted by Hepforge, IPPP Durham

FROG

FROG Logo

Home

Tutorials

Download

UserManual

FAQ

SVN (deprecated)
Github

Configuration of FROG

You can edit the configuration file : config.txt and change : (remark : each line have to end by a semicolon ';' )

  • InputVisFile - the input file you want to read. Exemple:
    • "../test/MinBias.vis"
    • {http://www.fynu.ucl.ac.be/users/l.quertenmont/FROG/Vis_CMS/MinBias}
  • eventNumber - the event you want to display first
  • ScreenShotFormat - the format of the screenshot produced when pushing on ENTER. It can be ps, png, eps, tex, pdf, svg, pgf.
  • GeomToDisplay - the geometry that you want to display. It can be the :
    • Tracker (PIB,PIE,TIB,TID,TOB),
    • HCAL (HB, HE, HO, HF),
    • ECAL (EB,EE,ES),
    • Muon System (DT,CSC,RPC)
  • EventToDisplay - the information in the event that you want to display. It can be :
    • Sim tracks
    • Sim vertices
    • Sim Hits
    • ECAL Hits
    • HCAL Hits
    • Muon Hits
    • Tracker hits
    • Reco tracks
  • WaC_* - the width and color of the
  • updateVisFileTime - The time (in seconds) between two update of the .vis file (for DQM purposes). If this variable is negative, the .vis file will not be updated

It is also possible to define colors, widths, and energy threshold in the file : soft/Config/CMS_Colors.txt :

  • Id_********_Color -the colors (red, green, blue, alpha) (Default is opac black)
  • Id_********_Marker - the marker used to display hits, vertices,... These marker are defined in the directory : soft/Resources/Marker (Default is 0=square)
  • Id_********_MarkerSize - the size of the marker (Default is 1)
  • Id_********_Thikness - the thikness of the line, curve (tracks,...) displayed (Default is 1)
  • Id_********_PtMin - the minimum pt threshold on objects (simtracks) (Default is -1GeV)
  • Id_********_EMin - the minimum energy threshold on objects (clusters) (Default is -1GeV)

where the * have to be replace by the ID of the object you want to display. These ID are defined in the file : soft/Includes/FROG/FROG_DetId.h

Note1 : When more than one collection of the same kind of objects is produce, you have to set color of the new collections in soft/Config/CMS_Colors.txt , The Id of the first collection is the event Id of the object (e.g. 23100000 for a track/trajectory) + 1. The second collection is event Id of the object + 2, and so on. For example if you have 2 trajectory collections (traj1 , traj2) and 2 track collections (track1, track2).

You can set the colors, just by increasing the Id by 1 unit :

  • Id_23100000_Color = { 1.0 , 0.0 , 0.0 , 1.0 }; // All Tracks are red
  • Id_23100001_Color = { 1.0 , 1.0 , 0.0 , 1.0 }; // traj1 is yellow
  • Id_23100002_Color = { 0.0 , 0.0 , 1.0 , 1.0 }; // traj2 is blue
  • Id_23100003_Color = { 0.0 , 1.0 , 0.0 , 1.0 }; // track1 is green
  • Id_23100004_Color = { 1.0 , 1.0 , 1.0 , 1.0 }; // track2 is white

of course, you can use the same techniques for any other displayable collections, and also to set up the thickness the markers, etc...

Note2 : It is possible to set color for a very small subset of detector modules/cristals. You only need to know the detId of the subset. (You can find it by looking in the frog_anaylzer source code.) But it is always build in the same way. Let's doing an example with a tracker module :

  • 11000000 = Tracker DetId
  • 11000000 + A*100000 = TrackerSubDetId, So,
  • 11A00000 with A=1-->PIB, A=2-->PIE, A=3-->TIB, A=4-->TID, A=5-->TOB, A=6-->TEC (Let's Choose A=6 for the following)
  • 11600000 + B*10000 = TECSide DetId (B=1 is TEC-, B=2 is TEC+)
  • 11610000 + C*1000 = Wheel C of TEC-
  • 1161C000 + D*10 = Ring D of TEC- Wheel C.
  • 1161CDD0 + E = Petal E of Ring D of TEC- Wheel C.

The same idea is use for all the detectors, but of course, the meaning of the digit depend on the SubDetector (not the same in barel and endcap for exmaple) but you can find all the meaning in the frog_analyzer source code. Or try to discover them yourself, We tried to do it in the most logical way. Remember that you can change colors for every subset of detectors. It can sometimes be usefull to put all defected/wrong modules in red and all others in green for example. In order to get the full status of a detector part.

Keyboard shortcut and mouse

All keyboard shortcuts can be seen when you press F1.

It is also possible to click on the objects to get informations on it (Pt, chi2, E,...) (left button of the mouse).

When you click on a geometry it is possible to see the parent by clicking on 1, the grand-parent by clicking on 2,... (A parent is the collection which contains the clicked object).

Is is also possible to rotate around the detector with the mouse by moving and clicking on the right button of the mouse.

Is is also possible to do translation using the arrows anf pushing in the same time on CTRL.