Bug #4184
Solve issue w/ flugg files having entries where no target info is present (and event # = 0)
Status:
New
Priority:
Normal
Assignee:
-
Start date:
06/20/2013
Due date:
% Done:
0%
Estimated time:
Description
Track down what causes flugg to generate entries where the information about the hadron coming out of the target is left unfilled. This seems to also be coupled to having the evtno (proton #) also left as zero.