[Halld-cpp] [EXTERNAL] How much amorphous data should we take?
miskimen
miskimen at physics.umass.edu
Thu Jun 23 09:25:17 EDT 2022
Hi Elton, this looks like a reasonable plan for both full and empty target running. Rory
Sent from my iPad
> On Jun 23, 2022, at 8:29 AM, Elton Smith <elton at jlab.org> wrote:
>
> I received some feedback from Sean, Curtis, Alexandre and Alexander regarding the amount of amorphous radiator data needed.
>
> Another reason for having empty target data that I had overlooked is that it proves very useful for MONITORING. For example, see Alexandre’s log entry https://logbooks.jlab.org/entry/4006041. Alexander points out that we need regular amorphous data in order to normalize the coherent peak spectrum, which is used for monitoring during data taking. The consensus is that we may not need as much data as was taken for GlueX. Let me make the following proposal for the taking full-target data:
>
> Sequence for Full-Target Data
> Diamond 45(2h)/ Diamond 45(2h)/Diamond 135(2h)/Diamond 135(2h)/AMO(0.5 h). That results in 0.5/8.5h = 6% of time allocated to amorphous running. It also makes sure that we take the data uniformly through the running period.
>
> I am inclined to continue the SAME sequence of data taking for empty target, including the amorphous running, so that we have consistent sets between full and empty.
>
> Thoughts/comments?
>
> Cheers, Elton
>
>
>
> ------------------------------------
> Elton Smith
> Jefferson Lab MS 12H3
> 12000 Jefferson Ave STE 4
> Newport News, VA 23606
> (757)269-7625
>
>> On Jun 22, 2022, at 5:31 PM, Sean Dobbs <sdobbs at jlab.org> wrote:
>>
>> Hi Elton,
>>
>> Another thing we use the amorphous data for is to evaluate instrumental asymmetries. This may be something to be concerned about since you're looking at tracks at small angles, but I also agree that for this you probably need less data than we have been taking.
>>
>> Cheers,
>> Sean
>>
>>> On Wed, Jun 22, 2022 at 5:05 PM Curtis A. Meyer <cmeyer at cmu.edu> wrote:
>>> Hi Elton,
>>>
>>> I think we have used the amorphous data to also check systematics when we analyze data away from the coherent peak. My guess is you probably need less than GlueX.
>>>
>>> Curtis
>>>
>>>
>>> Curtis A. Meyer | MCS Associate Dean for Research
>>> The Otto Stern Professor of Physics
>>> cmeyer at cmu.edu | 412 260 6290
>>>
>>> Carnegie Mellon University
>>> Department of Physics, Wean Hall 8410
>>> 5000 Forbes Ave., Pittsburgh PA, 15213
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.curtismeyer.com&d=DwIFaQ&c=CJqEzB1piLOyyvZjb8YUQw&r=cpPCbeMAbcjUkVM8na3mXiIQlQp45KwF9GDqF5CC4ms&m=A-eFHIDO7MRvBbRC5V5WcDkU-PRO3jHzpZ6whFMVUNS5FmDOQf6Mts23eEtUEgFh&s=Hiq7O5c4oNHDXL8Rwna2SG9X0oBNb6UJcCb-ro50Z50&e=
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>> On Jun 22, 2022, at 16:57, Elton Smith <elton at jlab.org> wrote:
>>>>
>>>> Dear Hovanes, Mike, and others,
>>>>
>>>> The CPP experiment has been considering how much data should be taken with the amorphous radiator and wanted to get your input. As you know, for GlueX we collected about 10% of the triggers on the amorphous radiator.
>>>>
>>>> As, I understand it, the main arguments for collecting data with an amorphous radiator are a) to be able to normalize the coherent spectrum and b) check systematics of the polarization. We need very little data for a), but how much data we need to address b)? Also, if there are other used for the amorphous radiator data, please send us feedback.
>>>>
>>>> We have already started taking data that can be considered production and all of it was taken using polarized beam. We will want to make a plan regarding how much amorphous radiator data we take so that it is interspersed with diamond radiator data. At the moment, we do not anticipate using the amorphous radiator data in the physics analyzes for CPP nor NPP.
>>>>
>>>> Thanks, Elton.
>>>>
>>>>
>>>> ------------------------------------
>>>> Elton Smith
>>>> Jefferson Lab MS 12H3
>>>> 12000 Jefferson Ave STE 4
>>>> Newport News, VA 23606
>>>> (757)269-7625
>>>>
>>>
>
> _______________________________________________
> Halld-cpp mailing list
> Halld-cpp at jlab.org
> https://mailman.jlab.org/mailman/listinfo/halld-cpp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-cpp/attachments/20220623/2a6c44d4/attachment-0001.html>
More information about the Halld-cpp
mailing list