There are really four sorts of variables, which are classified by what the array index means.
- Class One:
+ -=Class One=-
Array index is the detector. So for example, na.nd.n1.LT element 4 would be the the left time for detector N1-4.
- ((na.nd.n#.LT))
- ((na.nd.n#.LA))
- ((na.nd.n#.LApedc))
- Class Two:
Array index is the hits, lowest index number is hit that hit lowest in the detector. For example, na.nd.n1.hit_tof element would be the ((tof)) variable for the lowest detector number hit in plane N1.r />((na.nd.n#.hit_tof)) />((na.nd.n#.hit_bar))r />((na.nd.n#.hit_Edep)) />((na.nd.n#.hit_ypos))
((na.nd.n#.hit_xpos)) />((na.nd.n#.lthit_time)) />((na.nd.n#.lthit_bar))
((na.nd.n#.lahit_Adc)) />((na.nd.n#.lahit_Adcp))r />((na.nd.n#.lahit_bar))
+ ===Class One Software Variables===
||__Variable Name__|__Description__
na.nd.n1.LT| This is the Left Time ((Neutron Plane)) 1, corrected for all corrections in the DB used to create it.
na.nd.n2.RT| This is the Right Time. See Left Time description. For all variables that might have a left or right, L refers to left and R refers to right (of this variable type).
na.nd.m1.LA| This is the Left raw Adc value for the ((Marker Bar)).
na.nd.s1.RApedc| This is the Right pedestial corrected Adc value for the ((Sums)). ||
- Class Three:
+ -=Class Two=-
The Array index runs over the channels with 'hits'.
These are packed arrays, such that only channels that have information get saved. This would permit for space-savings (if the Class One variables were not saved), but also for multiple-hits per channel to be stored. The most basic TDC and ADC information is stored here as __na.nd.{planename}.lthit___, __na.nd.{planename}.rthit___, __na.nd.{planename}.lahit___,
and __na.nd.{planename}.rahit___. Arrays with the same prefix (up to the _____) are __parallel__; for example the entries na.nd.n1.lthit_time[[3] and na.nd.n1.lthit_bar[[3] correspond.
The stored information is sorted by the channel number (most often bar-number). For example, na.nd.n1.hit_tof element 0 would be the ((tof)) variable for the lowest detector number hit in plane N1.
First-level reconstructed information, such as associating all the TDCs and ADCs of the detector element, is stored as '__na.nd.{planename}.hit___'.
===Class Two Software Variables===
||__Variable Name__|__Description__
na.nd.n3.lthit_time| corrected time for a 'hit' on the left PMT.
na.nd.n3.lthit_bar| associated bar number for the 'hit' on the left PMT.
na.nd.n1.rahit_Adc| This is the variable that gives the raw Adc value for a right adc hit.
na.nd.n1.rahit_Adcp| This is the variable that gives the pedestal corrected Adc value for a right adc hit.
na.nd.n1.rahit_bar| This is the variable that gives the associated bar number with a right adc hit.
na.nd.n4.hit_tof| This will be the time of flight variable. Currently it is the ((Average Time)) for a given hit in ((Neutron Plane)) 4.
na.nd.n3.hit_bar| This is the variable that gives the bar number for a given hit in ((Neutron Plane)) 3.
na.nd.n7.hit_Edep| This is the variable that gives the energy deposited in a bar for a given hit in ((Neutron Plane)) 7.
na.nd.n6.hit_ypos| This is the variable that gives the ((Y Position)) for a given hit in ((Neutron Plane)) 6.
na.nd.n5.hit_xpos| This is the variable that gives the ((X Position)) for a given hit in ((Neutron Plane)) 5.
||
-=Class Three=-
Array index is the hits, lowest index number is the hit that had the highest Energy Deposition.
- Class Four:
+ -=Class Four=-
Array index size. This is just a the maximum array size for one of the array variables. For example, for na.nd.n1.lthit_time it would be the largest number of hits in N1 in a given event. These variables are in the form:
Ndata.*
where * is the arrayed variable.
| ![[hide]](javascript:icntoggle('mod-mnu_application_menu','mo.png');)
Wiki