]>
Commit | Line | Data |
---|---|---|
0145e89a | 1 | // $Id$ |
2 | ||
3 | /*! \page README_mchview Tracker visualisation program | |
4 | ||
9016a84e | 5 | A visualisation program, \link mchview.cxx mchview \endlink, is now available to display, in two dimensions |
0145e89a | 6 | (3D visu being done within the EVE framework), the tracker chambers. |
7 | ||
8 | \section mchview_install Installing the program | |
9 | ||
9016a84e | 10 | \em mchview should be installed together with the rest of AliRoot. Two points should be noted though. |
11 | \em mchview is using two external files to run properly. One is a resource file $HOME/.mchviewrc, used | |
0145e89a | 12 | to "configure" the program and keep some history of the user interaction with it (e.g. the list of recent |
13 | data sources used). The other one is a Root file, padstore.root (default name, can be changed with the resource file), | |
14 | which contains lots of precomputed information (like the contours that are being displayed, the geometry transformations, | |
9016a84e | 15 | etc...). By default, \em mchview will look for this file in the current directory. If it's not there, it will |
0145e89a | 16 | ask if it's OK to create it. Be warned that this will take a while (but is only done once). |
9016a84e | 17 | If you install a new version of \em mchview, it is recommended to delete this file first, before lauching \em mchview again. |
0145e89a | 18 | |
19 | \section mchview_navigation Navigating the display | |
20 | ||
9016a84e | 21 | When starting \em mchview (and after the padstore.root file has been created for the first time), |
0145e89a | 22 | you'll be presented with two tabs. The first one allow to navigate within the detector, and the |
23 | second one to select data sources to be displayed. | |
24 | The first tab offers a global view of the 10 tracking chambers. On the right you'll see | |
25 | a color palette (used in the display of data sources, see later). On the top (from left to right) are | |
26 | navigation buttons (backward and forward), and radio buttons to select the kind of view you'd like : you can | |
27 | view things for a given cathode or for a given plane. Note that in some instances those buttons maybe inactive. | |
28 | On the bottom are three groups of radio buttons, labelled "responder", "outline" and "plot", followed by data source buttons (see later) : | |
29 | Each group will contain a number of buttons corresponding to different view levels of the detector (e.g. detection element, manu, buspatch, etc...). | |
9016a84e | 30 | In \em mchview jargon, what is displayed on screen is called a "painter". The meaning of responder, outline and plot is as follow : |
0145e89a | 31 | |
32 | - responder (only one selected at a time) is the type of painter that responds to mouse events. When you mouse over responder painters, they'll | |
33 | be highlighted (bold yellow line around them), and some information about them will be displayed in the top right corner. | |
34 | If you click on a responder painter, a new view will open to show only this painter. If you meta-click (button2 on a mouse, or alt-click on a Mac for instance) | |
35 | on a responder painter, a new view will open, showing the clicked painter and its "dual" (the other cathode or other plane, depending on how the first one | |
36 | was defined). | |
37 | ||
38 | - outline (multiple selection possible) indicates which painter(s) should be outlined. When starting the program, only manus are outlined, but you | |
39 | can outline the detection elements, the chambers, etc... | |
40 | ||
41 | - plot (see later about plotting and data sources) indicates at which level you want to see the data. | |
42 | ||
43 | On the bottom left is a group button used to select which data source should be displayed (empty until you select a data source, see next section). | |
44 | Next to it will be a list of buttons to select exactly what to plot from a data source (once you've selected a data source only). | |
45 | ||
46 | Note that whenever you click on a painter and get a new view, you get use the navigation buttons (top left) to go forward and backward, as in | |
9016a84e | 47 | a web browser for instance. Note also that the \em mchview menu bar contains a "History" menu where you can see (and pick a view) all the views that were opened. |
0145e89a | 48 | |
49 | Even before selecting something to plot, at this stage you could use the program to familiarize yourself with the detector structure (aka mapping). | |
50 | ||
51 | \section mchview_datasource Specifying the data source | |
52 | ||
9016a84e | 53 | The second tab of the \em mchview allows to select one or several data sources. |
0145e89a | 54 | Each data source, in turn, will provide one or more "things" to be plotted. |
55 | The number of "things" actually depends on the data source. | |
56 | For instance, a raw data source will allow to plot the mean and the sigma of the pad charges. | |
57 | ||
58 | Be warned that this part of the program is likely to evolve, as you'll for sure notice that the interface is quite crude for the moment. | |
59 | ||
60 | From top to bottom, you'll see group of frames used to : | |
61 | ||
62 | - select from a list of recently used source | |
63 | ||
64 | - select a raw data source (either by typing in its full pathname, or opening a file dialog). The second text field in this group is to specify the | |
65 | location of the OCDB to be used (if any). If that field is not empty (and the corresponding entry is correct, of course), the raw data will be calibrated. | |
66 | ||
67 | - select an OCDB data source (pedestals, gains, capacitances) | |
68 | ||
69 | In all the frames, once you've selected or entered the needed information, you'll click on the "Create data source" button, | |
70 | and a new data source line will appear in the bottom of that tab (and in also in the first tab, that data source will now | |
71 | be selectable for plotting). Each data source line indicates the short name of the data source, the full path, and a list of buttons to run, stop, rewind and | |
72 | remove. Run/Stop/Rewind is only selectable for data sources where the notion of event means something (e.g. for pedestals it won't). | |
73 | ||
9016a84e | 74 | Note that all the file paths can be local ones or alien ones, if you have a correctly installed alien, and you use a short wrapped to call the \em mchview program. |
0145e89a | 75 | For instance : |
9016a84e | 76 | <pre> |
0145e89a | 77 | alias mchl $HOME/mchview.alien |
9016a84e | 78 | </pre> |
0145e89a | 79 | |
80 | where mchview.alien is a little script : | |
9016a84e | 81 | <pre> |
0145e89a | 82 | #!/bin/sh |
0145e89a | 83 | test=`alien-token-info | grep -c expired` |
0145e89a | 84 | if [ $test -gt 0 ]; then |
85 | echo "Token expired. Getting a new token" | |
86 | alien-token-destroy | |
87 | alien-token-init | |
88 | elif [ ! -e /tmp/gclient_env_$UID ]; then | |
89 | echo "Getting a token" | |
90 | alien-token-init | |
91 | fi | |
0145e89a | 92 | if [ ! -e /tmp/gclient_env_$UID ]; then |
93 | echo "No token. Exiting" | |
94 | exit | |
95 | fi | |
0145e89a | 96 | source /tmp/gclient_env_$UID |
0145e89a | 97 | export alien_API_USER=youralienuserid # only needed if different from your local username |
0145e89a | 98 | mchview $* |
9016a84e | 99 | </pre> |
0145e89a | 100 | |
101 | --------- | |
102 | ||
103 | IMPORTANT WARNINGS | |
104 | ||
105 | The remove button is currently not working... | |
106 | ||
107 | In principle, you could have several raw data sources running at the same time. This is NOT currently working. You can have several data sources opened | |
108 | at the same time, but not running at the same time. (this has to do with AliRawReader not being thread-safe for the moment). | |
109 | ||
110 | Once you have one or more data sources added, you can go back to first tab and start looking at the data ;-) | |
111 | ||
9016a84e | 112 | This chapter is defined in the READMEmchview.txt file. |
113 | ||
0145e89a | 114 | */ |