<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Hi Rolf, all - <br>
<br>
Mark just came by office and we discussed the impact of the reduced running.<br>
<br>
For now, Mark's plan to finish LAD as scheduled, use what time is left in FY25 to run as much of R-SIDIS as we can, and then continue R-SIDIS in the next run period. Looking at the calendar, it appears we would get about 4 weeks this year and the rest next
year.<br>
<br>
So it looks like our mission is to figure out the optimized plan for breaking the running into 2 run periods. During the time period we're looking at next year, Hall A is off and Hall B is at 1 or 2 pass (and Hall D at 5 pass as usual), so that looks totally
compatible with R-SIDIS running at 3,4, and 5 pass. The gradient is scheduled to be slightly different (2.2 GeV per pass), so we would need to tweak kinematics a little I guess.<br>
<br>
Regards,<br>
Dave<br>
<br>
<div class="moz-cite-prefix">On 3/27/25 9:13 AM, Rolf Ent wrote:<br>
</div>
<blockquote type="cite" cite="mid:DM8PR09MB61522589F5D44808A69FFD21D4A12@DM8PR09MB6152.namprd09.prod.outlook.com">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi all,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
not unexpected that we get all kind of turmoil from the year-long continuing resolution situation coupled with uncertainty for FY26. Do the five weeks solely come from R_SIDIS, i.e., what does it mean for how many calendar days or PAC-equivalent days we can
assume? And the issue may also be the alignment of energies, presumably for most of our time Hall A is at the highest energy and we have some choice.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Overall, we should just get some complete scans for R_SIDIS, as whatever we get is new and the world is in eager anticipation. Plus the recent theory calculations start hinting that R_SIDIS may be higher than the naive R_DIS assumption, so we will gather interesting
results either way. So that is my view, we should be pragmatic and make sure we prioritize to always get some R scans out. Same with R_SIDIS in nuclei. Something is better than nothing.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I am sure we can stare at the various kinematics tables to figure something out. But we do need to know the rough idea of days and flexibility in energies?</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Best regards, Rolf</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div dir="ltr" id="divRplyFwdMsg"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> Rsidis-mgmt
<a class="moz-txt-link-rfc2396E" href="mailto:rsidis-mgmt-bounces@jlab.org"><rsidis-mgmt-bounces@jlab.org></a> on behalf of Dave Gaskell
<a class="moz-txt-link-rfc2396E" href="mailto:gaskelld@jlab.org"><gaskelld@jlab.org></a><br>
<b>Sent:</b> Thursday, March 27, 2025 8:55 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:rsidis-mgmt@jlab.org">rsidis-mgmt@jlab.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:rsidis-mgmt@jlab.org"><rsidis-mgmt@jlab.org></a><br>
<b>Subject:</b> [Rsidis-mgmt] FY25 running</span>
<div> </div>
</div>
<div style="font-size: 11pt;">Hi all -<br>
<br>
Douglas Higinbotham announced at the 7:45 meeting this morning that<br>
budget guidance to the lab has arrived, and that the lab will need to<br>
reduce the running for FY25 from 25 to 20 weeks. No word on how this<br>
will be divided amongst experiments, but we should look into options for<br>
reducing needed beam time for R-SIDIS.<br>
<br>
Regards,<br>
Dave<br>
<br>
_______________________________________________<br>
Rsidis-mgmt mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Rsidis-mgmt@jlab.org">Rsidis-mgmt@jlab.org</a><br>
<a href="https://mailman.jlab.org/mailman/listinfo/rsidis-mgmt" id="OWAbb305751-f8ba-81bf-540d-deb721de1ff6" class="OWAAutoLink moz-txt-link-freetext" data-auth="NotApplicable" moz-do-not-send="true">https://mailman.jlab.org/mailman/listinfo/rsidis-mgmt</a></div>
</blockquote>
<br>
</body>
</html>