Abstract
There are essentially three tools for the online monitoring of the data:
- the online monitor tool
- the online analysis tool
- GOSED (event display developed by R. Claus and the onlien group)
This page describes the Ntuple structure on the Online Monitor. These are standard HippoDraw Ntuple (or circular buffer): we can manipulate the entries only using standard HippoDraw rules.
The aim of this page is to show the information available to the shifter. Some of this variables are already plotted in the Online Monitor GUI.
The philosophy is to use a single Ntuple (the Main Ntuple) every time is possible to associate a single row with an event. In some cases more than a row per event is needed, i.e. when we want to put a row per hit strip. For this cases there is a special Ntuple for every subsystem.
- 3 Calorimeter Ntuples
- 3 Tracker Ntuples (the one for tem1 is of course empty)
- 8 Tagger Layer Ntuple
There are two visualization tool ready for the shifters (both can use realtime data and ldf files):
- Online Monitor: a simple canvas with standard plots organized in tabs.
- Onine Analysis: a standard HippoDraw canvas when all plot can be added using the Inspector
Online monitor
The online monitor should be the standard tool during the shifts under normal conditions. It comes with a pre-defined set of plots which are organized in several different pages/tabs. It can be configured quite simply, though it may be not trivial for the normal user.
Online analysis
It is essentially a Hippodraw canvas which knowsall the ntuple variables created by the monitor. The user can either open it and create his own plots from the inspector or load a text configuration file, which is trivial to create (even Carmelo can do it). The list of variables which are available for the online analysis is below.
Main Ntuple:
In this Ntuple there is one row for one events.
Variable name |
description |
|---|---|
lat_evt_timestamp |
timestamp of the event, caculated using GEM counters (sec) |
lat_evt_delta_time |
time difference between two consecutive events, calculated unsig GEM counters (sec) |
lat_ancillary_delta_time |
time difference between two consecutive events, calculated using AD counters (sec) |
lat_timestamps_difference |
lat_evt_delta_time - lat_ancillary_delta_time (sec) |
|
|
gem_trigger_condition |
GEM condition summary word remapped to the following values: ext=0, tkr=1, cal_le=2, cal_he=3, ext+tkr=4, ext+cal_le=5, ext+tkr+cal_le=6. |
gem_tkr_trigger_timing |
Arrival time of tkr trigger condition within the trigger window (clk ticks) |
gem_cal_le_trigger_timing |
Arrival time of cal_le trigger condition within the trigger window (clk ticks) |
gem_cal_he_trigger_timing |
Arrival time of cal_he trigger condition within the trigger window (clk ticks) |
gem_ext_trigger_timing |
Arrival time of ext trigger condition within the trigger window (clk ticks) |
lat_evt_energy |
Total raw energy in the calorimeters (MeV) |
lat_evt_theta_xz |
reconstructed event angle in the XZ plane (deg) |
lat_evt_theta_yz |
reconstructed event angle in the YZ plane (deg) |
lat_evt_impact_point_tkr_x |
reconstructed event impact point on top tracker layer, x coordinate (mm) |
lat_evt_impact_point_tkr_y |
reconstructed event impact point on top tracker layer, y coordinate (mm) |
lat_evt_impact_point_cal_x |
reconstructed event impact point on top of the cal, x coordinate (mm) |
lat_evt_impact_point_cal_y |
reconstructed event impact point on top of the cal, y coordinate (mm) |
lat_evt_top_tkr_x_hi |
hit position on top tracker layer x |
lat_evt_top_tkr_y_hit |
hit position on top tracker layer x |
lat_evt_tkr_top_num_hits |
number of hits summed over the top tracker layers |
|
|
temX-tkr_strip_count |
Number of strips per event in the tracker of tower X |
temX-cal_log_count |
Number of logs per event in the calorimeter of tower X |
temX-cal_energy |
Total raw energy in the calorimeter of tower X (MeV) |
acd-tileXX_pulse_height |
Pulse height in the ACD tile XX (adc counts) |
acd-tileXX_veto_pulse_heigh |
Pulse height in the ACD tile XX , when the veto signal is ON (adc counts) |
|
|
tagger_tag_momentum |
Particle momentum as measured by the tagger (GeV) |
lat_tag_gamma_energy |
Photon evergy, defined as BEAM_ENERGY - tagger_tag_momentum (MeV) |
tagger_total_beam_energ |
Total beam energy: tagger_tag_momentum + lat_evt_energy (MeV) |
tagger_tag_cu_momentum |
Particle momentum measured using the tagger module 0-1 and the CU |
|
|
tagger_beam_angle_x |
Beam angle, measured using tagger module 0-1, in the XZ plane (rad) |
tagger_beam_angle_y |
Beam angle, measured using tagger module 0-1, in the YZ plane (rad) |
|
|
tagger_cu_projected_beam_x |
Beam impact point on CU top tracker layer, measured using tagger module 0-1, x coordinate (mm) |
tagger_cu_projected_beam_y |
Beam impact point on CU top tracker layer, measured using tagger module 0-1, y coordinate (mm) |
tagger_cu_projected_beam_residual_x |
Difference between lat_evt_impact_point_tkr_x (traslated in the absolute reference frame) and tagger_cu_projected_beam_x (mm) |
tagger_cu_projected_beam_residual_y |
Difference between lat_evt_impact_point_tkr_y (traslated in the absolute reference frame) and tagger_cu_projected_beam_y (mm) |
|
|
tagger-modX_Number_of_Clusters_X |
Number of cluster on the x Layer of Tagger Module X |
tagger-modX_Number_of_Clusters_Y |
Number of cluster on the y Layer of Tagger Module X |
tagger-modX_Impact_Point_X |
Beam impact point on the x Layer of Tagger Module X (defined as the position of the cluster with max pulse height) |
tagger-modX_Impact_Point_Y |
Beam impact point on the y Layer of Tagger Module X (defined as the position of the cluster with max pulse height) |
tagger-modX_n_hits |
Number of readout strips of Tagger Module X |
|
|
tagger_X_int |
|
tagger_residual_x2 |
|
tagger_residual_x3 |
|
Calorimeter Ntuple:
In this Ntuple there is one row for one log in the data stream, and it's used to plot the beam profile inside the calorimeter
Variable name |
description |
|---|---|
View |
Layer view coded with a number: 'X'= 0, 'Y'= 1 |
Layer_Number |
Layer number (remapped as to show the top layer in the upper part of the plots) |
Log |
Log number |
Tracker Ntuple:
In this Ntuple there is one row for one strip in the data stream, and it's used to plot the beam profile inside the tracker.
Variable name |
description |
|---|---|
View |
Layer view coded with a number: 'X'= 0, 'Y'= 1 |
Layer_Number |
Layer number |
Strip |
Strip number |
Tagger Ntuple:
In this ntuple there is one row per spill, and is used to plot trigger rate as function of time
Variable name |
description |
|---|---|
live_time |
Tmestamp of the last event in the spill |
s0_counts |
Number of S0 count per spill |
trg_request_counts |
Number of trigger request per count per spill |
trg_accept_counts |
Number of trigger accepted count per spil |
trg_acp2req_ratio |
Ration betrwen trg_accept_counts and trg_request_counts |
Tagger Layer Ntuple:
In this Ntuple there is one row for one strip in the data stream, and it's used to plot the strip occupancy of the tagger layers
Variable name |
description |
|---|---|
Strip_Occupancy |
Strip number |
GOSED
The acronym stands for GLAST Online Single Event Display. It has been developed by the Online group at SLAC and in fact it is part of the standard LATTE distribution. It can either read data in realtime from the detector or playback stored ldf files.
