hi wang,
it is a pain to branch and then merge, so i would prefer to do the
debugging right on the head branch until we are ready to recrunch. then
we will will make a stable branch "b3_2" and use it for crunching until
the next cycle.
keeping that in mind, please hold off on experimental code until after
the recrunch. i believe we will want to base our new recrunch on the
latest version anyways.
--chris
adrian,
see chi's note about the most recent branch he added. it is basically
the head except for TBLFitTrack.{cc,h}, which has a segfault i haven't
had time to fix. note that need the latest version of FitTrack for the
recrunches, since it fixes the integrated path length.
--chris
(blast_talk, 2004/5/30)
Hi,
I narrowed down the problem to TBLFitTrack.h/cc. So I create another tag
called memorialday2. update to this tag would give you a copy of library
that works and is closest to the current version. all files in this tag
are same as the head except TBLFitTrack.h and .cc
If you want to do developement on sources other than these two, you can
update to head and revert these two files back to the tag by:
cvs up -rmemorialday2 TBLFitTrack.*
Chi
Wang Xu wrote:
>Hi Adrian,
> Since almost every one submit some codes into the head version
>without fully debuging the codes, (In fact, it is very difficult to debug)
>It often cause some mistakes, even segmentation faults. Because we will do
>a big recrunch for all recent runs, therefore I suggest we should make a
>branch and carefully check the codes, then start to do recrunch.
> Wang
>
>
>On Tue, 8 Jun 2004, Wang Xu wrote:
>
>
>
>>Hi Adrian,
>> I did not setup time information. Other than that, everything are
>>inculded in Bats software.
>> Codes currently are in cvs_v3bats/ directary.
>> Wang
>>
>>On Mon, 7 Jun 2004, Adrian T Sindile wrote:
>>
>>
>>
>>>Hi, Wang!
>>>Here is the TOF info I am currently using in my analysis:
>>>
>>>gRecon->fTracks(itrk)->fDet->TOF_PAD(),
>>>gRecon->fTracks(itrk)->fDet->PathLength(),
>>>gRecon->fTracks(itrk)->fDet->TOF_rtime(),
>>>gRecon->fTracks(itrk)->fDet->TOF_time(),
>>>gRecon->fTracks(itrk)->fDet->TOF_E(),
>>>gRecon->fTracks(itrk)->fDet->TOF_Chi2(),
>>>gRecon->fTracks(itrk)->fDet->TOF_Y(),
>>>
>>>Do we have these for the BATs (except, of course, the Chi2 of the track,
>>>since the BATs are outside the WC acceptance)? What else will we have
>>>there?
>>>
>>>Also, since we will be recrunching from the head version of BlastLib2, why
>>>don't you merge your stuff into the head version (unless somebody sees a
>>>problem with this - please speak up guys, if so)?
>>>
>>>Thanks!
>>>
>>>Adrian
>>>
>>>-------------------------------
>>>Adrian Sindile
>>>Research Assistant
>>>Nuclear Physics Group
>>>University of New Hampshire
>>>phone: (603)862-1691
>>>FAX: (603)862-2998
>>>email: asindile@alberti.unh.edu
>>>http://einstein.unh.edu/~adrian/
>>>
>>>
>>>
>>>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:31 EST