[G8b_run] g8b question

[Barry Ritchie]

Precisely. Sorry for any confusion. And the issue is the day, not the
time. If we can shift to every other week starting the Monday after
next, then there's no problem with the time.

---BGR

Professor  Barry G. Ritchie 
Department of Physics 
Arizona State University 
Tempe, AZ  85287-1504 
  
Telephone: (480) 965-4707 
Fax: (480) 965-7954 


-----Original Message-----
From: Michael Dugger [mailto:michael.dugger at asu.edu] 
Sent: Wednesday, July 20, 2011 8:01 AM
To: Barry Ritchie
Cc: Kenneth.Livingston at glasgow.ac.uk; g8b_run at jlab.org;
soulish at gmail.com; Nicholas Zachariou
Subject: Re: [G8b_run] g8b question


Hi,

When Barry says 9 AM, I think he means 12 Jlab time.

-Michael

On Wed, 20 Jul 2011, Barry Ritchie wrote:

> For those of us working with the Glue-X tagger, that time on this
coming
> Monday overlaps those standing meetings, which occur every other week.
> Can we pick 9 AM on another day or move to a week later so as not to
> overlap?
>
> ---BGR
>
> Professor  Barry G. Ritchie
> Department of Physics
> Arizona State University
> Tempe, AZ  85287-1504
>
> Telephone: (480) 965-4707
> Fax: (480) 965-7954
>
> -----Original Message-----
> From: g8b_run-bounces at jlab.org [mailto:g8b_run-bounces at jlab.org] On
> Behalf Of Ken Livingston
> Sent: Wednesday, July 20, 2011 4:52 AM
> To: g8b_run at jlab.org
> Cc: soulish at gmail.com; Nicholas Zachariou
> Subject: Re: [G8b_run] g8b question
>
> Hi Eugene and all,
> Let's try to have weekly g8 meetings from now on to discuss this,
> polarization etc. We seemed to drift towards having meetings on
mondays
> at 12.00 Jlab time. Is that OK with everyone? - If so can we meet next
> on Monday 25th at 12.00 EST.
>
> Cheers,
> Ken
>
>
> On 07/20/2011 05:31 AM, Eugene Pasyuk wrote:
>> Can you look at other banks: PART/TBID, GPID for these events?
>> also SCRC, STR, SCPB, STPB
>>
>> -Eugene
>>
>>
>>
>> On 7/20/2011 12:21 AM, Brian Vernarsky wrote:
>>> Eugene,
>>>
>>> I know, it makes no sense, which is what leads me to believe that it
>>> might be an error...I'm hoping.  As a reference point I have been
> able
>>> to find a number of events in a particular BOS file that is
available
>>> on the cache disk.  The file is
>>> /cache/mss/clas/g8b/production/Pass1/v1/BOS/cooked_048089.A13.B00
>>> (chosen simply because it was available).  There are a 34 "bad"
> events
>>> in this file.  Below I have included one particular event with as
> much
>>> information as I can muster about it, you can see that an MVRT
vertex
>>> is found, momentum is found for all particles.  Each new particle
>>> begins with the Particle ID.  Perhaps the most important line for
> each
>>> of the particles is the 4th one which contains the SC status, paddle
>>> id, etc.  There are two values for some of the variables, those are
>>> just calculated in two different ways.  This particular event is
>>> 9385225.
>>>
>>> Charged(3):
>>>      MVRT vertex: (0.709342,-0.0453113,-12.4996) Vtimes: (1):
3.10515
> (2): 3.10516
>>>      Particle IDs: SEB: 14 PART (1): 14 PART(2): 14
>>>        Q: 1 P: (0.193137,-0.510105,0.981207) Sector: 6
>>>        Vertex: (-0.447834,-0.258554,-13.2271) ST: time: 0 vtime: 0
>>>        SC: status: 0,0 paddle id: 0,0 edep: 0,0 path: 0,0 time: 0,0
> chi2: 0
>>>        EVNT flags: status: 2 DC: 3 CC: 0 SC: 0 EC: 2 LC: 0 ST: 3
>>>      Particle IDs: SEB: 9 PART (1): 9 PART(2): 9
>>>        Q: -1 P: (-0.386338,0.151609,0.290332) Sector: 4
>>>        Vertex: (-1.98492e-06,-0.782951,-11.8707) ST: time: 3.279
> vtime: 2.82
>>>        SC: status: 33,2 paddle id: 22,22 edep: 12.6,12.6 path:
>>> 557.06,557.06 time:22.101,22.101 chi2: 1.9
>>>        EVNT flags: status: 3 DC: 2 CC: 0 SC: 1 EC: 1 LC: 0 ST: 2
>>>      Particle IDs: SEB: 0 PART (1): 8 PART(2): 8
>>>        Q: 1 P: (0.137921,0.133909,0.177599) Sector: 2
>>>        Vertex: (-0.0280066,0.0161696,-12.8483) ST: time: 0 vtime: 0
>>>        SC: status: 0,0 paddle id: 0,0 edep: 0,0 path: 0,0 time: 0,0
> chi2: 0
>>>        EVNT flags: status: -2 DC: 1 CC: 0 SC: 0 EC: 0 LC: 0 ST: 1
>>>
>>> I can give more info if needed.  (Note: this is not sent to the g8
>>> list as I'm not a member of it yet).
>>>
>>> Cheers,
>>>
>>> Brian
>> _______________________________________________
>> G8b_run mailing list
>> G8b_run at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/g8b_run
>
> _______________________________________________
> G8b_run mailing list
> G8b_run at jlab.org
> https://mailman.jlab.org/mailman/listinfo/g8b_run
>
> _______________________________________________
> G8b_run mailing list
> G8b_run at jlab.org
> https://mailman.jlab.org/mailman/listinfo/g8b_run
>