[Sbs_gems] [EXTERNAL] Re: [New Logentry] SBS GEM Latency Scan Results

[Anuruddha Rathnayake]

Hi Nilanga,

Actually it peaks at the 5th TS now. See page 3, 3d raw, 3rd and 4th plots.

In BB GEMs we have the signals peaking at the 4th TS. See here fore
reference
https://logbooks.jlab.org/files/2022/10/4061353/summaryPlots_1999_bb_gem.pdf

If I remember correctly, it was decided during GMn to cut out background
that are present in the fist few time samples and separate good signals
from them.
Also if we want to apply Time Sample Deconvoution later on, it is better to
have 3rd TS peaking as opposed to 4th TS peaking.

Best,
Anuruddha



On Mon, Oct 17, 2022 at 4:53 PM Liyanage, Nilanga K (nl8n) via Sbs_gems <
sbs_gems at jlab.org> wrote:

> Hi Anuruddha
>
> This looks great.
>
> I guess later you can shift it by a tiny bit more, right ? Looks like
> currently max ADC is peaking at the 4th sample, and it would be best to
> have it in the 3rd one
>
> Best
>
> Nilanga
> ------------------------------
> *From:* Sbs_gems <sbs_gems-bounces at jlab.org> on behalf of adr--- via
> Sbs_gems <sbs_gems at jlab.org>
> *Sent:* Monday, October 17, 2022 4:45 PM
> *To:* sbs_gems at jlab.org <sbs_gems at jlab.org>
> *Subject:* [Sbs_gems] [New Logentry] SBS GEM Latency Scan Results
>
> SBS GEM Latency Scan Results <https://logbooks.jlab.org/entry/4061421>
>
>    - Edit
>    <https://logbooks.jlab.org/entry/4061421/edit?destination=email/send>
>    - Delete
>    <https://logbooks.jlab.org/entry/4061421/delete?destination=email/send>
>
> Lognumber 4061421 <https://logbooks.jlab.org/entry/4061421>. Submitted by
> adr <https://logbooks.jlab.org/user/adr> on Mon, 10/17/2022 - 16:41
> <https://logbooks.jlab.org/entries?start_date=1666035710&end_date=1666042910&book=HALOG&book=SUPERBIGBITE>.
>
> Logbooks: HALOG <https://logbooks.jlab.org/book/halog> SUPERBIGBITE
> <https://logbooks.jlab.org/book/superbigbite>
> Tags: GEM <https://logbooks.jlab.org/tag/gem>
> Entry Makers: adr
> References: 4057468 - BB and SBS GEM, MPD trigger time difference = 240
> ns = 10 latency units <https://logbooks.jlab.org/entry/4057468>
>
> We found that our guess value for global latency of "102" for SBS GEM
> latency is correct/very close.
>
> Look at page 3, 3rd raw, 3rd and 4th plots in the attached files. These
> are max time sample histos for U/X and V/Y strips respectively, for events
> with track cuts.
>
> At 102 latency ->
> https://logbooks.jlab.org/files/2022/10/4061348/summaryPlots_1998_sbs_ge...
> <https://logbooks.jlab.org/files/2022/10/4061348/summaryPlots_1998_sbs_gem.pdf>
> At 108 latency ->
> https://logbooks.jlab.org/files/2022/10/4061354/summaryPlots_1999_sbs_ge...
> <https://logbooks.jlab.org/files/2022/10/4061354/summaryPlots_1999_sbs_gem.pdf>
> At 96 latency ->
> https://logbooks.jlab.org/files/2022/10/4061357/summaryPlots_2000_sbs_ge...
> <https://logbooks.jlab.org/files/2022/10/4061357/summaryPlots_2000_sbs_gem.pdf>
>
> At 102 latency, we see a peak is at 5th time sample. At both 108 and and
> 96, we clearly don't see a distribution and suggests that the latency is
> off.
> We will ideally want to peak at the 4th time sample just like the BB GEMs.
> So we will decrease the latency by 1 unit and see.
> https://logbooks.jlab.org/entry/4061417
> _______________________________________________
> Sbs_gems mailing list
> Sbs_gems at jlab.org
> https://mailman.jlab.org/mailman/listinfo/sbs_gems
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/sbs_gems/attachments/20221017/9a7a2dcf/attachment-0001.html>