[Pansophy] FW: L2PRD-CAV-HOM-TUNE traveler data

[Megan McDonald]

From: Naeem Huque <huque at jlab.org>
Sent: Monday, April 27, 2020 4:39 PM
To: Peter Owen <powen at jlab.org>
Cc: Anna Shabalina Solopova <shabalin at jlab.org>; Danny Forehand <forehand at jlab.org>; Megan McDonald <megan at jlab.org>
Subject: Re: L2PRD-CAV-HOM-TUNE traveler data

Hi Peter,

The data that is uploaded to the shipping and assembly travelers is a different set than what would be uploaded here, correct? If that is the case (i.e. we wouldn't just be repeating the data entry) I'd like this traveler resurrected and filled out for the other CMs. The fact that HOMs detune themselves so much warrants an additional data point.

Please revise the traveler into a format that can be automatically loaded

Thanks,
Naeem
________________________________
From: Anna Shabalina Solopova <shabalin at jlab.org<mailto:shabalin at jlab.org>>
Sent: Monday, April 27, 2020 4:12 PM
To: Peter Owen <powen at jlab.org<mailto:powen at jlab.org>>; Danny Forehand <forehand at jlab.org<mailto:forehand at jlab.org>>
Cc: Naeem Huque <huque at jlab.org<mailto:huque at jlab.org>>
Subject: RE: L2PRD-CAV-HOM-TUNE traveler data


I think automation is great.  Please, do rewrite that traveler as you wish. It's clearly obsolete. It may be not so important to know who was the person tuning, assume whoever usually got the task did it, if Naeem and Danny agree.



Naeem,  how do you want to proceed?



From: Peter Owen <powen at jlab.org<mailto:powen at jlab.org>>
Sent: Monday, April 27, 2020 4:10 PM
To: Anna Shabalina Solopova <shabalin at jlab.org<mailto:shabalin at jlab.org>>; Danny Forehand <forehand at jlab.org<mailto:forehand at jlab.org>>
Cc: Naeem Huque <huque at jlab.org<mailto:huque at jlab.org>>
Subject: Re: L2PRD-CAV-HOM-TUNE traveler data



Hi Anna,



That's a lot of back logged data. The data files have been stored in M:\asd\asddata\LCLS-II_HOM\CM    . Though the RF data is present, some of other data for the traveler such as RF technician, workstation, or any relevant comments, are not recorded.

I have always added HOM data to the assembly and shipping travelers as necessary, but forgot about this traveler. I suppose it could be possible to automate taking the data from this folder to the traveler, but that is a question for Valerie/Megan. There is a consistent file structure in how the data is stored for each tuning of each module. I'd be happy to help them import from that if needed.



Peter

________________________________

From: Anna Shabalina Solopova <shabalin at jlab.org<mailto:shabalin at jlab.org>>
Sent: Monday, April 27, 2020 3:57 PM
To: Peter Owen <powen at jlab.org<mailto:powen at jlab.org>>; Danny Forehand <forehand at jlab.org<mailto:forehand at jlab.org>>
Cc: Naeem Huque <huque at jlab.org<mailto:huque at jlab.org>>
Subject: L2PRD-CAV-HOM-TUNE traveler data



Hi Danny and Peter,

The HOM tuning traveler from ages ago, L2PRD-CAV-HOM-TUNE, was supposed to be one where data from Peter's VI is uploaded, as well as the spreadsheet with the peaks and notch values. Turns out, only 6 were ever filled.... I haven't looked at it since Peter took over HOM stuff. Could any of you track and trace if the data from tuning was saved elsewhere in the system, please?

Naeem has a route to either close and abandon the travelers or fill 15 CM worth of data....



Thanks.

Anna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20200428/04a84ca3/attachment.html>