<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D">FYI… SLAC wants all raw data related to CAV INSPs, TUNE, & VTRF; and CMTF raw data….<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> John Vennekate <hannesv@jlab.org> <br>
<b>Sent:</b> Friday, June 18, 2021 4:05 PM<br>
<b>To:</b> Kirk Davis <kdavis@jlab.org>; Tony Reilly <areilly@jlab.org>; Valerie Bookwalter <bookwalt@jlab.org><br>
<b>Cc:</b> Katherine Wilson <kwilson@jlab.org>; John Hogan <hogan@jlab.org><br>
<b>Subject:</b> HE Cavity Data<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Kirk, Tony, and Valerie,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Megan and Valerie gave me a quick tour through Pansophy the other day. Within that framework we also discussed what kind of access we can provide SLAC (in person of James, he is basically taking over Dan’s part of L2) for the cavity test
data. My understanding is that besides the circumstance that we do not want to give them full access to Pansophy – and with that other project results –, there has also been some discussion about the level of “filtering” we
<o:p></o:p></p>
<p class="MsoNormal">conduct on our side i.e. which data exactly we provide from our measurements at the VTA.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I reached out to James to understand which data he is interested in exactly. His answer (below) mostly reads like “pretty much everything”.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Would it be possible to set up a meeting (next week?) to discuss how we are going to proceed with this? Right now, we usually send them the raw data file from the travelers and I understood this not the way we want to proceed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Maniscalco, James <<a href="mailto:jamesm@slac.stanford.edu">jamesm@slac.stanford.edu</a>>
<br>
<b>Sent:</b> Friday, June 18, 2021 14:26<br>
<b>To:</b> John Vennekate <<a href="mailto:hannesv@jlab.org">hannesv@jlab.org</a>><br>
<b>Cc:</b> Gonnella, Dan A <<a href="mailto:gonnella@slac.stanford.edu">gonnella@slac.stanford.edu</a>>; Katherine Wilson <<a href="mailto:kwilson@jlab.org">kwilson@jlab.org</a>>; John Hogan <<a href="mailto:hogan@jlab.org">hogan@jlab.org</a>>; Fuerst, Joel
D. <<a href="mailto:fuerst@slac.stanford.edu">fuerst@slac.stanford.edu</a>><br>
<b>Subject:</b> [EXTERNAL] RE: Cavity Data<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi John,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Yes, I will be collecting and collating the test and traveler data from the partner labs for the purposes of review by the cavity technical board. I have a GUI that will be populated with this data for quick
study during CTB meetings; the GUI as well as the database powering it will be available to CTB members for their own analysis as well. I understand the concerns about having full access to Pansophy, and in principle I don’t need direct access myself if you
can provide the required data via email or some other method. To reassure you, we have no interest in SLAC folks having access to any information other than the data relevant to LCLS-II-HE and LCLS-II cavities and cryomodules.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">As for the data required, plots will not be sufficient. The success of the project depends on prompt and detailed vendor oversight. As such, the CTB needs to be able to review manufacturing data from the cavity
vendor (geometric measurements, material certificates, EP and furnace run data, etc.), as well as the RF test results from vertical test and cryomodule test (raw data and operator input recorded in the traveler – test location, usable gradient, gradient limiting
factors, comments on multipacting, field emission, processing, etc.), and cavity test preparation information (incoming inspection, cooldown and flux expulsion data, passband modes/tuning information, Qext of antennas, etc.) from the partner labs. Without
this information, the CTB will not be able to effectively carry out its duties to the project.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Critically, the technical board will not be able to approve cavities for string assembly until this information has been shared and collectively discussed for each cavity.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">For the data from the partner labs, if direct access to the internal traveler system for SLAC folks is not feasible (very understandable if this is the case), then I think the simplest way forward is for you
to send via email the RF test data files as well as the information from the RF test, cooldown, and incoming inspection travelers, within one week of the RF test. The one week deadline will be important to avoid delays in vendor oversight actions and approval
of cavities for string assembly. If you are able to export the data from each of these travelers into a CSV file or Excel spreadsheet, that will work for the purposes of the CTB as long as the files are in a consistent format. Perhaps you could send a weekly
summary email with the RF data and inspection, cooldown, and RF test travelers for the cavities that were tested that week.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Another outstanding concern is access to the data from LCLS-II cavities. The RF test data and information from the LCLS-II versions of the above travelers will provide much needed information for LCLS-II-HE,
especially for points of concern that were not fully addressed in the earlier project. As an example, LCLS-II-HE will operate in the multipacting band of the cavities, and so multipacting processing is of great concern; we have strong reason to believe that
much multipacting in LCLS-II went unprocessed since the target gradient was only 16 MV/m. It will be a boon to the project if we are able to deeply study LCLS-II cavities retroactively to understand how often and how severely multipacting was present. This
can only be done effectively by fully and transparently sharing the relevant data from both partner labs among all members of the cavity technical board.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for your understanding, and I hope that we can all come to a mutually agreeable path forward. I think that access to the LCLS-II-HE and LCLS-II travelers in Pansophy would be easier than having you
email me each time a cavity is tested, but if it’s not feasible then it’s not feasible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">James<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> John Vennekate <<a href="mailto:hannesv@jlab.org">hannesv@jlab.org</a>>
<br>
<b>Sent:</b> Wednesday, June 16, 2021 2:04 PM<br>
<b>To:</b> Maniscalco, James <<a href="mailto:jamesm@slac.stanford.edu">jamesm@slac.stanford.edu</a>><br>
<b>Cc:</b> Gonnella, Dan A <<a href="mailto:gonnella@slac.stanford.edu">gonnella@slac.stanford.edu</a>><br>
<b>Subject:</b> Cavity Data<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hey James,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I understood you will basically play the role of the book keeper for all cavity test data for the production of HE, correct? Could you let me know what data exactly you need to pull from our system?<o:p></o:p></p>
<p class="MsoNormal">The reason I am asking is that our OPs side is currently working on an exchange platform for external users within pansophy. I assume your account has already been deactivated(?). There are certain concerns that won’t allow us to give external
users full access to all our testing records.<o:p></o:p></p>
<p class="MsoNormal">So far, I believe, we are only considering to provide plots of the measurements we took. So, please let me know if that suffices and what exactly or else, respectively, you require.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I remember the quick show of your nice Matlab tool for cavity evaluation. I assume that is supposed to be fed by that data, correct?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>