[BTeam] minutes of meeting 03/21/2020

[Brian Freeman]

We spoke a few weeks ago about doing option 1, to check for reproducibility of the machine as well. If the machine comes up and restores well it is good knowledge.  Having a machine that has already shown to reproduce, means that we can back up then and do the M56 piece in Arc 1 and know that we can back out if needed. Once we have tested the Arc 1 Optics, and how bad the rest of the machine is we can then assess whether or not to install the optics, or back out.  It also allows us to, delay the Arc 1 piece for future beam studies, and move on to Physics if we run short of time. Just my 2 cents, and what I thought we had already decided upon.

Sorry I missed the meeting this afternoon.
-B
________________________________
From: BTeam <bteam-bounces at jlab.org> on behalf of Yves Roblin <roblin at jlab.org>
Sent: Tuesday, April 21, 2020 2:11 PM
To: bteam at jlab.org <bteam at jlab.org>
Subject: [BTeam] minutes of meeting 03/21/2020

We discussed the machine restore. Two plans were presented.

Option 1), spin up to 5 passes restoring from previous setup then launch into beam studies
to assess the correct M56 for ARC1 but not download it.

Option 2) spin up to 3R, try all the M56 lattices to find which one results in least correction. Download it, match it and resume setup.

If going through option 2) also readjust the bcom from the start  so that higher passes dont end up 2.5 % off.

Using the archiver, we can construct a baseline of what the east arc BLM activity was last time we ran with tune beam. We can refer to that to see if we reduce loss

Both option 1) and 2) take about 2 weeks but option 1) can be shortened if we drop the beam studies since we can always do some of that later during regularly scheduled beam studies.

Before spin up, we can walk the tunnel to check for misplaced/fallen shims in dipoles as well as any alignment issues on the east side.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/bteam/attachments/20200421/42b6ef60/attachment-0002.html>