Win gave me a copy of their "idealized" run plan, which I reproduce
below. It is subject to many many caveats, but indicates how they
would like things to go. Note that they are thinking about a 24
hour cycle, with stores lasting for ~20 hours. Also note that Day
1 may have the luminosity pattern of store 2, rather than starting
at low luminosity.
One thing that is clear is that we will have many long hours in the
Portakamp during this period. Please let me know your availability
during this time, so that I can try to arrange things so that we
don't have people taking 120 hour shifts. [I have not pressed hard
on this before because of the uncertainty in the E811 schedule].
Cyrus
--------------------Start of E811 Schedule---------------------------
E811 Run Plan (1/5/96)
W. Baker
Day 1 10:00 Start shot setup for low t run: 6 on 6 bunches,
Store 1 6E26 luminosity at E0, 1500 hz maximum singles rate
(1/18/96) at 2.8 mm detector positions
14:00 Start low t data taking
Day 2 10:00 Start shot setup for efficiency calibration run:
Store 2 6 on 6 bunches, 1.5E28 luminosity at E0
14:00 Start calibration run for cluster efficiency
23:00 Scrape to 6E26 (store 1 conditions); take low t data
Day 3 10:00 Start shot setup for inelastic calibration run:
5 on 5 bunches, store 1 conditions
14:00 Start inelastic calibration run
Day 4 10:00 Start shot setup for low t run
store 1 conditions
14:00 start low t data taking
Day 5 10:00 Start shot setup for low t run
store 1 conditions
14:00 start low t data taking
until 10:00 of day 6
NOTES: It is estimated that main ring can restore stack running
approximately 50% of the time, depending on conditions of
each store. E811 will determine when to shut off main ring
ramp during each store consistent with restoring stack.
This schedule allows for 70 hours of low t data taking,
approximately 25% of which will be lost to main ring
operation, yielding 50 hours of low t data
-----------------End of E811 Schedule-------------------------------