<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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);">
All,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<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);">
Re-including Hall folks here for comments.... as they stare at and understand their Halo counters/ Detector rates better than I. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<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);">
One puzzling thing I noticed while digging is that the Upstream counters are quiet, the midstream only marginally increased on one counter (bottom), and the Downstream are noisy the right counter has almost double the counts as any others. If we had significant
halo coming into the Hall wouldn't all counters have increased, or is this due to the focusing?</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<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);">
I don't think pre-buncher is worth touching as I could find no reason in the archiver to believe that it would do any good, and if it did we would likely have to put it back anyways, for the other Halls. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<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);">
So, additional items to add to the list are:</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<ol>
<li></li><li>Injector check and retune has also come to mind .... alot a few hours for Yan/ Alicia to check the front end? We know the C beam has a tail from logs the other day, and we continue to have 0R08 BLM trips. ( 1 hr - 2hrs ) <br>
</li><li>Re-steer at 2R->3S, this should be done regardless of the Hall B situation. After we re-steered at 2R after separation check I saw that Swing shift had difficulty with 7S01 BLM trips. The 3S01 vertical position isa at +7-8mm. I think we can improve this
some. I also noticed that for some reason there is another BComm of design by 0.33% ( MXS3R ), maybe fine but I would like to check this. ( 30 min to 1 hr ). </li><li>Given my above statements about no upstream counts. It could be possible that we should narrow our focus into the Hall from 2C24 to the target. Is it possible we are hitting the collimator that sits after the tagger magnet? Does the hall have insertables
we don't know about? A valve, harp, or viewer simi-stuck in the beam line? We should simply cycle all insertables in the B line. (10 min) </li><li>We could simply try angle and position changes into the target ? It looks like things got really noisy after a target change in the hall on the 15th, probably a coincidence (<a href="https://logbooks.jlab.org/entry/3835820" id="LPlnk901337">https://logbooks.jlab.org/entry/3835820</a>)
. I believe that the Midstream counters sit around the Target somewhere, and Downstream counters are after CLAS. So perhaps we just have a bad angle going into the Target? ( 1hr )<br>
</li><li>Try focusing effects from the 2H00 and 2H00A quad pair that Tief/ Yves had mentioned in previous emails. Do we need to back up to the Tagger to do this? ( 1-2 hrs ). </li><li>Open to other ideas from anyone.....<br>
</li></ol>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
-Brian</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size: 11pt;" data-ogsc=""><b>From:</b> BTeam <bteam-bounces@jlab.org> on behalf of Michael Tiefenback <tiefen@jlab.org><br>
<b>Sent:</b> Thursday, August 27, 2020 9:15 PM<br>
<b>To:</b> Dennis Turner <dturner@jlab.org>; HyeKyoung Park <hkpark@jlab.org>; bteam@jlab.org <bteam@jlab.org><br>
<b>Subject:</b> Re: [BTeam] Fw: [EXTERNAL] Follow up on Hall B Halo Rates Troubleshooting</font>
<div> </div>
</div>
<div dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We've had hints of scraping in 3S01 and vicinity. It may be useful to test the sensitivity of 2R vertical (perhaps horizontal as well) steering. The orbit locks steer the beam in the accelerator with some delay, not coordinating within the set of locks.
This flutter will move the beam by small amounts during the (very minor) steering tweaks. If no effect on count rates is seen, then perhaps scraping is not the cause of the Hall B background rates. Other diagnostic tests near the Hall B target are under
consideration, too.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Michael Tiefenback<br>
</div>
<div>
<div id="x_appendonsend"></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size: 11pt;" data-ogsc=""><b>From:</b> BTeam <bteam-bounces@jlab.org> on behalf of Dennis Turner <dturner@jlab.org><br>
<b>Sent:</b> Thursday, August 27, 2020 21:03<br>
<b>To:</b> HyeKyoung Park <hkpark@jlab.org>; bteam@jlab.org <bteam@jlab.org><br>
<b>Subject:</b> Re: [BTeam] Fw: [EXTERNAL] Follow up on Hall B Halo Rates Troubleshooting</font>
<div> </div>
</div>
<div dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Separation has already been rechecked. First pass separation was tweaked, but no improvement for Hall B beam resulted:<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<a href="https://logbooks.jlab.org/entry/3835771" id="LPlnk774024">https://logbooks.jlab.org/entry/3835771</a></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<a href="https://logbooks.jlab.org/entry/3835775" id="LPlnk487943">https://logbooks.jlab.org/entry/3835775</a></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dennis<br>
</div>
<div>
<div id="x_x_appendonsend"></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size: 11pt;" data-ogsc=""><b>From:</b> BTeam <bteam-bounces@jlab.org> on behalf of HyeKyoung Park <hkpark@jlab.org><br>
<b>Sent:</b> Thursday, August 27, 2020 7:40 PM<br>
<b>To:</b> bteam@jlab.org <bteam@jlab.org><br>
<b>Subject:</b> [BTeam] Fw: [EXTERNAL] Follow up on Hall B Halo Rates Troubleshooting</font>
<div> </div>
</div>
<div dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
FYI</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I presume BTeam has been pondering the results of tests and analysis.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">Talk to you tomorrow,</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">HyeKyoung </span></div>
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="x_x_x_appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_x_x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size: 11pt;" data-ogsc=""><b>From:</b> mhattawy@odu.edu <mohammad.hattawy@gmail.com><br>
<b>Sent:</b> Thursday, August 27, 2020 6:21 PM<br>
<b>To:</b> Brian Freeman <bfreeman@jlab.org>; HyeKyoung Park <hkpark@jlab.org>; Stepan Stepanyan <stepanya@jlab.org>; Kuhn, Sebastian E. <skuhn@odu.edu>; Paul Vasilauskis <vasilaus@jlab.org>; Mike Spata <spata@jlab.org><br>
<b>Subject:</b> [EXTERNAL] Follow up on Hall B Halo Rates Troubleshooting</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div>Dear HyeKyoung and all,<br>
</div>
<div> Following up on the effort of understating the rates increase we see in Hall B and the logbook entry from Brian
<a href="https://logbooks.jlab.org/entry/3835655">https://logbooks.jlab.org/entry/3835655</a>. Brian reported on checking the laser phase on FC and the sensitivity to the 2C09 position. Unfortunately, we did not improve the situation and the rates are still
increasing forcing me to reduce the beam current to 170 nA (from 180 nA). <br>
</div>
<div><br>
</div>
<div>Brian mentioned additional possible tests in his summary: <br>
</div>
<div>1. Check/ Recheck all Separation.<br>
2. Check background relative to pre-buncher settings.<br>
3. Test the sensitivity to Quad changes.</div>
<div><br>
</div>
<div>I would like to ask Brian if he can provide a time estimate for these additional tests and I would like to ask you if you can provide the manpower to continue this investigation tomorrow at the beginning of the day shift.
<br>
</div>
<div> <br>
<div dir="ltr" class="x_x_x_x_gmail_signature">Best regards,<br>
Mohammad Hattawy.<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>