Attached is the signal mapping that will be used for the BEAVERTAIL test.

Note we plan to use 5 FEBEX cards to run 8 Si detectors because we will only use one pocket setup this time. In future, a solution using only 4 FEBEX cards will need to be found.

Bias Select: In general, higher bias resistors -> lower electronic noise. However, higher resistance = larger voltage drop due to leakage current.
Our natural leakage currents at operating voltage of 60V range from 18nA (MSPad 15A) to 320nA (Design I 13). At maximum expected rate of 100Hz, our signal induced leakage current is 
8.9nA. Hence our voltage drop range is 0.54V to 6.6V with 20MOhm resistors.
Since we are not electronically noise limited with GeV signals, we decided to choose the lower resistance in case any detectors have bad leakage currents to ensure a good comparison.

For Silicon detectors: p-side collects positive signals, n-side collects negative signals.

Finally, the expected signal energy for each detector is:
 - 1st Si pad -> 2.2GeV
 - 7th Si pad -> 2.5GeV
 - CsI scint  -> 1.3GeV
 - GAGG scint -> 0.9GeV
 - BGO scint  -> 129MeV
As a result, all Si preamps were set to 5GeV max range (MSI#1 Ch1-8 & MSI#2 Ch1-4). CsI & GAGG will use 4GeV range preamps (MSI#2 Ch7-8). BGO will use 330MeV preamps (MSI#2 Ch5-6).

Attached is the final MSI-8 preamp setup using the above settings.

Three terminals/processes are required to record data on a local machine.
1. log in x86l-131. 
	cd to '2021-beavertail/febex3-x86l-131'
	'resl' to clear, then run 'mbs'
	'@startup' -> initialises mbs by running startup script,
	'show acq' gets status, check if there are triggers incoming

2. new terminal on lab machine, cd to /data.local2/2022_beavertail
	to record data, run ./rawDispRFIO64-wheezy, then data record is listening
	bacl to mbs terminal, to send data, '@connect.scom' -> this a a connection script to connect mbs to RFIO
	@openfile.scom -> opens data file to record and automatically names them run####.lmd. 
	@closefile.scom -> closes file and stops file writing
	'show file' show connection to file, and whether its open/closed
	'type event' shows header, 1 words = related to data readout. -v shows full event output.

3. monitor with go4
	cd ~/beavertail/go4/CsISiPHOS_febex/
	source /u/litv-exp/go4login
	go4 x86l-131.hotstart

Our DAQ machines are x86l-131 (DAQ-1), x86l-124 (DAQ-2), x86l-128 (Time-sorter)

litv-exp has /beavertail folder for our testing.
x86l- DAQ computers have remote folder kept somewhere. These will run.

To login remotely: Log into lx-pool.gsi.de with litv-exp user:
ssh -XY litv-exp@lx-pool.gsi.de
From lx-pool you need another tunnel: ssh lxg1050
From there (or any other lxg-machine) you can do: ssh x86l-131

Beam: 208Pb(82+), 269.0 MeV/u, ~2*10^7 ions in ESR

Position pocket outside: GE01DD2AG (A= aussen, outside)
Position -126mm outside (very left), beam at ~-15mm

- BGO runs
electron cooler current: 20 mA (at ~2:00 am) (SC06): Moved pocket to -20mm
run005-033 with traces on. runs034-037 no traces rate is 1.2kHz
At ~2:35am (run038) changed e current to 100 mA, rate increase to 3kHz.: 
run038-080(?) no traces. run080-117 incl traces

- GAGG runs ~6*10^6 ions
Pocket at -20 mm, e current at 100 mA
Moved pocket to -50mm, 200 mA e current
run0114 - run0143 incl. traces
run0149 - run0157 no traces -> moving detector in/out
run0158 - run01?? cooler voltage changed from 100mA to 200mA

- large CsI
~2*10^7 particles in ring
100 mA e current
run0167 - run0197 incl. traces. Moved detector position from -70mm to -20mm in steps of 10mm
run0??? - run0210 no traces. Status detector pocket.

Attached is the detector arrangement for the 3 setups used during the tests.

Here were the f_user.c choices we implemented for this experiment.

Ln029: No white rabbit time stamp available so commented out. This needs to be done in the Go4 analysis script too.
Ln087: We used SFP 1 (random port choice) with 5 FEBEX cards (see signal map)
Ln104: We controlled traces.
Ln163: Channel control: we used 0x91000000 (all enabled,etc) for positive signals, 0x81000000 for negative signals.
Ln191: Sparsifying turned on for all channels.
Ln217: Trigger enabled as OR of pads 2, 4, and 6 + PD front and back: 0xef00, 0x0000, 0x00ef, 0x00ef, 0xc02a.
Ln257-261: Thresholds set to 0x85f as value that partially suppressed our pulser. Tbh, thresholds didn't seem to make an impact to our signal so we just left it at that.

In the previous signal map, I incorrectly mapped the DSSD channels. To correctly read out the DSSD for the new test, we will swap the Lemo cables into the MSI-8, rather then messing with the flange. Hence, plug the old labels into the new channels as outlined 
in the attached table.

Uwe and I were able to get some noise testing done before the ESR was closed with asbestos exposure. We used the new flange so didn't address any issues with the old flange. Our main findings were:
   1.	majority of noise comes from the connection to the ESR. Compare the two scope pics attached with a) the detector isolated from the ESR, and b) the detector in the pocket. It is clear that the large high-frequency spikes of amplitude 40mV plus some low 
frequency modulation is coming from the ESR.
   2.	The signal loop for the MS Pads is through both the MPR-32s and the MSI-8s, so ensuring those preamps are collectively grounded is paramount. Having a short grounding cable that connects all of them to the NIM crate containing the preamp power supply 
is ideal. Wrapping in aluminium foil also seemed to help.
           a.	Perhaps creating a Lemo to preamp ground signal would also help directly connect the flange to the preamps.
   3.	Shielding of the preamp cables seemed to help a bit, but not a huge amount. It may be worth investigating more the effects of shielding, but my feeling is that the above two sources are more important so shielding may not be worth the hassle.

Remaining tasks to investigate:
   1.	Try and quantify impact of isolation from ESR by wrapping mounting system in Kapton tape. If this makes a big difference, perhaps we can create something more purpose built.
   2.	Quantify impact of noise on our signal from data analysis to see if its worth all this effort.

MSI-8 module details.

MMPR1 card configurations:
   - MMPR1_2000_50_V62hf_HV: 2GeV range, 20/60 MOhm bias resistors. 50us decay time. Batch # 37_20: 1/18 - 16/18.                 Dillmann PLEIADES CFI.
   - MMPR1_1G_25_V62_HV:     5GeV range, 20/60 MOhm bias resistors. 25us decay time. Batch # 42_13: 13/54 - 17/54, 21/54 - 28/54. Old LISA modules.
   - MMPR1_20G_25_V62_HV:    20GeV range, 2/11 MOhm bias resistors. 25us decay time. Batch # 29_13: 33/36 - 35/36.                Old LISA modules.

MSI-8 1+2: All 2GeV cards.

MSI-8 3:   Positions 1-5 are 5GeV cards, 6-8 are 20GeV cards

MSI-8 4:   All 5GeV cards

Attached are photos of leakage currents for the current GAGG and BGO setups.
This setup uses the new flange (blue gas inlet), all pads are biased to +60V, the DSSD to +40V and the SiPD to +100V.
Dry nitrogen from and LN2 dewar was flowing over the detectors.

Attachment 1, GAGG housing. Contains:
   MSPad 17A       - 310 nA
   DSSD 161054     - 249 nA
   MSPad 17B       - 316 nA
   MSPad 17C       - 334 nA
   MSPad 16A       - 339 nA
   MSPad 16B       - 361 nA
   MSPad 16C       - 361 nA
   GAGG SiPD       - 293 nA

Attachment 2, BGO housing. Contains:
   Design-I 14     - 135 nA
   DSSD 121813     - 30 nA
   Design-I 13     - 583 nA
   MSPad 15B       - 78 nA
   Empty           - 
   Design-I 6      - 586 nA
   Design-I 8      - 518 nA
   BGO SiPD        - 162 nA

Last week we tested both the new and old flanges with the GAGG housing set up described in the previous ELog entry.

Performance of the new flange was excellent, with clear signal and low noise contribution. We didn't take any photos of this as it was so textbook.

The old flange we identified as performing poorly in June was installed and we carried out the same pulser tests.
This flange clearly creates a different noise environment and initially showed noise comparable/exceeding the 500mV pulser we were inputting.
A photo of the scope signal from one of the pad detectors is shown in Attachment 1.

We thought this could be due to the separate ground planes the MPR and MSI modules are on on the flange PCB so connected these ground planes together. 
This did not really improve the very noisy signal, but made the MSI-8 slightly worse. All-in-all, no significant improvement.

We noted an electrical connection between the D-Sub connector housings and the L-brackets on the flange, connecting the D-Subs, their signal and grounds directly to the ring.
Isolating them from the flange was as simple as applying some tape to the inside of the bracket.
I installed the old flange in the ESR with the GAGG housing and the noise is dramatically improved. There remains some significant wobble in the signal baseline

I have changed the configuration of Housing 2 (BGO) to account for the detector being fixed (bond wires) and provide a "plug-and-play" housing ready to go for any future experiments.

The detector ordering is as follows:
Slot 1 - Design-I #14 
Slot 2 - Canberra DSSD 121813
Slot 3 - MSPad 15B
Slot 4 - Design-I #13
Slot 5 - Design-I #8
Slot 6 - Design-I #6
Slot 7 - EMPTY
Slot 8 - Design-I #3

Design-I #14 previously fell out of its frame during tests at TRIUMF. Its leakage current is comparable with other Design-I detectors but if real-world performance is different in future this may be the 
cause and the detector should be swapped out.

The housing is also a little warped around the slots for the screws to attach the detector to the end of the flange arm due to overtightening of those screws. This makes inserting a detector into slot 5 very 
difficult for the first ~1cm and should be done with considerable care.

Whilst constructing a new flange to replace the old one, we did some tests again to compare the performance of new vs old flange.
See attached images:
1. Old flange, in the lab, no grounding attempts made, biased, n-sides.
2. Old flange, lab, ground plate connected to flange, biased n-sides.
This comparison shows that for the old flange, connecting the ground plane to the flange improved the 50Hz noise. This was also true in the ESR, so all following screenshots had this 
ground connection.

3. Old flange, in the ESR, grounded, biased, n-sides.
4. Old flange, in the ESR, grounded, biased, p-sides.
5. New flange, in the ESR, biased, n-sides.
Attachment 3 v 5 is an apples to apples comparison. This confirmed that even for the best case scenario, the noise in the old flange is an order of magnitude worse. Note that the n-
sides have the worse profile, and for the old flange, the high frequency noise is almost the same size as the pulser. For the new flange, that same noise can be seen, but much smaller 
magnitude.
Grounding on the new flange made no appreciable difference. But in general, we think connecting the electronic ground to the ESR is the best decision. 

We tested the new new flange using the same setup as in ELOG entry 14. The noise level seemed to be somewhere between the middle flange and the old flange.
See attachments:
1. Best noise conditions (grounding two planes and connection to ESR) on worst n-side pad.
2. Worse noise conditions (no grounding) on worst n-side.
3. Best noise conditions on a better n-side. We were unsure why some n-sides were different though.

Thus, for a final comparison of the flanges (best conditions on n-sides):
 - 2016 flange - noise scale = ~5V
 - 2022 flange - noise scale = ~0.4V
 - 2023 flange - noise scale = ~0.8V

MSI-8 and MPR-16 preamps have nominal differential output ranges of +/-1.8V and +/-1.2V respectively at maximum input (ie 5GeV).
All our FEBEX cards are now modified to accept +/-2V range. If serious pileup occurs, this could make it difficult to disentangle events for the n-sides.

To test whether out preamps satisfied this output range, we attempted to calculate the expected height from a 500mV pulser. This should have been:
 input height * (pulser coupling range / preamp energy range) * nominal output range

Mesytec noted that all coupling components are only tested to be within +/-10%, including the pulser coupling capacitors. Thus exact testing is challenging.
The pulser inputs of our MSI-8 cards are:
MMPR-1: Pulser inputs:
Type: 2GeV Pulser : 330MeV/V
Type: 5GeV Pulser : 330MeV/V
Type: 20GeV Pulser: 1GeV/V
Thus in the attached table, we can see the 2GeV and 5GeV cards are well within tolerance, but the 20GeV card is a bit outside. Thus we should probably expect a large output range from those cards.

We also tested the MPR-16 cards. However these cards do not have a terminated pulser input, and it is not clear to us what impact that would have. In the attached table, it seems to have a pretty consistent 
factor of 4 difference though.  

We took a few lmd-files with different settings of the febex DAQ to provide data for go4 development, when the DAQ is not running.
The files are located at lxg1048:/data.local2/2023_pleiades

timesorter_sparcifying.lmd - both nodes delivering data to the timesorter (sparcifying on)
timesorter_traces.lmd      - both nodes delivering data to the timesorter (sparcifying off)
x86l-124_sparcifying.lmd   - single node data (sparcifying on)
x86l-124_traces.lmd        - single node data (sparcifying off)
x86l-131_sparcifying.lmd   - single node data (sparcifying on)
x86l-131_traces.lmd        - single node data (sparcifying off)

comment: 
Both systems run on a 70 Hz pulser via 4 MesyTec preamps into 3 febex cards.
For unknown reasons x86l-124 delivers more data than x86l-131 when sparcifying is on. However, the threshold settings were not checked.


 

Further PLEIADES tests are to be carried out during E018 and E203. This will be an important test of PLEIADES operation in isochronous mode and provide an opportunity to try better understand the PID 
"handle" seen in the analysis of the data collected in 2022.

PLEIADES detectors will be installed at the ESR in opposing pocket positions after the dipole following the gas-jet target.

Much of the setup remains the same as in the previous tests.

To optimise channel assignments and require only 4 FEBEX cards to fully instrument each detector, slot 7 is left vacant and the final Si pad is positioned in slot 8.
See signal table in Elog https://elog.gsi.de/esr/Beavertail/1 for further clarification re. read out of slot 7/8.

Current detector layouts are as follows:

Detector 1:
Slot 1: MSPAD 17A
Slot 2: DSSD 161054
Slot 3: MSPAD 17B
Slot 4: MSPAD 17C
Slot 5: MSPAD 16A
Slot 6: MSPAD 16B
Slot 7:
Slot 8: MSPAD 16C
Crystal: GAGG

Detector 2:
Slot 1: Design I 14
Slot 2: DSSD 121813
Slot 3: MSPAD 15B
Slot 4: Design I 13
Slot 5: Design I 8
Slot 6: Design I 6
Slot 7:
Slot 8: Design I 3
Crystal: BGO

MSPAD 16C has been installed in slot 8 of housing 1 having had its rear bond wires repaired on the 16 November 2023. 
16C has 3 rear bond wires. 
Full function has not yet been confirmed.

The Go4 parameter file will be updated to reflect the change in active channels before the start of the experiment.

Additional notes:

MSPAD 15C shows some lifting between the carrier PCB and Si chip and, while there is nothing to suggest is isn't fully operational, needs checking before future use.

Design-I detectors 81, 82 and 5 are in the spare housing in the vacuum safe in Jan's container.

DSSD 121812 is in the extra detectors box in the container, but is in the supplier box labelled for DSSD 161054.

PLEIADES detectors were installed in both the inside and outside pockets after the dipole behind the gas jet.

The detector include the GAGG crystal is installed in the outside pocket and read out by DAQ computer x86l-131.
The detector include the BGO crystal is installed in the inside pocket and read out by DAQ computer x86l-124.

Both setups are detailed in https://elog.gsi.de/esr/Beavertail/18

All read out and bias cables are now connected according to the attached signal map (attachment 1).

Detectors mounted to the support arms and flanges are shown in attachment 2.

Both DAQs are places on the outside of the ring, with the inside pre-amps mounted above the inner pocket actuator and their outputs cabled through the space under the ring (attachment 3).

The outer pocket cabling to the pre-amps is shown in attachment 4.

Still to do:
   - bias tests
   - test move pockets in and out
   - confirm signal mapping

The MSI-8 modules were reconfigured to properly instrument the current setup.

For each detector:
   - 7x n-side signals     -> MSI-8 #1(or #3), Ch 1-5 & 7
   - 4x DSSD signals       -> MSI-8 #2(or #4), p-side -> Ch1+2,  n-side -> Ch3+4
   - 2x Crystal PD signals -> MSI-8 #2(or #4), p-side -> Ch7,    n-side -> Ch8

MSI-8 #1 and #3 contain all 1/5GeV range cards and are set to receive -ve signals as input, with 20 MOhm bias resistors selected and 5 GeV range selected.

MSI-8 #2 also contains all 1/5 GeV range cards with all bias resistors set to 20 MOhm.
Ch1+2 are set for +ve signals.
Ch3+4 are set for -ve signals.
Ch7 is set for +ve signals.
Ch8 is set for -ve signals.

MSI-8 #4 contains 5x 1/5 GeV range boards on Ch1-5 and 3x 4/20 GeV range boards in Ch6-8. All channels have the bias resistor jumper closed (20 MOhm for 5GeV cards, 2 MOhm for 4 GeV cards).
Ch1+2 are set for +ve signals.
Ch3+4 are set for -ve signals.
Ch7 is set for +ve signals and a 4 GeV range.
Ch8 is set for -ve signals and a 4 GeV range.

Attachments 1, 2, 3, 4 show the internal configuration of modules 1, 2, 3, 4, respectively.
Attachment 5 shows the pin jumper definitions.

After testing the biasing scheme for all detectors, two problems emerge.

On the inside pocket, one SiPad (SiPad#3 - Design-I 13) shows a linear current response to bias.
Attachment 1 shows a bias "curve" for this detector 0-60V and a clear linear response for both +ve and -ve applied bias.
This is not a diode.
After extensive testing, no clear problem is identified and no clear solution. 
Possibly some bond wire has popped and there is a short.
All other detectors bias as expected with reasonable leakage currents.

On the outside pocket, SiPad#4 (MSPAD 16A) also does not display diode-like bias response.
Attachment 2 shows the bias response of this detector for both positive and negative applied biases.

********************************************
** Setup of DAQ x86l-131 (outside pocket) **
********************************************

Used FEBEX GUI to set thresholds for all channels.
Using ~65 mV pulser input, find 3000/0xbb8 (decimal/hex) to be a robust level where pulser is always seen and the trigger level is well above noise.
We expect much higher real detector signals so this should be an appropriate trigger.

Set channel trigger mask to:
0x0000, 0x,0000, 0x0000, 0xcf57

This will trigger readout on n-sides 1-3, 5, 7, the DSSD and the crystal PD.
(pad in slot #7 = pad 6)
Triggers are turned off for all p-strips, unconnected channels and the n-side of pad 4 since that cannot be properly biased.

See some high frequency noise on all channels so extended integration time of hit finder to integrate this out.
Hit finder params set to:
TRIG_SUM_A 20
TRIG_GAP   10
TRIG_SUM_B 21

Trace length (FEB_TRIG_LEN) is set at 3000 and the trigger delay at (FEB_TRIG_DELAY) 500

Sparsifying turned on so if the hit finder doesn't find at least one hit on a given channel, the trace for that channel will not be saved.

*******************************************
** Setup of DAQ x86l-124 (inside pocket) **
*******************************************

The inner pocket n-sides seem to see more noise and the trigger rate is not as stable -> additional component due to fluctuating noise.
Set up similarly to x86l-131 in terms of hit finder parameters, thresholds etc.

Trigger mask is set to:
0x0000, 0x,0000, 0x0000, 0xcf5b

This will trigger readout on n-sides 1,2,4,5,7, the DSSD and the crystal PD.
Triggers are turned off for all p-strips, unconnected channels and the n-side of pad 3 since that cannot be properly biased.

Data files written to /mnt/raw.data/e0203_e0018.

From MBS computers:
cd exp_mnt/data.ESR/e0203_e0018/run***.lmd

Everything called run*** is from timesorter.
Everything with a number (either 124 or 131) before run is from one of the independent DAQs.

Sample file taken with pulser to inside DAQs (124) and written to 124_run0001.lmd.

The MHV modules are set up for remote control. This can be accessed via the mesycontrol software running on x86l-128.

A configuration file has been save to: esr/usr/litv-exp/DAQ-control/mesycontrol/pleiades_2025_v2.xml

DAQ OPERATION

The files of each MBS node or the timesorter are written to the ESR NAS by the RFIO server.
The server is running on the virtual machine atprfio.gsi.de. 
The NAS is mounted there and we write data to the subfolder: /mnt/raw.data/e0203_e0018/

This folder can be mounted to any x86l-XXX pc using litv-exp user with the shell command
> mountESR
The NAS is then mounted at /esr/usr/litv-exp/exp_mnt/data.ESR 
Which is where you will find the folder e0203_e0018 and the data.

We started inserting the inside and outside detector, see
https://elog.gsi.de/esr/E0203_E0018/46

Outside detector (131): started beam scraping at -40mm, at -35mm no beam left
Inside detector (124): drove it in up to 2mm, no beam scraping seen.

MBS files: run0010.lmd (outside detector, ~14:25)
run0011.lmd (16:50): first inside detector, then also testing outside detector again
run0012.lmd: running now with both detectors in:

inner detector: BGO
device: GE01DD2IG 
position: +20mm
scraping beam: not possible

outer detector: GAGG
device: GE01DD2AG
position: -55mm
scraping beam at: -45mm

The experiment has been running stably during the afternoon.
DAQ rates have remained constant and the frequency of hits in the Go4 has remained 1 hit every ~few mins.

However, leakage currents have increased significantly in most detectors, by up to a factor of 20x times in some.

I find it hard to see how radiation damage could cause this, but using the rule of thumb of 2x current for 8C rise in temperature, this would imply a >35C rise. This also doesn't seem realistic.

I don't currently have any other ideas.

Attached is the current leakage current plot - it is clear they have been increasing linearly since this afternoon.

Due to the continued rise in leakage currents, I have stopped the run, moved the detectors completely back and turned off the 
bias to all detectors.

-X86L-128:transport  :-I- remote output file /mnt/raw.data/e0203_e0018/run0015.lmd closed
-X86L-128:transport  :Rfio server atprfio: closed file after    999.981 MB, open next:
-X86L-128:transport  :/mnt/raw.data/e0203_e0018/run0015.lmd
-X86L-128:transport  :/mnt/raw.data/e0203_e0018/run0016.lmd
-X86L-128:to         :error (no timeout) getting event from node X86L-124,
-X86L-128:to         :exiting..
close file
-X86L-128:transport  :closed file after    338.199 MB written:
-X86L-128:transport  :-I- remote output file /mnt/raw.data/e0203_e0018/run0016.lmd closed
-X86L-128:transport  :/mnt/raw.data/e0203_e0018/run0016.lmd

The settings of the MBS daq during the first data taking with fragments around 194Pb (W.Korten experiment) was not entirely correct:

1. both FEBEX nodes had the very same sub-sytem identifier 0x200. The timesorter did merge the two data streams into the lmd files. Now the events cannot be easily separated/identified, 
because both have the same WR header. The only option to identify which FEBEX was the source for an event might be to look for the actual channels receiving hits, because they are slightly 
different for both arrays/DAQs. This might only work for "good" events though...

2. The trigger signals transmitted to the scaler DAQs (VME & NTCAP) had a different input for both DAQs. The GAGG trigger (outside) was using the FEBEX self-trigger as input only, while 
the BGO trigger (inside) was using the FEBEX self-trigger OR the 10Hz sync trigger as input.

The runs with run number lower than 0016 are affected by the above points.

Now the setup has been changed, for run numbers 0017 and higher the following should be valid:

1. WR identifiers
The BGO DAQ on x86l-124 (inside) does use WR sub-system identifier 0x100
The GAGG DAQ on x86l-131 (outside) does use WR sub-system identifier 0x200
The VME DAQ on x86l-204 does use 0x400

2. transmitted triggers
Both DAQs now transmit only the FEBEX self-trigger to the scaler DAQs.

3. Gate Generator for PEXARIA input
We now use a Gate Generator to provide 200ns TTL signals for the PEXARIA, with the goal of avoiding double trigger/pulses (a known issue of the old EXPLODERs we are using)

4. SPARSIFYING
We turned off SPARSIFYING for both FEBEX DAQs. So 
in f_user.c 
#define DATA_FILT_CONTROL_DAT 0x80
was changed t0
#define DATA_FILT_CONTROL_DAT 0x82

During an access break to the ESR, I made a few tests with the bias scheme to see if we could better understand some of the weird quirks.

Two detectors showed likely shorts during initial setup - these detectors were still cabled to the bias network though. 
If there is a short to ground, we wondered if that could then impact the other detectors on the same MHV4 module.
These detectors were uncabled at the pre-amp end.
No change was noticed we bias was applied again.

On the outside pocket, I also noticed that when one detector is turned off, the leakage currents of the others remain the same amplitude but flip polarity as the other biases down.
I disconnected all detectors from that MHV module and connected them one-by-one and this effect was immediately seen with two detectors connected.
I double-checked the cabling and cannot see anything wrong there.

Please enter the leakage currents from the mesycontrol every ~1h into this Google document:

https://docs.google.com/spreadsheets/d/1Gt1tFHwn4XFrJ5_-nQvTi635UD0aHgN6gCdXDTHQdkI/edit?gid=299353113#gid=299353113

The inner detector was moved into position.
The device control for the outer detector is not responding and I am not an expert/don't know how to make it work.

See ELog: https://elog.gsi.de/esr/E0203_E0018/126

Inner detector (x86l-124 BGO)
Device: GE01DD2IG
Position: +20 mm
Scraping beam: not possible

At 19:00 the timesorter slowed down and stopped responding. at 19:56 the the inner detector was retracted (pulled back further from the beam)

Outer detector (x86l-131 GAGG)
Device: GE01DD2AG
Position: -127 mm
Scraping beam: n/a

This could be an interesting test of the detector leakage current response to being in place (i.e. only the inner detector is in place, do all leakage currents increase or 
only that detector?)

Started taking data with file run0017.lmd @ 17:35.

Will continue to run for a few hours this evening and closely monitor leakage currents.

Go4 is running on x86l-184 connected to stream server.

186Hf now stored stably in the ring.

Will move both detectors in to position.

run0021 taking data during moving process and start a new file once they're in place.

Inner PLEIADES detector moved into position at +2mm.
Again, the outside pocket cannot be moved.

run0022 started 16:26:50.

Run stopped at 16:47:20.

Going to attempt a bias curve on one detector. With the present leakage currents, the voltage drop induced is close to the applied bias voltage.