<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Here it is: <a href="https://userweb.jlab.org/~baltzell/.tmp/x.txt" class="">https://userweb.jlab.org/~baltzell/.tmp/x.txt</a></div><div class=""><br class=""></div><div class="">-Nathan</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 8, 2021, at 11:15 AM, Bravo, Cameron B. <<a href="mailto:bravo@slac.stanford.edu" class="">bravo@slac.stanford.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div class="">
<div class="">Hello,</div>
<div class=""><br class="">
</div>
<div class="">I never saw a run list from Norman. Can you forward that info so the collaboration has access to it?</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">Cameron</div>
<hr style="display:inline-block;width:98%" tabindex="-1" class="">
<div id="divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size:11pt" class=""><b class="">From:</b> <a href="mailto:hps-software@SLAC.STANFORD.EDU" class="">hps-software@SLAC.STANFORD.EDU</a> <<a href="mailto:hps-software@SLAC.STANFORD.EDU" class="">hps-software@SLAC.STANFORD.EDU</a>> on behalf of Nathan Baltzell <<a href="mailto:baltzell@jlab.org" class="">baltzell@jlab.org</a>><br class="">
<b class="">Sent:</b> Tuesday, December 7, 2021 7:03 PM<br class="">
<b class="">To:</b> <a href="mailto:hps-analysis@jlab.org" class="">hps-analysis@jlab.org</a> <<a href="mailto:hps-analysis@jlab.org" class="">hps-analysis@jlab.org</a>>; hps-software <<a href="mailto:hps-software@slac.stanford.edu" class="">hps-software@slac.stanford.edu</a>><br class="">
<b class="">Subject:</b> Re: [Hps-analysis] 2021 trigger skims</font>
<div class=""> </div>
</div>
<div class="BodyFragment"><font size="2" class=""><span style="font-size:11pt;" class="">
<div class="PlainText">Hello All,<br class="">
<br class="">
After some further preparations, the 2021 trigger skims are launched.<br class="">
<br class="">
Outputs will be going to /cache/hallb/hps/physrun2021/production/evio-skims.<br class="">
<br class="">
I broke the run list from Norman into 5 lists, and started with the first 20% in one batch, all submitted. I'll proceed to the other 4 batches over the holidays, assessing tape usage as we go.<br class="">
<br class="">
-Nathan<br class="">
<br class="">
> On Nov 29, 2021, at 3:39 PM, Nathan Baltzell <<a href="mailto:baltzell@jlab.org" class="">baltzell@jlab.org</a>> wrote:<br class="">
> <br class="">
> The 10x larger test is done at /volatile/hallb/hps/baltzell/trigtest3<br class="">
> <br class="">
> -Nathan<br class="">
> <br class="">
> <br class="">
>> On Nov 29, 2021, at 2:52 PM, Nathan Baltzell <<a href="mailto:baltzell@jlab.org" class="">baltzell@jlab.org</a>> wrote:<br class="">
>> <br class="">
>> Hello All,<br class="">
>> <br class="">
>> Before running over the entire 2021 data set, I ran some test jobs using Maurik’s EVIO trigger bit skimmer. Here’s the fraction of events kept in 14750 for each skim:<br class="">
>> <br class="">
>> fee 2.0%<br class="">
>> moll 3.3%<br class="">
>> muon 1.9%<br class="">
>> rndm 2.9%<br class="">
>> <br class="">
>> In each case, it’s inclusive of all such types, e.g., moll=moll+moll_pde+moll_pair, rndm=fcup+pulser.<br class="">
>> <br class="">
>> Are those numbers in line with expectations? The total is 10% and not a problem if these skims are expected to be useful. The outputs are at /volatile/hallb/hps/baltzell/trigtest2 if people are interested to check things.<br class="">
>> <br class="">
>> A 10x larger test is running now and going to /volatile/hallb/hps/baltzell/trigtest3 and should be done in the next couple hours.<br class="">
>> <br class="">
>> ************<br class="">
>> <br class="">
>> Note, it would be prudent to do this *only* for production runs, those that would be used in physics analysis, to avoid unnecessary tape access. By that I mean removing junk runs, keeping only those with some significant number of events, and only keeping
those with physics trigger settings (not special runs). For that we need a run list. I think we have close to a PB, but I remember hearing at the collaboration meeting that at least 20% is not useful for the porpoises of trigger bit skimming.<br class="">
>> <br class="">
>> -Nathan_______________________________________________<br class="">
>> Hps-analysis mailing list<br class="">
>> <a href="mailto:Hps-analysis@jlab.org" class="">Hps-analysis@jlab.org</a><br class="">
>> <a href="https://mailman.jlab.org/mailman/listinfo/hps-analysis" class="">https://mailman.jlab.org/mailman/listinfo/hps-analysis</a><br class="">
> <br class="">
<br class="">
<br class="">
########################################################################<br class="">
Use REPLY-ALL to reply to list<br class="">
<br class="">
To unsubscribe from the HPS-SOFTWARE list, click the following link:<br class="">
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__listserv.slac.stanford.edu_cgi-2Dbin_wa-3FSUBED1-3DHPS-2DSOFTWARE-26A-3D1&d=DwMF-g&c=CJqEzB1piLOyyvZjb8YUQw&r=HLszBssMDrxg1suTls0aX2y52oDK_fWrLNLTgw_5saE&m=w73GiS4BL7KeYy9evAuVAXjRWWZlbLCqOPcIFDaPbFQUMSVhMLBc7njIqBYWupAo&s=f-4orMSAw1m9x7bfLT-VQAJZrOPDvFEWd5GCFy3PnKU&e=" class="">https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1</a><br class="">
</div>
</span></font></div>
</div>
</div></blockquote></div><br class=""></div></body></html>