[Halld-offline] [EXTERNAL] Re: Monitoring Launch 2023-01 ver06

[Sean Dobbs]

Hi Beni,

Thanks for checking this out.  I'd been focusing more on the
calibration of other detectors, and hadn't looked closely at the
tagger yet.

My 2 cents:
- the TAGH bad counters seem to be at the level of the usual number of
bad/problematic counters so we can take a closer look at these
- the current scheme I'm using for the TAGM (while a more
sophisticated scheme is being developed) is pretty sensitive to some
of the thresholds and other
Also, some of the issues you are seeing are due to changes in the run
list that weren't recalibrated yet.

So, a few things to take care of before we do another launch.

Cheers,
Sean

On Fri, Sep 29, 2023 at 9:23 AM Beni Zihlmann via Halld-offline
<halld-offline at jlab.org> wrote:
>
> I should be more specific:
>
> regarding the tagger hodoscope: most runs are fine and only a few counters
> are slightly off.  and only two runs show a significant number of counters that are
> off (I guess because statistics issues). This I can fix easily I guess.
>
> regarding the microscope: here there are quite a few runs where it seems the issue
> is in the walk correction, making the picket-fence peaks wider and very asymmetric.
> this can only be fixed with redoing the walk correction and then after that once
> can again look at the constant offsets.
>
> cheers,
> Beni
>
> On 9/29/23 09:09, Beni Zihlmann via Halld-offline wrote:
>
> Hi Alex, Sean,
>
> I had a short look at the tagger timing offsets and I find some runs that seem to have
> many counters off. I think this may be related to the walk correction that is not good
> enough and causing the constant offset to be off. The reason I think the issue is more
> in the walk correction than in a simple constant offset is that the width of the peaks
> in he "picket-fence" plots are very wide and show even "double-peak" structures or
> humps on once side indicating that the walk correction applied uses not the best
> parameters.
>
> cheers,
> Beni
>
>
> On 9/28/23 09:58, Alexander Austregesilo via Halld-offline wrote:
>
> Dear Colleagues,
>
> We completed a new monitoring launch for the 2023-01 GlueX-II data set.
> We reconstructed 5 files for 548 runs with the RCDB query
> "@is_dirc_production and status>0".
>
> The usual monitoring plots can be found on the web pages:
>
> https://halldweb.jlab.org/data_monitoring/Plot_Browser.html
> https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/runBrowser.py
> https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/versionBrowser.py
>
>
> The merged histogram files can be found on the work disk at:
> /work/halld/data_monitoring/RunPeriod-2023-01/mon_ver06/rootfiles/
>
> The REST files, random trigger skims and several trees are saved on cache:
> /cache/halld/offline_monitoring/RunPeriod-2023-01/ver06/REST/
>
> Best regards,
>
> Alex
>
> _______________________________________________
> Halld-offline mailing list
> Halld-offline at jlab.org
> https://mailman.jlab.org/mailman/listinfo/halld-offline
>
>
>
> _______________________________________________
> Halld-offline mailing list
> Halld-offline at jlab.org
> https://mailman.jlab.org/mailman/listinfo/halld-offline
>
>
> _______________________________________________
> Halld-offline mailing list
> Halld-offline at jlab.org
> https://mailman.jlab.org/mailman/listinfo/halld-offline