Privacy and Security Notice
Archived Messages for CLAS_DRIFT_CHAMBERS@cebaf.gov: Re: Minutes of last DC/track meeting
Re: Minutes of last DC/track meeting
Joseph Manak (manak@jlab.org)
Thu, 16 Apr 1998 13:48:21 -0400
We have BOS banks for almost everything - DC_TDLY, geometry,
event x vs. t tables - just nobody uses them - our love of
common blocks is amazing... I agree that
if common blocks were not being shared between dc and trk
and if the dc package had some sort of coherent meaning - like
"where we put the chamber geometry" or something like that it
could stay a separate package - right now I don't really understand
what the purpose of it is (initialization of tracking? - filling
the wcs array for tracking? who knows...) - when I write a tracking
related routine I have no idea what package to put it in dc? trk?
I also get annoying problems because you have to be very careful
with your link list - some routines in one package are called by the
other - creating strange interdependancies and unresolved objects...
As for worrying about gsim being slower or something? if you link
to the greater trk lib instead of just dc - the linker will only fold
in routines that share the same file, so if you need the geometry from
track but not ana_segm you will only get the geometry...
- Joe