|
||||||
|
|
|
|
|
||||||||||||||||||||||||||
wget http://www.slac.stanford.edu/~perl/HepRApp/HepRApp.jar
If you are on Mac or Windows (or some other systems that have automatic association of jar files with Java), just click on this file to start the application.
The first time you run HepRApp, it will
immediately open the "Select Group" menu.
This is where you can specify whether HepRApp should run with any
special settings
for known groups. Select BaBar.
You can also revisit this setting at any time from the Options menu.
The setting you make here, along with many other settings you make as
you work in HepRApp,
will be stored in a file called "user.properties" that will be created
in the directory
from which you ran HepRApp.
|
There is a single menu (the "View Menu") from which you can select and control all kinds of viewing aspects of the event display. To explore and use the menu, simply click your right mouse button anywhere in the view of the detector (see picture below).
As an example, you can rotate the detector by selecting the "Mouse Function" submenu and clicking the "Rotate" checkbox.
As an example, I've rotated the detector to an angled side-view.
If you can see it in HepRApp, you can disable it. The list of displayable components (both detector pieces and reconstructed information) is in the right-hand panel of the event display window.
Click on the sign to the left of "Detector Geometry" (depending on your operating system and selected Java look and feel, the sign will be either a little right arrow, or a circle with a line coming out of it, or a plus sign). This will open a tree of displayable elements for the detector model. For instance, you can draw every layer of the IFR RPCs if you so choose.
Clicking on the "Data EventURL" will display the tree of all reconstruction objects which are displayable in the detector view. For instance, the "InfoBox" is the event information text that appears in the bottom left corner. You can also see that, by default, a number of candidates from PID selector lists are displayed (if they are present in the event).
Among the data types shown in the "Data Visibility Tree" is the special data type, "Particles". This type can be configured to show any particle or candidate list (1) if the list is actually present in the Framework (i.e. the server knows to create the list using CompositionTools, etc. and (2) if there are candidates in that list in a given event.
You tell the server which lists you want available. Go to the "Options Menu" at the top of the screen and select "Server Property Control..."
A new window will appear, in which you can turn on various properties. Scroll down to where it says "Particles" on the left.
In the box to the right of "particles...lists", specify one or more lists (separated by commas), and then hit the enter key, for example,
GoodPhotonLoose,PidLHElectrons,piLHTight,KLHTight,muNNTight,GoodTracksLoose
When you hit the enter key, the value is transmitted to the server.
You can also use this Server Property Control to set various other properties. Once you have set all the properties you want, hit the reload button to reload the event from the server.
The data type "Particles" in the "Data Visiblity Tree" will now contain subtypes for each of the specified lists. For example:
You can then turn these individual lists on and off from the "Data Visibility Tree" just as you would any other data type.
Your specified properties will be retained for the rest of your server session. If you want to retain these properties for future sessions, use the "Save Settings" button at the bottom of the "Server Property Control." This will write your settings into your user.properties file.
You can turn on labels for objects. For instance, let's turn on the labels for the muNNTight candidates. To do this, go to the "Options Menu" at the top of the screen and select "Label Control...".
A new window will appear, in which you can turn on various labels (for energy, PID, momentum, etc.).
Scroll down until you find piLHTight, and then check "Name" and uncheck "short name". This will make for a cleaner label. The label control will now look like:
Click "Dismiss" in the "Label Control" window, and you should see a label has appeared next to the red tracks (pions).
You may find it useful to be able to cut out a class of objects from the event display. For instance, if you were studying radiative penguin processes and wanted to cut out all photons with energy less than 1.6 GeV, you could then isolate the primary photon from the penguin process. Here is an example of how to define such a cut.
To place a cut on the EmcClusters in the display, go to the "Options Menu" at the top of the screen and select "Cut Control...".
A new window will appear, inviting you to define cuts on the EmcClusters in the event. Here, I have chosen to isolate clusters with a minimum energy of 1.6 GeV.
Here is a before (left or top) and after (right or bottom) shot of the same event. In the after shot, you can see the cut is printed on the screen so you don't forget what is being applied to the event.
Cuts are preserved if you proceed to any other event or collection.
To export your event to such graphical formats, click on the "File" menu button at the top left of the event display window and select "Export Graphics...". A new window appears, in which you can select the filename, filetype, and set options for the file type (such a transparency/non-transparency for PNG files, etc.).
Select an output format by expanding the format list:
Once you have selected a format, you can then get format-specific options by clicking on the Options button.
The graphic below was generated from HepRApp as a PNG file with a black background (non-transparent).
Click on the "File" menu and select "Save as Local Data...". A window will appear and ask you to specify a filename. Let's call it "test.heprep" for now.
You can open the test.heprep file at any time by clicking on the yellow folder icon ("Open Data") and clicking the "Open HepRep File..." button in the Open Data window. Select your file and wait for it to load. You can then draw/disable the objects you do/don't wish to see.
Write a list of events to disk for later viewingYou can load a list of collections into HepRApp. You can then direct HepRApp to autoload each one and, using an option (autoSaveHepRep) to have it write the XML files for each event. Here is an example of actually doing this.
|
