search

padsley / k600analyser

Code for the K600 analyser including plugin codes for silicon, clover and HAGAR data
1 stars 4 forks source link

SetupGATEAUDev #58

Closed padsley closed 5 years ago

padsley commented 9 years ago

Right.

In the interest of my being able to work on the GATEUA development for the offline sort, I've made a new branch.

@jwbrummer is in charge for this stuff but I will be responsible for writing much of the code. Between the two of us, we'll get something working.

Bear in mind that we're going to have to merge this branch with the GammaDev stuff of Luna and Retief's changes so when that happens, we're going to need beer.

At some point, all of this stuff will need to be merged back up to the master as well but I would suggest that we get consistency between the new branches before we try to be overly fancy.

padsley commented 9 years ago

After discussions, the data classes required for GATEAU sort:

  1. Number of wires that fired total.
  2. Number of wires that fired per PCB sector. This should be a 2 by 5 int array.
  3. The wires that fired for each PCB sector. Some sort of int array. Not worked out what yet...
  4. The TDC values for the wires that fired for each PCB sector. Some sort of int array as well? Same form as for part 3.

Then fit the track (if 3-16 wires in a sector have fired) with a linear function and compute and store the:

  1. chi**2/ndf
  2. TDC x-axis crossover value (as a proxy for the interaction position).
  3. Slope (as a proxy for angle).
  4. A flag for whether the event has been accepted as good (i.e. a condition on the number of wires that have fired in a sector).
padsley commented 9 years ago

Other data classes may be required but I haven't thought of them yet.