If ypou now check the actual values in the aida10 Options screen are the correct ?

It can happen that corruptions once loaded are propagated when Options are generally saved. 

Looking at the dates the files were modified does that make sense to you. It doesn't look as if the corrupted database was changed except when they all were ? Can you check ? Have you checked the other Options files ? I seem to recall that RIKEN AIDA had a program to to this ?

Testing merger with 3 DSSDs connected, with thresholds of 10 (slow comparator), 2 (HEC) and 255 (fast discriminator)

Merger handling rate of 1.6 million events per second comfortably. Forwarding to MBS fine.

Network usage: 130 Mbps (AIDA network) and 20 Mbps (MBS network)

Two raspberry pis:

nnrpi1 - FEE64 system consoles
nnrpi2 - AC Mains Relay & CAEN HV

Startup:

1. Plug in micro-USB on pis
2. Connect via ssh: ssh pi@nnrpi1  or ssh pi@nnrpi2
3. Start MIDAS:
cd /MIDAS/TclHttpd/Linux-arm
./TclHttpd-server

4. Connect from aida-gsi web browser
http://nnrpi2:8015 - For AC Relay Control
http://nnrpi1:8015 - For Pi Monitoring (Get list of USB terminals, Connect)
-> Parse USB log for details to check if all FEEs have finished booting completely or not

5. For CAEN HV connect via ssh/X (ssh -X pi@nnrpi2) and run
putty &
Opens putty window to connect to the CAEN HV module (Serial /dev/ttyACM0)

If you have a GSI account it should be possible to connect to aida-gsi remotely via the following
SSH into lx-pool.gsi.de with GSI Linux username/password (ssh username@lx-pool.gsi.de)
Then SSH into aida-gsi via ssh npg@aida-3

Currently

- 1 DSSD and Plastic is in the AIDA snout, which is not mounted

- The FEEs are offline due to a water supply issue, this will be repaired early 21/03/2019

- The pis & aida-3 are online

The water interlock also didn't clear, which will be investigated

Ideally installation can be completed tomorrow but this depends on water

The AIDA water system has been repaired and not leaking.

The interlock did not light immediately, but power cable reconnected to box and now it works.

All 12 FEEs powered up, and temperatures are OK.

Passed ASIC checks and system wide checks - now checking cabling and to mount snout.

FEEs have been on this morning, temperatures attached

Leakage current attached

the DSSD is attached to the following AIDA modules:
Beam Left: 10
Beam Right: 12
Bottom: 11
Top: 9

MIDAS Servers on, will be looking at resolution (pulser)

Pulser widths of AIDA modules, resolution is fairly typical. AIDA09 still noisier than other DSSD channels.

Figure 1: Picture of pulser peaks
Figure 2: Raw waves (AIDA01 did not calibrate, so AIDA02 used instead as "non DSSD module")
Figure 3: Good Events

Fast comparator threshold (LEC/MEC) changed to 0xFF

AIDA09 seems noiser than before(?) but is known to be noisy.

AIDA01:  24.22

AIDA09: 205.21

AIDA10: 88.60

AIDA11: 63.33

AIDA12: 102.69

Extra FEE information:

HV braid (0 V) goes into FEE10 (beam left) with LK1 jumper
HV core (-160 V) goes into FEE09 (top)

Could be related to noise in FEE09?
Both these FEEs have higher rates too

Other setup information:
According to the switch in S4, the AIDA workstation is only connected via 100Mbps rather than 1Gbps. (Fig 1)

Plastic is inside the snout, but is not yet connected to the electronics yet
Figures 2-4 Show the DSSD & Plastic in the Snout. Plastic is far upstream solely to ensure plenty of ribbon cable

End of the day - Detector unbiased and FEE64s turned off for the weekend as they won't be monitored.

Water will remain on.

Plastic electronics have now been installed.

Water is not leaking still.

FEE64s powered on at 15:00 to test MBS connection (fig1: temperatures)

MBS relay connects to MBS server OK...

AIDA Merger does not accept any data... (links with data reads 0) and lots of timestamp errors in log? (Figs 2-4)

Startup procedure incorrect?

Otherwise things still OK.

Fig1: FEE temperatures from 26.03.2019  all OK

AIDA has been on today and merger setting fixed (see previous ELOG entry https://elog.ph.ed.ac.uk/DESPEC/36)

Still diagnosing issues with MBS (figure 2) but local data acquisition should be functional.

Detector has not been biased.

MBS is currently configured and accepting data:

x86l-94 : AIDA Foreign data receiver

x86l-4 : DESPEC Time sorter

The time sorter is complaining about AIDA time warps (around 1 Hz) it is assumed this is related to other merger / timestamping issues being worked on by Vic

Pulser settings during April run:

Rate 2Hz
Delay 250 NS
Amplitude 1 V
Fall 1 ms
Polarity Pos
Pulse Top Tail
Attenuation 1X
PB5 Pulse On
Clamp Off

it seems a FEE somtimes enters a confusing state and stops sending data
the current merger requires all FEEs to be active and so this stops the entire system from proceeding.

On MIDAS the page reports the module is "undefined"

On the TTY console (PUTTY) it returns: do_GetState returned z=0 and 8

Resetting the DAQ in question via MIDAS works (Putty logs of the stages shown) and then the merger resumes without trouble.

Update on issue #48 - the "confusing state" is that the FEE has restarted and hence is undefined again.

An attached TTY log from the pi shows that the module is kernel panicking.
I have seen a couple of FEEs panic with the same error now.

(NB. The Day/time of the logs is wrong as the pi does not have the correct time - pis dont have a RTC or Internet access so the time isn't corrected)

Temperature of the modules is fine.

Aida is currently powered off (and I am away from GSI)

New merger has been worked on by VP which fixes the timewarp issues and MBS integration.

Currently no WAVE capture is supported, VP will re-add WAVE histogramming for startup testing.

10.05.2019 - Pulser walkthrough
-> Pulser rate 50 Hz
-> 1 minute per 0.1 V (0.1 to 1 V)
-> extra time on 1 V

With this 95% of channels calibrate easily (good statistics)
Issue: ~16 channels (most of ASIC3) in FEE10 are horrificly noisy. Not calibrated

Fig 1. Pulser of FEE1 (no DSSD)
Fig 2. Pulser of FEE9 (DSSD)
Fig 3&4. Pulser of FEE10 noisy channels

Future TODO: Will investigate WAVE data and look if issue can be found.

20.05.2019 - Alpha walkthrough
-> Pulser off
-> FEE10ASIC3 has readout off & discriminator masked
-> Slow threshold 0x64
-> Fast threshold 0xff
-> HEC threshold 0x2

File is nyx/gamma/nhubbard/AIDA/alpha_bg_200519_

Rate is approx. 1MB/s still of WR timestamp data.

(NB, MIDAS Alpha walkthrough before beamtime I see no alpha events in!)

Fig 5: Temps
Fig 6: Stats
Fig 7: Merger Stats
Fig 8: MBS Stats

The latest version of MIDAS has a new page to check the WR timestamp of each FEE.

In AIDA Hardware control click: GSI White Rabbit Control
In expert options click: Collect all Timestamps
Verify every FEE has a good timestamp.

Currently AIDA's interlock is off (no lights) and hence AIDA cannot be powered on. Under investigation - power supply has been replugged but seems ok.

Update: It seems the interlock is correctly stopping AIDA from being powered on due to high humidity on the cooling lines. Am currently trying to verify the temperature with GSI technical staff