Re: Empty events (again)

[David Lawrence <davidl@jlab.org>]

Hi Richard,

    Thanks for looking into this. When I look at the "empty" events 
using hddm-xml, I can see there are some hits in the forwardTOF and 
forwardEMcal  sections inside of hitView. There are also 
mcTrajectoryPoint sections recording the particle information at every 
step so I can see that the tracks go through the volume of the CDC and 
are not scattered down the beamline. You can look at the hddm file  if 
you like in the /scratch/davidl directory on the JLab CUE. I have also 
pulled out just the empty events I listed into separate files to make it 
easier to look at single, problematic events.

    In regards to the "unrecognized Red Hat release" messages: Those 
should be only informational and should not prevent you from building 
anything. They are coming from the scripts/osrelease.pl script. You must 
have a linux version not listed in the script. Feel free to update it 
based on the contents of your /etc/redhat-release file so others won't 
be similarly annoyed by all of the warning messages.

Regards,
-David

Richard Jones wrote:
> Dave,
>
> I applied all of the latest updates from the main trunk under 
> subversion, and ran with your control.in, but none of the events 
> looked unusual to me.  In particular, the events you listed (84, 464, 
> 493, 532) all had copious numbers of CDC hits.  Can you remind me what 
> you mean by no hits?  Literally that, just a Monte Carlo header and no 
> contents in the <hitsView> element?  I have now initiated a complete 
> rebuild of the exact release-2009-05-27 and will try that one as soon 
> as I can get it to build.  Right now, I am getting hit with 
> "unrecognized Red Hat release" messages from the BMS make system.
>
> -Richard J.
>
>
>
> David Lawrence wrote:
>> Hi Richard,
>>
>>     This problem with events occasionally showing up with no hits 
>> seems to still be present, albeit at a much lower level. I reported 
>> on this a few weeks ago and promised I'd send you the details needed 
>> to reproduce it. I'm now finally getting around to it.
>>
>>     I have attached a control.in file that exhibits the problem in 
>> events 84, 464, 493, and 532 when run with release-2009-05-27. (Note 
>> that this is release-2009-05-27 as of todays patch, not the original 
>> release-2009-05-27).
>>
>>     I should note that these events show the problem when running it 
>> on Linux. I see the same problem when running on Mac OS X, but for 
>> different run numbers. This behavior is different than when I ran 
>> across this problem originally where the same event seemed to show 
>> the problem on both platforms. I don't know if this is because I'm 
>> making a mistake or something has changed with the random number 
>> generators used on the 2 systems. If you don't see the problem for 
>> the event numbers I indicated, just let me know and I'll look a 
>> little deeper.
>>
>> Regards,
>> -David
>>
>>   
>

-- 

------------------------------------------------------------------------
 David Lawrence Ph.D.
 Staff Scientist                 Office: (757)269-5567   [[[  [   [ [       
 Jefferson Lab                   Pager:  (757)584-5567   [  [ [ [ [ [   
 http://www.jlab.org/~davidl     davidl@jlab.org         [[[  [[ [[ [[[
------------------------------------------------------------------------