[Clas12_software] Feb. 13 minutes: software meeting

[Mac Mestayer]

Hello all;

Here are my minutes of yesterday's meeting.

Veronique presented a summary of her proposal for
near-term project priorities.

1- she has placed the DC geometry document on the wiki
as an example for the other detector groups

2- the detector groups are responsible for two other
documents: a MONITORING document which describes the
kinds of numbers, plots, graphs which are necessary to
monitor performance at various levels: data-taking, event
reconstruction, software debugging; and a CALIBRATION
document which names and describes all of the numbers
necessary to convert signals to corrected hits

3- we spent most of the time discussing the details of
the event-building algorithm.  Stepan, Veronique, Johann
and I will meet next week to come up with a detailed
logic flow-chart of event reconstruction; if anyone of
you wants to be at this meeting, please contact me.

There were some factual issues raised in this discussion:
one was how track - outer-detector matching would take
place - it seems the general consensus is that the
tracking program would build a TRAJECTORY along with
the track; this TRAJECTORY would consist of an vector
of information evaluated at many points along the
track's trajectory (including extrapolations beyond the
tracking detectors).  This vector might contain x,y,z,
curvature,two angles,time, other?

There was also some discussion about bank structures.
Depending on the verbosity required of a process (tracking,
for example) one might just output the track parameters at
the origin and the trajectory information; or if more detailed
info. is requested, residuals at each measurement plane, etc.
We will need to decide if the additional information is kept
in a separately named new bank, or as additional columns in
the same bank.

That'a all the notes I have.  If you have additional comments
or corrections, please respond to the group.

 				- Mac


"mestayer at jlab.org", (757)-269-7252