[Halld-offline] [Fwd: Re: bggen thrown particle type]

[Blake Leverington]

Ok, thanks guys. In trying to filter background events down to a 
manageable size I hadn't realized the whole process tree was there so it 
was giving me funny results when I was filtering on thrown information 
and was looking at mcthrown histograms.

-Blake

Alexander Somov wrote:
>
> Hi,
>
> Might also be useful: if you use tracks relations between DMCThrown
> and DMCTrackHit, you have to skip tracks in the DMCThrown with
> type = 0 (geant id = 0).
>
> Cheers,
>        Alex
>
>
>
>
>> Date: Mon, 27 Jul 2009 19:54:34 -0600
>> From: Blake Leverington <leverinb at uregina.ca>
>> To: Eugene Chudakov <gen at jlab.org>
>> Cc: Alexander Somov <somov at jlab.org>
>> Subject: Re: bggen thrown particle type
>
>> Ok, I was unsure how HDGeant handled the events that weren't final 
>> state. I was trying to figure out what my background was and all 
>> these extra events were confusing me.
>
>> -Blake
>
>> Eugene Chudakov wrote:
>>> The bggen writes out everything, since it might be
>>> useful to be able to check the event structure later. The reading
>>> routine in HDGeant should be smart and store into GEANT only the 
>>> entries
>>> with a non-zero code. I thought it had been done this way, but
>>> I am not sure. Alex Somov or David may know. Alex used the bggen
>>> output with HDGeant.
>>>
>>> Eugene
>>>
>
>
>