<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Aaron,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
It ends up that THia cancelled tomorrow's meeting. So it will probably be next week,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
when I will present. If you have updates to the slides regarding Brad's comments,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
then you can send updated slides before next Tuesday</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Cheers,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Mark</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Brad Sawatzky <brads@jlab.org><br>
<b>Sent:</b> Monday, October 31, 2022 3:17 PM<br>
<b>To:</b> Aaron Brown <ambrown@jlab.org><br>
<b>Cc:</b> Mark Jones <jones@jlab.org>; Patrizia Rossi <rossi@jlab.org>; Dsg-hallc_nps@jlab.org <dsg-hallc_nps@jlab.org><br>
<b>Subject:</b> [EXTERNAL] Re: [Dsg-hallc_nps] DSG NPS slides</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Aaron,<br>
<br>
Just a few comments/corrections.<br>
<br>
The LED and chiller/thermal systems are *way* behind schedule. I just<br>
want to reiterate that this needs to be an immediate priority (ie.<br>
target of 2 weeks + 1 week contingency at worst, not a best-effort<br>
4+ weeks or 'unknown' as noted in the slides).<br>
<br>
LED boards were delivered to the DSG back in April with the plan that<br>
the controls would be ready by July/August. Chiller controls were on<br>
a similar timeframe. We need to test the bleaching function of the LED<br>
system as well, so the both the chiller and thermal readbacks will be<br>
needed soon.<br>
<br>
The DSG is also needed to support the chiller controls hook-up, LED<br>
controls cabling, and connection to the thermal/humidity readbacks and<br>
associated troubleshooting. This work will happen in EEL/108 and should<br>
be added to your list/ schedule. NOTE: at this point, such work will<br>
interrupt ongoing detector checkout, and will require coordination.<br>
<br>
Do you have all of the cables, connectors, power supplies, etc needed<br>
for those systems? The 5V supply required for the humidity sensors (and<br>
added cabling + power breakout box) was a surprise a couple weeks back.<br>
I know the missing cable and breakout connectors for that power rail<br>
were ordered a few weeks ago. What is the plan for the 5V power supply<br>
itself? Installing these items will require modifications to the NPS<br>
frame and routing cables internally -- that should be added to the <br>
list/schedule.<br>
<br>
<br>
I certainly do understand that the DSG shifted focus from the initial<br>
timeline when NPS was busy working the noise issue, but I am *very*<br>
concerned that the combination of Thanksgiving at the end of November<br>
and the inevitable inefficiencies in December mean a near-term delay<br>
will result in nothing being delivered until mid-January.<br>
<br>
NPS installation is approaching very rapidly. This needs to be an<br>
*immediate* and direct priority if we want to actually meet the<br>
Experimental schedule and avoid chaotic last-minute scrambling.<br>
<br>
<br>
I do understand that we are all oversubscribed. So, if the above<br>
timeframe is not possible due to EIC, MOLLER, CLEO/SOLID, tasks (etc)<br>
that are taking precedence over the upcoming experimental program, then<br>
we need to know that ASAP so we have a chance to respond and/or realign<br>
priorities.<br>
<br>
<br>
On slide 2:<br>
- The DSG will not be working under the production accounts.<br>
- Do not wait for access to a particular account. Please add<br>
start-up instructions for all systems on the wiki here:<br>
<a href="https://wiki.jlab.org/cuawiki/index.php/NPS_Controls">https://wiki.jlab.org/cuawiki/index.php/NPS_Controls</a><br>
- For example, the /home/cdsg/phoebus-4.6.10-SNAPSHOT/phoebus.sh<br>
'HV' script noted on the wiki (or an equivalent, as noted in last<br>
week's email thread) should be adapted to point at relevant paths<br>
for the Phobeus install and the Config files for a given<br>
application.<br>
- The tarball 'phoebus_screens.tar.gz' I received from Brian <br>
- That script can then be trivially adapted to run wherever it needs<br>
to run within the Hall C cluster.<br>
- Similar 'launch' scripts will be needed for each Phoebus application<br>
you note.<br>
<br>
<br>
On slide 3:<br>
- The VME64x crate shown does not have the LED driver modules noted.<br>
- The two modules there are intel SBCs that were just being stored in<br>
that crate a long time back.<br>
- Wrong picture?<br>
<br>
<br>
The associated Phoebus config files for all systems really need to be<br>
version controlled and made available on Github by the DSG.<br>
- We need the backup/reference that will automatically provide<br>
- We will also need to track and merge changes made by both the DSG<br>
and Physics people on their respective systems -- something git<br>
is designed to manage well.<br>
<br>
Startup/Restart instructions need to be documented for all DSG supported<br>
systems. (Add them to the above wiki link, for example.)<br>
<br>
EPICS PVs need to be added to the Archiver and verified. (Please give<br>
them good names and put them under 'NPS' or 'HALLC/NPS' in the Archiver<br>
hierarchy.)<br>
<br>
While I'm running through things in my head, I am reminded of the<br>
required alarm handlers for all of these systems. We've discussed<br>
trip points, visual displays, etc in the past, but I'd like some<br>
clarifications on the low-level implementation.<br>
<br>
Are these alarms (including an audible alarm) integrated into the<br>
respective Phoebus interface? Do they rely on BEAST (commonly part<br>
of the CSS/Phoebus setup)? Do the relevant PVs have the appropriate<br>
alarm-handler fields attached?<br>
<br>
<br>
-- Brad<br>
<br>
<br>
On Mon, 31 Oct 2022, Aaron Brown via Dsg-hallc_nps wrote:<br>
<br>
> Hi Mark,<br>
> Here are a few slides detailing the work DSG is doing for NPS.<br>
> Let me know if there's anything else you need.<br>
> Thanks,<br>
> Aaron<br>
<br>
<br>
-- <br>
Brad Sawatzky (he/him), PhD <brads@jlab.org> -<>- Jefferson Lab/SciComp/F272<br>
Ph: 757-269-5947 -<>- Fax: 757-269-5235 -<>- Pager: brads-page@jlab.org<br>
The most exciting phrase to hear in science, the one that heralds new<br>
discoveries, is not "Eureka!" but "That's funny..." -- Isaac Asimov<br>
</div>
</span></font></div>
</body>
</html>