The Event Browser
The BaBar event Browser, developed by the Annecy
team (A.Bazan, D.Boutigny, Y. Karyotakis, T.Le
Flour, S.Lieunard & V. Tisserand) is a user friendly interactive
tool, for dumping BaBar events, in an organized and readable way.
Its main purpose is to help physicists to understand particular events,
the same way as an event display is doing.
Last Update September 27, 2000
Browser Features Running
the Browser How it works Installation
Current Status
Browser features
Event selection
-
Select a particular collection or a list of collections,
dump all events.
-
Select and dump events from a list. The collection
name and event stamps are needed.
-
Select events satisfying simple cuts on tag variables.
Ex. : number of tracks < 3, Emin ...
General event information and NanoDST
-
Event id (Run number, major, minor, date, time ...).
-
Event parameters (Beam parameters, primary vertex,
event shape, number of tracks ...).
-
Trigger information ( Level 1 and Level 3 ).
-
Bgfilter information ( isRadBhabha, isMultiHadron
...).
-
EventTagTools.
List selection for BtaCandidates in the Events
All available lists on MicroDST ( Candidates lists
: ChargedTracks, CalorNeutral, PID lists ...
).
Single Btacandidate information : any content available
in the Micro
-
Tracking
-
Calorimeter
-
IFR
-
PID Quality : dE/dx & DIRC
-
PID Information
Installation
To download the Babar Event Browser
client code, copy the single file to your own directory.
Downloading
the Client ( Unix, Windows 95 98 NT ) of the Event Browser
Then open a command window, go to the directory where you copied install.class,
and run the installer by typing:
java install
Running the Browser
From the event browser directory:
On UNIX, just type : chmod
u+x startEB.sh then startEB.sh.
On Window, NT : double click on startEB.bat
By default , the CES server connection is on shire01.slac.stanford.edu
,
port 5030. The server
name is : CES_BETA2.
Requirements
How it works
The package is based on Serge Du's ( LAL Orsay)
CesBase and CesBaseImp, packages. Event information is retrieved
via BetaCes
(Beta Corba Event Server) which accesses the
Objectivity dataBase. BetaCes communicates to a Java client (a Java application,not
yet a Java Applet) through a CORBA communication protocol. Both,
BetaCes, which is a Beta application and runs on UNIX side, and the
Java server running on the user's workstation ( PC, SUN etc...) have been
developed by the Annecy group.
Screen Shots and explanations
Current Status
Up to now, a server is running :
| DATABASES |
Computer |
Port |
Code Version |
Server Name |
| analboot2 |
shire01.slac.stanford.edu |
5000 |
>= 8.6.5e |
CES_BETA |
The
following features are available for the moment :
-
Connect a remote CORBA Event Service (CES) knowing
the name and the port of the remote host and the CES Server name.
-
Setup and configuration
-
Set a default dataBase collection name.
-
The default database name is in a file named <ServerName>.default
in the directory : /afs/slac.stanford.edu/g/babar/simu/bbsim/prod/collectionLists
-
Selected a given user collection list from users's
file.
-
This file could be anywhere in the AFS area.
-
Getting a collection list matching witth a given
pattern.
-
The full list of collections is in a file named
<ServerName>.collectionList
in the directory :
/afs/slac.stanford.edu/g/babar/simu/bbsim/prod/collectionLists
-
Choose the list(s) for single BtaCandidates information
in the event (GoodTracksLoose ...) .
-
Navigated through data collections
-
Next collection
-
Event access
-
Accessing to the next or the previous event.
-
Direct access to an event in the current collection with an ordinal value.
-
Direct access to an event in the current collection with the lower and
upper hexadecimal values.
-
Choose the list(s) for single BtaCandidates information
in the event (GoodTracksLoose ...) .
-
For each list select block of data (Tracking, PID,
Calorimeter...) to dump.
-
Dump selected data nicely formatted and show
the poor's man event display (magnitude, theta, phi views for each BtaCandidate).
Related talks
|
