10 Nov 2019 08:40, Edgar Sanchez, Routine, General, S1 data taking without field
|
Run 1041
Gas pocket: OFF
Fields: OFF |
10 Nov 2019 08:04, Edgar Sanchez, Routine, General, S1 data taking with field
|
Run 1032
Gas pocket: OFF
Fields: drift 500 V/cm, extraction 3.78 kV/cm |
10 Nov 2019 00:06, Yi Wang, Routine, General, morning data taking
|
Run 1022
Gas pocket: ON (thinkness 7mm)
Fields: drift 500 V/cm, extraction 3.78 kV/cm |
09 Nov 2019 09:39, Sam Hill, Routine, General, Evening data taking
|
Run 1016
Gas pocket: ON (thinkness 7mm)
Fields: Off |
09 Nov 2019 07:29, Marco Rescigno, Problem Fixed, MIDAS, this morning problem
|
frontend process still alive but slow, causing lot of rejected triggers.
stopped and restarted the feov1725 process to fix this |
09 Nov 2019 00:13, Xiang Xiao, Routine, General, Morning data taking
|
"ERROR INFO: 10:38:10.924 2019/11/09 [feov1725MTI00,ERROR] [feoV1725.cxx:1048:read_trigger_event,ERROR] Error: did not receive a ZMQ bank after
100.000000 ms. Stopping run."
Emailed to Ben. |
08 Nov 2019 22:31, Marco , Configuration, Hardware, Adding darkside01
|
Wrong MAC address fixed in CERN network setting, now the machine is visible from external network too:
From CERN network (even laptop) can connect by
ssh -XY dsproto@ds-proto-daq2.cern.ch. (same password as local account in ds-proto-daq) |
08 Nov 2019 10:07, Edgar Sanchez, Routine, General, Monitoring Data Taking
|
Run 995
Gas pocket: ON (thinkness 7mm)
Fields: drift 200 V/cm, extraction 2.8 kV/cm |
08 Nov 2019 05:14, Ben Smith, Configuration, Hardware, Adding darkside01 to the network
|
The analysis server from Roma (darkside01) is now connected to the local network. It is not yet connected to CERN.
There are 2 network ports on the rear of the machine:
|
08 Nov 2019 09:09, Ben Smith, Configuration, Hardware, Adding darkside01 to the network
|
The cable has been fixed. Socket 0001/007 is still not active. |
08 Nov 2019 08:35, Ben Smith, Configuration, Hardware, Failed to talk to steering module from DAQ PC
|
I have failed to communicate with the steering module arduino from the DAQ PC.
The steering module has the most bizarre communication protocol of any device I have used:
|
08 Nov 2019 02:48, Ben Smith, Configuration, MIDAS, Enabled dotfile naming in Logger
|
I have changed `/Logger/Channels/0/Settings/Filename` to start with a dot, so files will be hidden until they are complete.
The current value is `.run%05dsub%03d.mid`.
|
08 Nov 2019 02:31, Ben Smith, Routine, Software, New "run type" selection page
|
I made a new page that makes it easier to switch between laser/noise/physics runs.
It handles setting the most common chronobox trigger settings, and the V1725 self-trigger thresholds.
|
08 Nov 2019 02:21, Ben Smith, Problem Fixed, Software, Increased max waveform length that we can take
|
I've increased various thresholds so that we can now take 3000us (3ms) waveforms.
The changes are:
|
07 Nov 2019 23:48, Yi Wang, Routine, General, morning data taking
|
Run 973
Gas pocket: ON (thinkness 7mm)
Fields: drift 200 V/cm, extraction 3.78 kV/cm |
07 Nov 2019 02:34, Sam, Routine, General, Run 966 Laser Run with SiPMs at 65V, 30us trace
|
Laser Intensity: MIN
Threshold: external clock (laser NIM), laser set to 1kHz
Trace length: 30us, 5us pre-trigger |
07 Nov 2019 02:16, Sam, Routine, General, Run 964 Laser Run with SiPMs at 65V, 30us trace
|
Laser Intensity: MAX
Threshold: external clock (laser NIM), laser set to 1kHz
Trace length: 30us, 5us pre-trigger |
07 Nov 2019 02:07, Yi/Marco/Andrea, Routine, General, morning data taking, purity check
|
Run 956
Gas pocket: ON (thickness 7mm)
Fields: drift 200 V/cm, extraction 2.8 kV/cm |
07 Nov 2019 02:07, Sam, Routine, General, Run 963 Laser Run with SiPMs at 65V, 12us trace
|
Laser Intensity: MAX
Threshold: external clock (laser NIM), laser set to 1kHz
Trace length: 12us, 5us pre-trigger |
06 Nov 2019 11:22, Yi Wang, Routine, General, Evening data taking, purity check
|
Not sure if the trigger threshold is correctly set, there is an error:
Traceback (most recent call last):
File "/home/dsproto/online/dsproto_analyzer/threshold_tool.py", line 71, in <module> |
06 Nov 2019 12:28, Ben Smith, Problem Fixed, General, Evening data taking, purity check
|
> Not sure if the trigger threshold is correctly set, there is an error:
Sorry, I made a change to the baseline calculation and forgot to update the threshold tool. It's updated now.
|
06 Nov 2019 05:58, Ben Smith, Configuration, Hardware, CAEN VME Crate DHCP
|
The CAEN VME crate now gets its IP address from the ds-proto-daq DHCP server. To do this, I set the IP address of the crate to 0.0.0.0 (using the front
panel interface) then reset the crate (not just a power cycle - pressing the reset button is required).
|