14:45

New run 55 with:

Right arm at 64.60 mm

Left arm IN at 36.54 mm

MBS working - hopefully

Target 7E11

Injection ca. 5E7

horizontal beam position 8.75 mm

vertical beam position  -5mm

Changed electron cooler set point to 244.2 V

Read value 243.66 V

Collector current 4.31A

Rates OK. Temps OK.

15:00

Detector 0 was noisy. Shook arm. Fixed it.

16:15

Detector 0 was noisy. Shook arm. Fixed it.

There is no beam in CRYRING since 16:05.

16:25

The beam is back but it is still a bit unstable and the operators are still trying optimize it.

17:20

We just did standard detector/electronics checks. Everthing looks OK.

17:50

Take screenshots.

20:50

Detector 0 was noisy. Shook arm. Fixed it.

But now detector 2 seems to have lost the Rutherford peak.

Screenshots taken and attached.

21:05

We did "Check ASIC Control" following Carlo's advise. This fixed the detector 2, but the detector 0 got noisy again. Another movement of the detector fixed the noise again.

22:15

Detector 0 was noisy. Shook arm. Fixed it.

23:05

This run has finished. The cooler voltage will be increased by 0.1V for the next run.

The latest spectra and detector/DAQ status are in the attachment.

Target density this morning had stabalised at 7e11 at/cm2

This is sufficient to test the beam/target overlap using the lifetime of the beam in the ring.

Previous attempt at this method was done at 1.5e11 at/cm2 where lifetime from residual gas and target are essentially the same.

Beam set to bunched. Beam position varied by 1mm and the number of particles in the ring taken from Grafana plots. Particles at injection compared with at dump.

Significantly more beam loss at > 8 mm beam position with highest value at 8.75 mm. This is the maximum we can move the beam.

Test repeated with no target. Same beam loss rate for all positions. We see a clear difference with the target only at positions > 8mm.

Test repeated with original electron cooler voltage Gleb tuned with last night. Same outcome -> cooler voltage has no significant impact on overlap (for 0.1V at least)

Overlap using count rate over 7.5 minutes also tested. DSSD 1 (top right) used as gauge as no beam stripe is seen in this detector. 

At horizontal position 4 mm (previous estimation of overlap) we saw a small increase in counts around 4.7 MeV with the target off compared to target on (76 vs 57)

At horizontal position 8.75 mm we saw a large decrease in counts around 4.7 MeV with target off compared to target on (95 vs 290)

It appears clear the overlap is at 8.75 mm. Future runs will use this as horizontal beam position.

09:30

New run 54 with:

Electron cooler setpoint 244.1 V

Electron cooler read 243.55 V

Collector current 4.3 uA

Right arm at 64.60 mm

Left arm IN at 36.54 mm

MBS working - hopefully

Target 7E11

Injection ca. 5E7

horizontal beam position changed to 8.75 mm

vertical beam position still -5mm

10:30

No beam

ADC stats increased to 250k again same time as beam lost

Detector shake resolved problem

System checks OK

10:35

Beam back

12:17

All system checks OK

12:29

DSSD top left noisy again. Detector shake resolves issuie

14:02

Running smoothly. Temps OK. Stats OK, but write to disk rate x10 usual for unclear reasons.

Target mostly stable. Beam OK, missing some injections occasionally.

14:25

Detector 0 noisy. Shook. Fixed it.

New run 52 with:

Electron cooler setpoint 244.2 V

Electron cooler read 243.66 V

Collector current 4.3 uA

Right arm at 64.60 mm

Left arm IN at 36.54 mm

Target 2E11 fluctuating

Injection ca. 5E7

22;00

Detectors moved out while HKR plays with the beam injection to improve its stability

22;56

All system checks good. Detectors still out. Stats in attachment 1

23:08

HKR still has to call, but I have put detectors back in since they are only operating on injection.

Noticed that from time to time the target density still sparks to E12, and this corresponds to when the temperature drops.

23:42

HKR called back, they found the problem and fixed it. Beam seems more stable, with injections at ca. 5E7

23:50

DSSD0 high stats, cycled the motors to clear them.

00:18

All system checks are fine. Attachment 2-3 with stats and a spectrum

00:38

Spikes in the target got more frequent. Increased temperature to 30.5K and monitor if it helps stabilizing it.

01:52

All checks OK. Target behaving, density 5-8E11.

Attachments 4-5

03:10

System checks OK.

Target consistent

Some beam outages which were quickly fixed by HKR

05:03

System checks OK.

Target consistent

07:00

Lost beam. Detectors moved out

Will likely end run once beam is back and change energy. Do not use data past 7 am

All system checks OK

Interactive Motion Program [workspace 6, display 2]

c                         stop current command(s)
l s by -20 mm             confirm y at prompt
l s by 20 mm              confirm y at prompt
read FakeMotion.dat       confirm y at prompt

15.40 DSSSD bias & leakage current OK - attachments 1-2
       log shows variations due to ambient temperature changes in CRYRING hall

      FEE64 temperatures OK - attachment 3

      WR timestamps OK - attachment 4

      System wide checks Ok *except* global clock (aida16) - attachments 5-6

      ADC data item stats OK - attachment 7

      per FEE64 Rate spectra - attachment 8

      per FEE64 1.8.L spectra - attachments 9-10
       have not been cleared in some time probably - will zero histograms & stats for later review

     per FEE64 1.8.W spectra - 20us FSR - attachments 11-12

     Merger, TapeServer etc - attachments 13-14
      data file G22-222/R51_15

     Motion control - attachment 15

16.01 all histograms & stats zero'd

16.43 online per DSSSD energy spectra - attachment 16

      photographs of CRYRING beam & target diagnostics - attachments 17-22

18.45 Left DSSSDs cycled to clear high rates (c. 250k/FEE64) aida01-aida04 per https://elog.ph.ed.ac.uk/CARME/603

18.49 DAQ continues data file G22-201/R51_27

      DSSSD bias & leakage current OK - attachment 23

      FEE64 temperatures OK - attachment 24

      ADC data item stats OK - attachment 25

      per FEE64 Rate spectra - attachment 26

      online per DSSSD energy spectra - attachment 27

19.00 Beam less stable but most cycles 5e+7 or higher
      Target peaking c. 1e12 dropping to c. 6e11

19.09 CRYRING hall temperature increasing, DSSSD leakage current increasing - attachments 28-29


20.06 Beam less stable most cycles 1-2e+7 or higher
      Target c. 1-2e12

20.15 JM/CB advise changing Lakeshore 336 Temp Controller set point from 29k to 29.5K - done
      Average pressure decreases but rapid variations still observed - see attachment 30


21.00 contacted HKR to improve beam stability - they were alreday working on it but did not know what was causing the problem - will contact on-call CRYRING expert

      cycled L DSSSD to reset rates
      
21,10 beam 0ff - DSSDs OUT

      Increased target temperature to 30K to solve instability that developed again up to E12 density range.


      


 

11:13

ML enabled ring signals remotely.

Used FakeMotion.dat (read FakeMotion.dat from InteractiveMotion.x).

Started run 50.

Cooler voltage moved up by 0.1 V. Did not refocus.

Setpoint = 244.4 V

Read = 243.85 V

Collector current = 4.3 mA

Target thickness 3.4E11 atoms/cm2 now stable

Injection 1-4E7 ions

Realised motors were not in.

Moved detectors in (36.54 / 64.60 mm)

Started run 51. Ignore run 50.

11:46

Realised the left half of DSSD BL was not counting. Checkloaded. Fixed it.

12:00

Fire alarm? Stopped later. EM thinks it is a test.

13:00

Run continues.

Rates OK. Merger OK. Writing to disk back to 200 kB/s. Nothing changed, reasons unclear.

FakeMotion.dat continues

System wide checks as before

Temperatures OK

13:36

Beam lost. Called HKR. Detectors out. Run continues. FakeMotion stopped

14:09

Beam is back. Detectors back in. FakeMotion.dat restarted.

15.10 High rates observed aida01-auida04 ( c. 250k/FEE64)

          Cycled Left Servo

         Rates normal

07:00

After putting the target back, we observe strong periodic (5 s) fluctuations going from 3E11 to 5E12. The reason is unclear. One may warm up the target to solve this, but will ask Nikos later instead.

The target may be a bit too thick for our purposes, and the luminosity will vary greatly depending on injection vs. target fluctuations timing.

Rates OK. Temperatures OK. Merger OK.

System wide checks as before.

07:30

Moved detectors fully out to check elastic and signal rate in this configuration.

Half of DSSD BR was missing. Checkloaded. Solved.

Moved to run 48. Target still unstable.

08:23

Beam issues. Called HKR. Target out.

09:00

Still no beam. Increased target temperature to 29K from 28.5K. It seems the fluctuations disappeared.

Rates as before.

10:22

Beam might be back but people are checking the steerer. Target in. Started run 49. Detectors still out.

10:13

Some beam. HKR is still working on it.

Data rate up to 2 MB/s. Merger events merged matches. However Stats do not seem to have increased. This is the second time I observe this.

RUN 46- started at 00:50

Horizontal beam position = 4.0 mm, vertical beam position = -5.0 mm.

Detectors are Left arm OUT = 36.64, right arm IN =  64.60 mm

Injection at ca. 6E7

Target density 6-7E9

-----

00:51

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 1-2

01:19

Attachments 3-4 waveforms. DSSD0 stats fine

01:33

DSSD0 stats fine

Attachments 5-6 spectra and xy, but I am not sure at which time these are cause I am stupid and apparently the AIDAsort code was not running....

01:56

Restarted the AIDAsort code and noted that stats in DSSD0 were bad again. Another shake. This time no change to the beam on my side.

2:43

All checks fine. Attachments 7-10 (also spectra)

4:01

Notice stats on DSSD0 went bad again. Attachment 11. Gave detector a shake.

Now all system checks OK (Attachements 12-14)

4:19

Just noticed target is oscillating a bit, hitting 1E10. I moved it further in X and Y. Seems to not go below 6E9 in any case.

NOTE: target was on at x=-19899 y=500.

5:17

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 15-18 (also waves)

5:53

Notice stats on DSSD0 went bad again. Gave detector a shake.

6:10

Stats ok in attachment 19, but

Noticed DSSD3 has started to get only a fate of 140 nstead of previous 5500is (similar to what DSSD2 has done earlier- see previous elog). Attachment 20 for the rates.

I have therefore made the Check ASIC control test from the ASIC control tab- attachment 21 with results.

DSSD3 back to normal operations - attachment 22

Tried to double check beam-target overlap by changing beam horizontal coordinate.

In the tablethe counts in the 4000-5200 keV region in each of the detectors are recorded. Counts were taken for a total time of 5 minutes per beam position. Attached are the xy plots.

I think the tests are inconclusive given that the beam in the first three points were not ideal, with many low intensity injections. Moreover, changing the beam often ends up causing the stats in DSSD0 to rise significantly (consequentely needing to shake the detector to go back to normal operation).

After fixing DSSD2, statsin DSSD0 went up again. Stopped the test after shaking again the detector.

----

I have put back the beam at 4mm horizontal. I switched off the target by moving it to x=-10000--->x=-5000 (previosuly X=-19800). Denisity went down to 5E9. However, I decided under Jordan's suggestion to make another test and I put the target back to x=-19800: interestingly the density went up to 5E12 and start oscillating for a while between 5E12 and 5E11.

I did a 10 minute check of counts in the 4000-5200 keV region with this configuration, then switched off the target and did another 10 minutes test. Results:

Re-increase in DSSSD leakage current c. 14-15.00 6.6.24 

There was a significant temperature spike in the CRYRING hall on the afternoon of 6.6.24 which has, partly, recovered - see attachment 1

15:35

Electron cooler voltage set point = 244.3 V

Electron cooler voltage readout = 243.75 V

Collector current = 4.29 mA

All system checks OK

Cycle time = 6 s

Detector positions: left = 36.54 mm, right = 64.60 mm

Target density = 2.5e11

Injection = 3 - 4 e7 pps

15:50

Injection intensity dropped to 1e7 pps

15:54

Injection intensity back to ~4e7 pps

17:30

All system checks OK

Target at 3.7e11

Beam dropped to 1e7 pps

17:34

Beam back to 3-4 e7 pps

19:10

Beam started varying between 1e7 and 4e7. The operators briefly closed the Faraday cup (~30 seconds), the beam is now back to ~5e7

19:25

All system checks OK

Target at 2.6e11

Beam at 5e7

21:25

All system checks OK

Target at 2.7e11

Beam at 4-5 e7

11:05

Confirmed overlap is at 4 mm under new settings.

For unclear reasons, the bottom-left detector is not seeing the halo anymore since around 10:00. Rutherford still visible and if the left arm is moved in the counts at 5 MeV become apparent.

l s by 20 mm, r p in -> 36.5 mm /  64.6 mm

Target thickness 3E11 atoms/cm2. Beam intensity few E7 at injection. Coasting beam mode.

Data rate x10 compared with earlier. Stats as before - the reason is unclear.

Temps & Merger OK. We should be able to tolerate these rates.

Moved detectors in/out to make sure we were not clipping the beam. A few seconds of data may be present in R41_9

11:30

Checkloaded. Detector 2 is now counting more.

Moved to run 42. No other changes.

13:00

Realised cooler voltage was being read via fault g35 divider. Beam stopped

15:00

Switched to F20. Beam back on. Moved to run 43

Electron cooler voltage = 243.155 V

Collector current = 4.29 mA

Beam energy was slightly off, will try again

Started run 39.

We have the 15N+ beam with 426 keV/nucleon. We see a peak in detector top left (mostly) and bottom right, at 4600 keV. We think it is the beam (nominally 6400 keV) after going through silicon dead layer, which however seems to be thicker than expected (expected 0.7 um, but given 1.4 MeV/um energy loss it seems to be > 1 um).

To understand what was going on we first played with detector and beam position.

At 17:28 detectors are fully out, while we are playing with the electron cooler to try to remove this beam halo hitting the detector.

Detector DSSD0 top left periodically seems to get noisier (statistics up to >2E5) and we need to move the detector in and out to go back to normal operations.

------------------

The beam halo in top left detector, as the detector gets moved in, gets elongated in the y direction instead of the x direction, as expected and previosuly observed.

Run 40 started.

18:36

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 1-4

19:43

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 5-8

21:15

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 9-11

00;25

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

-----------------------------------

Movements and observation in xy plot:

- Move right servo in by 20 mm and we see the halo in the top right moving accordingly (attachment 12)

-Move right pneumatic in, saw big increase on bottom right (attachment 13)

-moved beam position down vertical -6 mm and we see reduced beam spot on top left and more on bottom left

-----------------------------------

Beam - target overlap:

We have yet to obtain an overlap

We cannot do this using the beam lifetime as from beam calc the lifetime from the ring is comparable to the lifetime with a target of 1e11 at/cm2

We have tried using Rutherford. However, we will have to move the detectors IN further as the Rutherford peaks at ~3.8 deg.

Possibly we may require other overlap detections from the ring?

I also think the beam requires some optimisation, electron cooler voltage seems to be fluctuating a lot and we see some features on the detectors when moving the beam / detectors as mentioned above.

02:25

The beam intensity has decreased signficantly (by about a factor of five) since about an hour. Operators tried different things, also consulted with Frank Herfurth, but they could not solve the problem.

There is no device which indicates malfunction.

So, during the rest of the night shift we will continue searching for the overlap (of the beam with the target) with the available beam intensity.

03:30

The beam intensity has improved without any aparent intervention.

We have started a new search for the overlap with 20 minute runs per horiznotal beam position.

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

03:40

After changing the horizontal beam position from 0 mm to 1 mm, the bottom right detector lost the Rutherford peak and its position spectrum looks to be half empty.

Moving it OUT and IN again did not change the situation.

There is no reason to think that this behavior has been caused by moving the beam by just 1 mm.

04:10

The beam intensity has dropped again without any apparent reason. So, at the moment we can not continue search for the overlap.

The bottom right detector seems to be counting normally again (also without any apparent reason). 

06:45

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

07:18

Lost beam again. Gleb is looking for it. Moved right detector out temporarily.

System wide checks as before.

Merger OK, Tape Server OK.

Temperatures OK.

Rates currently OK.

Leakage current decreasing.

10:10

Beam is back. Target is unusually thick at 3-5E11

Checking beam overlap.

Merger & tape server OK.

Temps OK.

Rates OK, a bit higher in 01 and 04.

06:45

All system checks OK

Target density 3.4e11

11:50

System checks OK.

No beam in the ring yet. Althoug some injection may be taking place at low intensities

Target density appears much more stable than before.

Density currently just above 1e11 at/cm2

Note maintanace is required to appc025 so anydesk is currently down.

13:13

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 1-5 (also waveforms)

15:00

Merger OK, Tape server OK

ADC data item statistics DO NOT looks as before. NOT OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 6-8

15:16

Notice the statistics for aida01-aida04 (DDSD 0, top left) were counting extremely high in the previous check (attachment 6). Previous rate was 0-1 counts.

We tried ASIC check load three times but not effect on the rate.

We then tried 'shaking the detectors' by moving the left pneumatic in and out again.

Rates go back to normal levels (0-1 counts)

14:20

Target nozzle currently being replaced. No beam

We have decided to switch to 15N beam from now on.

Beam energy for 15N is significantly higher than deuteron beam so we have increased the thresholds (slow comparator) slightly for all detectors to 500 keV (0x32).

ADC data item rates - attachment 1

Run 37 started. Alpha background

Data rate ~ 200 kb/sec

17:44

All system checks OK

20:00

All system checks OK

23:30

All system checks OK

01:25

All system checks OK

03:25

All system checks OK.

Target is stable at 3.5e11, with T1=29 K

05:30

All system checks OK

Target density has slowly drifted down, and is now 1.2e11

14:00

Access to the cave as Nikos and Andreas have begun work on the target.

Run 36 started - pulser walkthrough.

Pulser amplitudes of 8, 7, 6, 5, 4, 3, 2, 1

Attachment 1 - pn channels

Attachment 2 - nn channels

Attachment 3 - pn channels (zoom)

Attachment 4 - nn channels (zoom)

Best pn channel looks like AIDA09 - pulser width 63

Worst pn channel looks like AIDA14 - pulser width 148

Best nn channel looks like AIDA12 - pulser width 58

Worst nn channel looks like AIDA16 - pulser width 246

This is approximately the same as pulser widths before the beam time.

09:30

Target density has not improved despite efforts last night. Mid 10 - low 11 density range. We will try to change the nozzle.

Target nozzle moved to the out position.

HKR allowed access to the cave to turn the compressor off. Target nozzle now warming up.

Internal cave work on changing nozzle expected to start at ~11. In the meantime we will let Wolfgang experiment with the beam settings to try to improve injection intensity.

Detectors have been moved out to fully out position

Run 35 started.

1) STOP DAQ [workspace 2, display 1, browser tab 'Run Control']
   all FEE64s should change status from 'going' to 'stopped' *except* whichever FEE64(s) have a problem - typically their status is 'going' or 'error'

2) Restart Merger by selecting the Merger icon [workspace 3, display 2]
    terminal window showing the startup will popup

3) Setup Merger by selecting 'SETUP' [workspace 3, display 1, browser tab 'NewMerger Control']

4) Start Merger by selecting 'GO' [workspace 3, display 1, browser tab 'NewMerger Control']
     all data links will be inactive (red)

5)   Disable data transfer by selecting 'Data transfer Disable #1 all' [workspace 2, display 1, browser tab 'Run Control']

6) Start DAQ

    Start DAQ by selecting 'GO' [workspace 2, display 1, browser tab 'Run Control']
     check that DAQ is *actually* going - if not repeat 'GO'

7) Check WR timestamps by selecting 'Collect all timestamps' [workspace 2, display 1, browser tab 'GSI White Rabbit Control']
     readout times will be displayed for each FEE64
     check that the readout times are monotonically increasing as you read down the list of readout times - if not, contact expert support

8) Stop DAQ 

    Start DAQ by selecting 'STOP' [workspace 2, display 1, browser tab 'Run Control']
     check that DAQ has *actually* stopped - if not repeat 'STOP

9) Enable data transfer to Merger and TapeServer and start DAQ

    Enable data transfer by selecting 'Enable data transfer Enable #1 All' [workspace 2, display 1, browser tab 'Run Control']

    Start DAQ by selecting 'GO' [workspace 2, display 1, browser tab 'Run Control']
     check that DAQ is *actually* going - if not repeat 'GO'

10) Check data is being transferred to Merger and TapeServer

    Select 'Reload' [workspace 3, display 1, browser tab 'NewMerger Control']
     you should see a non-zero 'current merged data rate' and all links should show as green at least some of the time (requires observation over several reloads)

    Select 'Reload' [workspace 3, display 1, browser tab 'TapeServer']
     you should see 'Blocks written' and 'kb written' counters increase

11) Check AIDA data is being forwarded from the TapeServer to MBS [workspace 3, display 2, command terminal]

12) Restart should now have been successfully completed. Please inform the 'on shift' crew' that AIDA is forwarding data.

    If not, please request expert assistance.

19:08

Beam energy = 3 MeV.

Horizontal beam position = 4.0 mm, vertical beam position = 0.0 mm.

Target density ~ fluctuating

Beam intensity at inj ~ 1.7e7

Detectors are positioned IN. Left arm = 36.54, right arm =  64.60 mm

MBS signals saved from motors code

Histograms and stats zero'd, monitoring code restarted.

Beam in the ring ~ 6 minutes.

Pressure in YR09 E target ~ 4.36e-11 mbar.

Merger error recovered

White rabbit time stamps

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

21:27

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

23:00

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Statistics attachment 5

Merger attachment 6

00:42

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Density is oscillating between E10 and low E11.

attachment 7 is statistics, attachment 8 is temperature, attachment 9 is merger, attachment 10 is spectrum browser.

02:20

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Density is oscillating between E10 and low E11. ( last 15 minutes below 2E10)

attachment 11 -13

From 2:00 target density falls below 2E10 and started decreasing to the E9 range. At 2:40 we started playing with x-y to get to higher density. At 3:30 we are at 5/6E10 and waiting to see if it stabilizesto that or if it needs more playing.

04:06

Target density being 1-2E11 since 5 minutes

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachment 14 statistics, attachment 15 merger

05;53

Target density 1E10, sometimes e11, before going down to low E10 and we need to play a bit with x-y to recover it

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachment 16-18

07:35

Target density 2.5E11, after changiny y position to 1000

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

09:00

Target density has not improved despite efforts last night. Mid 10 - low 11 density range. We have asked HKR to remove beam from the ring and allow access so Nikos can change the nozzle.

Beam off now, access granted. Will begin warming nozzle. Internal cave work on changing nozzle expected to start at 11

Run stopped.

Final monitoring code histogram attached