From: Frank Geurts (geurts_at_rice.edu)
Date: Wed May 07 2003 - 01:19:53 EDT
dongx_at_mail.ustc.edu.cn wrote:
> Hi, Frank:
> Dr. Wu and I have modified the MuDstMaker code for TOF microdst data.
> We have two versions now :) You may look at the directory
> /star/u/dongx/work/TOFr/MicroDst-bak and MicroDst-bak1
> In the first version, MicroDst-bak/ , we assume the StTofHit in StEvent
> has been updated ( just in StRoot/StEvent ), and we fill them in the
> analysis maker (StTofrSimMaker, which should be renamed actually), and
> then dump them into TCloneArrays in StMuDstMaker.
> In the second one, MicroDst-bak1/ , we just use the StEvent in lib now,
> and add StMuTofCollection, StMuTofHitCollection and StMuTofHit in
> MuDstMaker directory. Here StMuTofHit is very similar to the coming
> StTofHit. And we also fill StMuTofCollection in analysis maker and fill
> them into Micro Dst event in StMuDstMaker.
> These two both work well, I think. You may have a look at the most recent
> MuDst.root file in the corresponding directory.
> In either of these two, we need the analysis maker to give sufficient
> information according to the coming StTofHit, which means data should be
> calibrated already before filled into StTofCollection/StMuTofCollection.
> Would you please have a check before sent to the software guys? And also
> you should add the tofp analysis maker if you need.
great, i will look into this tomorrow ... the next star production will
most definitly use these muDSTs
>
> I think we should make clear for our TOF softwares now, including
> TofCollection in StEvent, TofMaker(analysis tofp/tofr),
> TofSimMaker(tofp/tofr), TofUtil( geometry, parameters etc.), MiniDstMaker,
> MicroDstMaker, embedding maker etc. Which can be put into lib now? Which
> needs modification? and what we need more?
>
Of the list of makers and utilties above, we can proceed with
introducing the geometry and the collections. Both are fundamental to
all other makers so committing those first is the way to go. Can you
update me on the (non-ROOT related) memory leak problems in
StTofrGeometry? The other parameter files very straightforward and need
no review, i suppose. I'ld suggest to put all utility files in the
already existing StTofUtil directory.
The updates and additions to the collections are in Thomas's court, like
I told you earlier today. Currently I am testing some of the updates in
a full chain ... and haven't seen any problems so far.
SimMakers depend very much on collections, but that doesn't keep us from
running it in a private environment for the time being. And, finally,
the mixermaker: jerome and i are not 100% sure your suggested scheme
will work (i.e. doing the mixing tpc-style, *before* StEvent is
available) and i hope you'll take another look at the rich and ftpc
mixermaker which i think are more in line w/ how we want tofp/r mixing
to look like.
cheers,
frank
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:41 EDT