Peter and all others,
For now yield_by_fill.C. It is in the utils directory. One caviate
though, as Karen said you need to update histogram limits as fill number
grows. I will think about a work around but for now just update it
every time you need to run it. Also, if there are any time cuts that I
can use to cut on (e,e'p) and (e,e'd) events without using wirechamber
info please let me know.
Cheers, Vitaliy
P.S. Please keep up with the crunching. This will allow me to use
maximum number of events for my analysis.
Peter Karpius wrote:
>Which is(are) the best macro(s) to run while on shift to comply with
>Richard's request?
>
> Pete
>
>---------- Forwarded message ----------
>Date: Wed, 31 Mar 2004 05:30:55 -0500 (EST)
>From: Richard Milner <milner@mitlns.mit.edu>
>To: Tancredi Botto <tancredi@lns.mit.edu>
>Cc: Blast_Shifts <Blast_shifts@rocko.mit.edu>, elog <elog@blast02.lns.mit.edu>
>Subject: Re: [BLAST_SHIFTS] minutes BLAST operation meeting 30/3/04
>
>
>Can we have each shift report in the shift summary the normalized rate
>for the major events in the experiment? This requires establishing
>canonical cuts for say (e,e'p) and (e.e'd). This is a vital quality
>control parameter of the experiment. It will be sensitive to both target
>thickness and wire chamber efficiency.
>
>Richard
>
>
>
>
>On Tue, 30 Mar 2004, Tancredi Botto wrote:
>
>
>
>>Plan is to resume polarized data taking.
>>
>>Outstanding questions (still) are
>>
>>_ tensor ed asymmetry where there is an apparent disagreement between
>> Genya and Chi. Presently the spin angle required to explain observed
>> result by GT would be 60 deg which would only possible for a small long
>> field. No report on false asymmetries, event by event correction to spin
>> angle, montecarlo
>>
>>_ Dilution factor from tensor asymmetry in ee'p is now complarable with
>> that from vector polarization. df~60 % in both sectors with a large
>> error bar since it is onyl sensitive to the high pmiss region. See
>> vitaly on thursday for a full report
>>
>>_ need to monitor ee'p events and correlate to ABS "fluctuations". Old
>> monitor based on charge file would not work presently
>>
>>
>>ABS:
>>
>>The ABS nozzle was temperature cycled. REady for data. The ligit
>>monitor of the ABS intensity presently shows 5.1x10^-8 vs 6.3 this
>>weekend (and 6.0 last week ?). Genya also agrees that we may just
>>have lower intensity.
>>
>>Lower ABS temperature to 82 K: will give 10 % density back and should
>>be safe for D2 based on hermes experience.
>>
>>BEAM:
>>A new set of steering coils have been installed. GT reports a lower beam
>>lifetime (from 30 minutes). CCR will optimize beam tonight.
>>
>>LADS:
>>Continued calibration work
>>
>>BATS:
>>cosmic data taking
>>
>>RunPlan:
>>After LADS and ABS we could remove wch and target covers. Plan is
>>to resume pol D2 running, 3 spin states flipping... no beam spin
>>flipper.
>>
>>
>>
>>
>
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST