[Clas12_first_exp] Train Output v2 (New DSTs to look at)

[William Phelps]

Hello FX,

You are correct. The two FT skims have either 2 charged tracks or two photons, both with the electron required in the FT. 

We could add a looser skim and see how large it is, but I would require a charged track instead of a pion. It is not currently possible to add a photon momentum cut without adding a custom wagon, which can be done. Let me know how you would like to proceed. 

-Will

> On Mar 6, 2019, at 5:35 PM, Francois-Xavier Girod <fxgirod at jlab.org> wrote:
> 
> Thanks for the reply Will
> I think there is not skim e in FT + one pion + one photon currently
> I am concerned that this skim would be too loose: will it be possible to apply more strict cuts in the future, here namely a cut on the photon energy to be above a few GeV for instance?
> I think we discussed having custom wagons before but I don't know if this was implemented yet
> 
> On Wed, Mar 6, 2019 at 11:32 PM William Phelps <wphelps at jlab.org <mailto:wphelps at jlab.org>> wrote:
> Hello FX,
> 
> There is a filtering scheme in the README.txt file. I have included the skims that I think are relevant for you and a tabular summary of the skims (which is slightly out of date since it excludes the epiN skim). 
> 
> If you would like a more specific skim that doesn’t overlap with other skims too much I would be happy to add it.
> 
> Also, I will update the RGA Analysis wiki page to make it more clear what the skims are similar to the table I have attached. I hope I have answered your question, please let me know if you have any other questions.
> 
> -Will
> 
> 
> #################################################### MESONEX-VERYSTRANGE
> # Electron and Pi0 in FT
>     PIZERO:
>       id: 2
>       tagger: 11:22:22:X+:X-:Xn
> # Twon pions with Electron in FT
>     TwoPionFTa:
>       id: 3
>       tagger:  11:X+:X-:Xn
>       forward: 1+:1-:X+:X-:Xn
>     TwoPionFTb:
>       id: 3
>       tagger:  11:X+:X-:Xn
>       forward: 2+:X+:X-:Xn
>     TwoPionFTc:
>       id: 3
>       tagger:  11:X+:X-:Xn
>       forward: 1+:X+:X-:Xn
>       central: 1+:X+:X-:Xn
>     TwoPionFTd:
>       id: 3
>       tagger:  11:X+:X-:Xn
>       forward: 1-:X+:X-:Xn
>       central: 1+:X+:X-:Xn
>     TwoPionFTe:
>       id: 3
>       tagger:  11:X+:X-:Xn
>       central: 2+:X+:X-:Xn
>     TwoPionFTf:
>       id: 3   
>       tagger:  11:X+:X-:Xn
>       forward: 1+:X+:X-:Xn
>       central: 1-:X+:X-:Xn
>     TwoPionFTg:
>       id: 3
>       tagger:  11:X+:X-:Xn
>       central: 1+:1-:X+:X-:Xn
> 
> 
>> On Mar 6, 2019, at 5:17 PM, Francois-Xavier Girod <fxgirod at jlab.org <mailto:fxgirod at jlab.org>> wrote:
>> 
>> Dear Will
>> 
>> I am not quite sure I can read the filter logic still, so maybe I will just ask directly
>> I am interested in events with one electron in the forward tagger, at least one pion anywhere, and at least one photon anywhere. 
>> Is this currently available? Seems to me like a no...
>> 
>> Thanks
>> 
>> Best regard
>> FX
>> 
>> On Wed, Mar 6, 2019 at 10:58 PM William Phelps <wphelps at jlab.org <mailto:wphelps at jlab.org>> wrote:
>> Hello All,
>> 
>> I have finished running the trains over the recently cooked full runs. Please have a look and let me know if you have any questions! Also, please let me know if you have requests for additional wagons/skims for the future.
>> 
>> They are located here: /work/clas12/clas12/data/trains/v2/
>> There is a README.txt file that details the contents of the skim.
>> 
>> Spring 2018:
>> 4013
>> 
>> Fall 2018:
>> 5000, 5001, 5030, 5036, 5038, 5046, 5117
>> 
>> Thanks,
>> -Will
>> 
>> 
>> _______________________________________________
>> Clas12_first_exp mailing list
>> Clas12_first_exp at jlab.org <mailto:Clas12_first_exp at jlab.org>
>> https://mailman.jlab.org/mailman/listinfo/clas12_first_exp <https://mailman.jlab.org/mailman/listinfo/clas12_first_exp>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/clas12_first_exp/attachments/20190306/0d288385/attachment-0001.html>