 Tue Apr 13 14:24:48 2021, TD, S460 information
|
aida-gsi Anydesk 897170655
DESPEC remote working - https://sf.gsi.de/d/a4fb2134e06a450ca777/
|
Fri Mar 5 23:45:41 2021, TD, S452 information 
|
aida-gsi Anydesk 897170655
|
|
Thu Mar 4 11:03:04 2021, NH, S452 Operating Notes
|
Please note the following "quirks" currently present in S452 that are important
[B]a) Strips/Thresholds[/B]
|
|
Tue Jun 14 12:15:33 2022, NH, S450 Archived
|
| All MIDAS files for S450 (/TapeData/S450) have been copied to lustre and archived |
|
Sun Oct 1 11:47:07 2023, TD, S4 cooling water
|
The photographs show the cooling water controls and temperature/pressure gauges outside S4 and the connections used by AIDA within S4. |
|
Mon Aug 5 12:57:48 2019, NH, S4 Conditions
|
Temp: 26 C
Humidity: 50%
Dew Point: ~15 C |
|
Sun Jul 14 16:52:28 2024, TD, S181 R7_38-44 7x
|
| |
|
Sun Jul 14 14:37:53 2024, TD, S181 R6_375-380 6x
|
| |
|
Thu Sep 8 12:31:25 2022, NH, Retrying AIDA DataAcq v10
|
Startup AIDA with ribbon cable connected to aida03 and aida07 for noise
Setup and run with waveforms enabled. Discriminators ADC power etc as default
|
|
Fri Mar 22 13:47:32 2019, NH, Resolution Checks
|
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") |
|
Mon Nov 4 13:17:12 2019, NH, Report: aida10 database corruption
|
Often aida10 database seems to get corrupted (ASIC values are all 0xad)
Unsure why it's only aida10, might be related to weird alpha rate behaviour at the moment.
|
 Tue Nov 5 10:02:45 2019, NH PJCS, Report: aida10 database corruption
|
This looks like the Options not the ASIC data. That will be in the CONTENTS file of the FEE64 named directory within the dated EXPERIMENT directory.
Looks like the latest is at /MIDAS/DB/EXPERIMENTS/AIDA/2019Oct31-13.24.23/aida10 ?
A quick look at this file and it looks normal , not all 0xad ? |
|
Tue Nov 5 10:32:21 2019, NH PJCS, Report: aida10 database corruption
|
Hi, see the attached files in the original comment. I think the BACKUPCorrupt is quite old now.
The Options data gets corrupted and for example the ASIC folder gets set to 'undefined' which I think is why the ASIC data loads incorrectly.
|
|
Tue Nov 5 11:15:41 2019, NH PJCS, Report: aida10 database corruption
|
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 |
|
Mon Feb 17 09:48:34 2020, NH, Report: aida09 Kernel Panic & Lost WR
|
aida09 crashed over the weekend and automatically rebooted.
After the reboot the WR timestamp sent to the merger is in the future and hence incorrect
|
|
Wed Feb 19 10:58:29 2020, NH, PJCS, Report: aida09 Kernel Panic & Lost WR
|
> aida09 crashed over the weekend and automatically rebooted.
> After the reboot the WR timestamp sent to the merger is in the future and hence incorrect
>
|
|
Mon Apr 22 09:03:54 2024, TD, Report: aida04 stops producing data
|
09.14 aida04 stopped producing data - system console output - attachment 1
|
|
Mon Mar 9 12:47:18 2020, NH, Report: Unusual AIDA Timestamp Error
|
Noted using my AIDA event builder code, a timewarp was reported and I noticed the ADC event had a different timestamp LSB to the "WR" markers preceding
it, which I didn't think was possible in the merger as it stands
|
|
Wed Apr 3 12:42:57 2024, NH, Report aida02 WR errors
|
The WR error counter for aida02 seems to consantly rise
Tried reseating cable on both ends, no change
However clock status passed, aida02 has a correct WR timestamp and no FIFO/PLL errors seen |
|
Thu Dec 19 10:11:59 2019, TD, Report - medium - FEE64 panics during boot
|
Some of the FEE64s aida01 .. aida12 panic during boot
|