[d2n-analysis-talk] New Production Run List and Target Polarization

[yawei at jlab.org]

Sorry, guys! I could not attend today's meeting. But I have finished the
polarization for BB production list. Please see the attachments.

all.dat is the summary of the target information for BB production list.
The sequence is: BB production run# / start time(here I choose the first
production run #1311 as 0 time point.) / Pumping chamber temperature /
Target chamber temperature / Pumping chamber density / Target chamber
density / Polarization (about this polarizaion, you can find more details
in my technical note)

.pdf file contains some raw plots to check the stability of the LHRS & BB
runs.

If you have any questions about it, please feel free to contact me!
Thank you very much!

Best regards,
Yawei



> Thanks, Yawei. I will double-check the list and get it to you as soon
> as I can.
>
> Best,
> Diana
>
> On Feb 12, 2011, at 4:47 PM, yawei at jlab.org wrote:
>
>> Hi,
>>
>> If the Bigbite production run list is ready, I am happy to do the
>> interpolation for the Bigbite run list.
>>
>> Best regards,
>> Yawei
>>
>>
>>> So, Dave has put a new version of the production run list on the
>>> Wiki:
>>>
>>> https://hallaweb.jlab.org/wiki/index.php/List_of_special_runs_%28d2n
>>> %29#Left_HRS_Production_Runs_.28Major_Kinematic_Settings.29_.
>>> 5BNegative_Polarity.5D
>>>
>>> Hopefully, this update removes the problem runs that Yawei noticed,
>>> making possible a new (and better) interpolation of the target
>>> polarization.
>>>
>>> I have a question for the group. The present interpolation of the
>>> target polarization, run-by-run, is based on the (old) LHRS
>>> production
>>> run list. However, the target polarization is not going to be used in
>>> evaluating LHRS data; it's really for the BigBite analysis. I had
>>> assumed that the BigBite runs matched the LHRS runs roughly one-to-
>>> one, but as I was trying to produce a mapping today, I found that
>>> this
>>> was not actually the case. I've only gone through about a quarter of
>>> runs, but it is pretty common for there to be two BigBite runs per
>>> LHRS run, and even higher multiplicities are also possible -- I've
>>> found one LHRS run (20573) that seems to span six BigBite runs.
>>>
>>> If it would not be a prohibitive amount of extra work for Yawei
>>> compared to redoing the interpolation for the new LHRS run list,
>>> would
>>> it make more sense to switch over to using the BigBite run list?
>>>
>>> Best,
>>> Diana
>>>
>>
>>
>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: all.dat
Type: application/x-ns-proxy-autoconfig
Size: 24647 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20110218/d0769317/attachment-0001.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Target_Report_d2n.pdf
Type: application/pdf
Size: 1065757 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20110218/d0769317/attachment-0001.pdf