Combine rntup (offline demuxing+ ntupling) and remake_dc0 (offline
demuxing + bank rewriting) into an official utility under the latest
"schema" of software organization. This includes:
using code management
putting the code in packages directory
reading the "proper" translation tables
providing user documentation
The purpose of the routine is to insure that raw banks demuxed offline
match the online demuxing. Raw data would be taken at intervals during
the physics runs to check the hardware/software operation.
I am gald that you want to retake over the care of demuxing. We should
discuss this so that I can design the utility I described so that the -SAME
CODE- can be compiled into the offile and online demuxing images. However, I
did find this difficult due to the machine differences and i/o
requirements. But maybe it is not impossible.
Talk to you soon,
Dave
------------------------------------------------------------------------
| David J. Tedeschi |
| Department of Physics and Astronomy (Email) tedeschi@sc.edu |
| University of South Carolina (Phone) 803-777-4121 |
| Columbia, SC 29208 (Fax ) 803-777-3065 |
------------------------------------------------------------------------
On Tue, 14 Oct 1997, David Heddle wrote:
>
> I was hoping to resume as caretaker of the de-muxing code. I will
> remind evryone of the history, as I recall it
>
> * I wrote version 1
> * My student and I wrote version 2
> * Sergui wrote version 3
> * Dave Tedeschi wrote version 4
>
> I have several ideas for speed/robustness improvements I will
> be trying out. I will need some help fro the DC group of
> course.
>
> If this has become anyone else's pet project let me know,
> although I would make a case that it would be most efficient
> for me to do this.
>
> Cheers,
>
> David
>
>
>