[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: missing events from hdgeant
Thanks. Worked perfectly.
Richard Jones wrote:
> Mark,
>
> Yes, that feature is enabled/disabled by the somewhat verbose
> compile-time switch
>
> #define WRITE_ONLY_IF_SOMETHING_WAS_SEEN
>
> in gout.F source file. Just for fun sometime, you might do the
> command "grep '# *define' *.F and browse to see what other
> little-known behaviors are compile-time switchable in the code.
>
> From your particle gun command line below, I see that you have about
> 10% of the pions going in the upstream direction outside the
> acceptance of any of the detectors. For these events, there are no
> hits generated and so the default behavior is to not write them to the
> hddm output file. In fact, wasn't this a feature you requested? In
> any case, you can override the value in gout.F yourself, or perhaps
> better, I can move definitions like this into a central "steering"
> header file that contains all of these global-behavioristic defines in
> one place, that gets included into all of the source files. You might
> want to bring this up with the offline group and see if there is a
> consensus on how these should be treated.
> -Richard Jones
>
>
> Mark M. Ito wrote:
>> Folks,
>>
>> With the following particle gun config line:
>>
>> c particle momentum theta phi delta_momentum delta_theta delta_phi
>> KINE 108 2.0 90. 0. 3.0 180. 360.
>>
>> I am missing about 10% of the event numbers in the hdgeant output
>> file, i. e., I only get 1824 of the 2000 requested triggers, i. e.,
>> the first 10 events are:
>>
>> <physicsEvent eventNo="2" runNo="9999">
>> <physicsEvent eventNo="3" runNo="9999">
>> <physicsEvent eventNo="4" runNo="9999">
>> <physicsEvent eventNo="5" runNo="9999">
>> <physicsEvent eventNo="6" runNo="9999">
>> <physicsEvent eventNo="7" runNo="9999">
>> <physicsEvent eventNo="8" runNo="9999">
>> <physicsEvent eventNo="9" runNo="9999">
>> <physicsEvent eventNo="10" runNo="9999">
>> <physicsEvent eventNo="11" runNo="9999">
>>
>> What happened to event #1?
>>
>> I remember something about a feature that explains this. How do I
>> turn off the feature? Is this documented somewhere? I would like to
>> keep track of statistics including events with no hits, etc.
>>
>> -- Mark
>>
>