[Pansophy] L2RB-INSP-HMFT

[Matthew Menia]

Hi Liang,

I have moved the NCRs over. There were no D3s to move.

The sequence numbers for the moved travelers staying the same will not affect any reports. Future instantiations will pick up from that point.

Matt
________________________________
From: Pansophy <pansophy-bounces at jlab.org> on behalf of Matthew Menia via Pansophy <pansophy at jlab.org>
Sent: Wednesday, July 16, 2025 11:15 AM
To: Liang Zhao <lzhao at jlab.org>; Adam Grabowski <adamg at jlab.org>; pansophy <pansophy at jlab.org>; George DeKerlegand <georged at jlab.org>; Earl Mosby <mosby at jlab.org>
Cc: John Buttles <buttles at jlab.org>; Kirk Davis <kdavis at jlab.org>
Subject: Re: [Pansophy] L2RB-INSP-HMFT

Liang,

I can go ahead and move the associated NCRs to L2RB. I will also check for D3s.

I will let you know once I have moved the data.

Matt
________________________________
From: Liang Zhao <lzhao at jlab.org>
Sent: Wednesday, July 16, 2025 11:12 AM
To: Matthew Menia <menia at jlab.org>; Adam Grabowski <adamg at jlab.org>; pansophy <pansophy at jlab.org>; George DeKerlegand <georged at jlab.org>; Earl Mosby <mosby at jlab.org>
Cc: John Buttles <buttles at jlab.org>; Kirk Davis <kdavis at jlab.org>
Subject: Re: L2RB-INSP-HMFT

Got it. Thanks for transferring the data and noting the additional field variable, Matt.

There is another issue associated with moving the travelers from HE to L2RB. HE NCR 718-725 were generated from these travelers, and currently sill in HE. Is there a way to move the NCRs to L2RB as well, keeping them associated with the respective traveler?

Also, the traveler Seq Number seem to stay the same after moving the traveler. Would it be an issue?

Liang
________________________________
From: Matthew Menia <menia at jlab.org>
Sent: Wednesday, July 16, 2025 10:25 AM
To: Adam Grabowski <adamg at jlab.org>; pansophy <pansophy at jlab.org>; Liang Zhao <lzhao at jlab.org>; George DeKerlegand <georged at jlab.org>; Earl Mosby <mosby at jlab.org>
Cc: John Buttles <buttles at jlab.org>; Kirk Davis <kdavis at jlab.org>
Subject: Re: L2RB-INSP-HMFT

Hi all,

The data  from L2HE-INSP-HMFT sequence numbers 364-407 has been transferred to L2RB-INSP-HMFT.

A new field variable called 'PIN_BRAZE_PASS' was introduced in the L2RB version of this traveler. Recommend that the data is verified in the L2RB travelers.

Regards,
Matthew Menia
________________________________
From: Pansophy <pansophy-bounces at jlab.org> on behalf of Earl Mosby via Pansophy <pansophy at jlab.org>
Sent: Tuesday, July 15, 2025 10:19 AM
To: Adam Grabowski <adamg at jlab.org>; pansophy <pansophy at jlab.org>; Liang Zhao <lzhao at jlab.org>; George DeKerlegand <georged at jlab.org>
Cc: John Buttles <buttles at jlab.org>; Kirk Davis <kdavis at jlab.org>
Subject: Re: [Pansophy] L2RB-INSP-HMFT

To all!

I will put a Pansophy service request for moving the travelers to L2RB.

The L2HE travelers are supposed to be exactly the same as L2RB, as per Traveler Author.  This was the agreed inspection plan.
Traveler L2RB-INSP-HMFT was not approved until 7-14-2025 at 4:57PM.

Regards,

 Earl Mosby

Jefferson Lab
12000 Jefferson Ave

SRFOPS; Bldg. 58
Newport News, VA 23606
(757) 269-6467




________________________________
From: Adam Grabowski <adamg at jlab.org>
Sent: Tuesday, July 15, 2025 9:57 AM
To: pansophy <pansophy at jlab.org>; Liang Zhao <lzhao at jlab.org>; Earl Mosby <mosby at jlab.org>; George DeKerlegand <georged at jlab.org>
Cc: John Buttles <buttles at jlab.org>; Kirk Davis <kdavis at jlab.org>
Subject: L2RB-INSP-HMFT

Pansophy, Inspection team,

The HOM feedthroughs that have been going through inspection have been documented against the wrong project traveler. I noticed that there are 44 open inspections for L2HE instead of L2RB. This needs to be corrected. I am hoping Pansophy can help. Please advise.

Thank you,


Adam Grabowski

SRF Test Engineer, L2HE Project CAM

Jefferson Lab
600 KELVIN DR Suite # 8

Mail Stop 55H
Newport News, VA 23606

O: 757-269-7665

C: 360-320-7003

E: adamg at jlab.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250716/7c236a72/attachment.htm>