ID |
Date |
Author |
Type |
Category |
Subject |
113
|
11 Nov 2019 00:37 |
Yi Wang | Problem | MIDAS | cannot connect to rootana |
The connection to rootana is lost.
No data taking can be started. |
119
|
12 Nov 2019 00:16 |
Yi Wang | Problem | Digitizer | V1725 error, runs keep crashing |
09:15:33.955 2019/11/12 [feov1725MTI00,ERROR] [feoV1725.cxx:663:link_thread,ERROR] Exiting thread 3 with error |
120
|
12 Nov 2019 00:23 |
Ben Smith | Problem | Digitizer | V1725 error, runs keep crashing |
It looks like there's a memory leak in the high voltage driver, and we were running out of memory (using a lot of swap). That *may* be related to the recent instability, but I'm not sure.
If things are more stable now, then the memory leak was probably the cause. If not, then we should try stopping the V1725 program, power-cycling the VME crate, then starting the V1725 program.
Yi: restarted the VME crate twice, now it seems like smooth. |
70
|
05 Nov 2019 01:22 |
Ben Smith | Configuration | Digitizer | V1725 board config |
The V1725s have been changed to have board config 0x50 rather than 0x10. This means that they will now trigger on the leading edge of the pulse rather than the tailing edge. There is now much less jitter in the location of pulses in the digitized waveforms. |
4
|
09 Jan 2019 12:22 |
Thomas | Routine | General | V1725 LVDS outputs |
Pierre figured out that NIM crate not working. We now see LVDS outputs from the individual channels firing.
Each set of two different channels is ganged together into a single self-trigger output. By setting the
register 0x1n84 to 3 we enable so that if either input channel fires then the self-trigger for that group fires.
Bryerton provided CDM outputting 50MHz clock; all V1725s now running with external clock.
Modified frontend to readout 4 modules and 16 channels per module.
Still need to modify the analyzer to show data for all 4 modules. |
55
|
01 Nov 2019 06:50 |
Alex Kish | Configuration | Hardware | Turn off the fields |
Ramp down the fields, in 200V steps.
Nominal values:
1st ring: 4180 V
wire gate: 3780 V
cathode: 6180 V |
58
|
01 Nov 2019 09:49 |
Alex Kish | Configuration | Hardware | Turn off the fields |
Ramp UP the fields, in 100V steps.
Nominal values:
1st ring: 4180 V
wire gate: 3780 V
cathode: 6180 V |
9
|
31 Jan 2019 15:18 |
Pierre | Configuration | Trigger | Trigger rate |
Somehow the trigger rate was not matching the trigger source.
Find out that Link 3 was not collecting and possibly holding the fragment assembly in the main thread.
Swap Link3 <-> Link0 on the V1725, restarted.
Needs further investigation!
Date rate is fine now! CPU load is balanced on all 4 threads (~25%)
- irqbalance disabled
- change affinity for A3818 to cpu9: /etc/rc.local add: echo 0200 > /proc/irq/136/smp_affinity
Check : watch -n 0.1 'cat /proc/interrupts'
Maximum Trigger rate (HW buffer not rising) 1950 Evt/s => 200MB/s
for event size of 100KB composed of 4 banks with 32us per channel. |
23
|
27 Mar 2019 14:04 |
Pierre | Configuration | Trigger | Time stamp sync |
The ChronoBox latest FW is loaded. Let tme know if this is what the chronobox should look like in term of registers.
Are we monitoring the PLL Lock Loss (odb: /DEAP Alarm ?)
Here is the dump of the 5 first sync triggers without any physics trigger behind.
1 0x830b577 0x17d7855 0x6b33d22 0x6b33d22 8.992791
2 0x830b577 0x17d7855 0x6b33d22 0x6b33d22 8.992791
3 0x830b577 0x17d7855 0x6b33d22 0x6b33d22 8.992791
4 0x830b577 0x17d7855 0x6b33d22 0x6b33d22 8.992791
1 0x830b581 0x2faf097 0x535c4ea 0x535c4ea 6.992792
2 0x830b581 0x2faf097 0x535c4ea 0x535c4ea 6.992792
3 0x830b581 0x2faf095 0x535c4ec 0x535c4ec 6.992792
4 0x830b581 0x2faf095 0x535c4ec 0x535c4ec 6.992792
1 0x830b587 0x47868d7 0x3b84cb0 0x3b84cb0 4.992792
2 0x830b587 0x47868d7 0x3b84cb0 0x3b84cb0 4.992792
3 0x830b587 0x47868d7 0x3b84cb0 0x3b84cb0 4.992792
4 0x830b587 0x47868d7 0x3b84cb0 0x3b84cb0 4.992792
1 0x830b5a1 0x5f5e119 0x23ad488 0x23ad488 2.992794
2 0x830b5a1 0x5f5e119 0x23ad488 0x23ad488 2.992794
3 0x830b5a1 0x5f5e117 0x23ad48a 0x23ad48a 2.992794
4 0x830b5a1 0x5f5e117 0x23ad48a 0x23ad48a 2.992794
1 0x830b5ab 0x7735959 0xbd5c52 0xbd5c52 0.992795
2 0x830b5ab 0x7735959 0xbd5c52 0xbd5c52 0.992795
3 0x830b5ab 0x7735959 0xbd5c52 0xbd5c52 0.992795
4 0x830b5ab 0x7735959 0xbd5c52 0xbd5c52 0.992795
With the physics triggers:
1 0x830b5c1 0x1834497f 0xeffc6c42 0x100393be 21.493591
2 0x830b5c1 0x1834497f 0xeffc6c42 0x100393be 21.493591
3 0x830b5c1 0x1834497f 0xeffc6c42 0x100393be 21.493591
4 0x830b5c1 0x1834497f 0xeffc6c42 0x100393be 21.493591
1 0x830b5d3 0x1834abb5 0xeffc0a1e 0x1003f5e2 21.495601
2 0x830b5d3 0x1834abb5 0xeffc0a1e 0x1003f5e2 21.495601
3 0x830b5d3 0x1834abb5 0xeffc0a1e 0x1003f5e2 21.495601
4 0x830b5d3 0x1834abb5 0xeffc0a1e 0x1003f5e2 21.495601
1 0x830b5dd 0x18350d7f 0xeffba85e 0x100457a2 21.497603
2 0x830b5dd 0x18350d7f 0xeffba85e 0x100457a2 21.497603
3 0x830b5dd 0x18350d7f 0xeffba85e 0x100457a2 21.497603
4 0x830b5dd 0x18350d7f 0xeffba85e 0x100457a2 21.497603
1 0x830b5e3 0x183585e7 0xeffb2ffc 0x1004d004 21.500068
2 0x830b5e3 0x183585e7 0xeffb2ffc 0x1004d004 21.500068
3 0x830b5e3 0x183585e7 0xeffb2ffc 0x1004d004 21.500068
4 0x830b5e3 0x183585e7 0xeffb2ffc 0x1004d004 21.500068
1 0x830b5ed 0x1a10bb9b 0xee1ffa52 0x11e005ae 23.991535
2 0x830b5ed 0x1a10bb9b 0xee1ffa52 0x11e005ae 23.991535
3 0x830b5ed 0x1a10bb9b 0xee1ffa52 0x11e005ae 23.991535
4 0x830b5ed 0x1a10bb9b 0xee1ffa52 0x11e005ae 23.991535
1 0x830b5fb 0x1a111f65 0xee1f9696 0x11e0696a 23.993578
2 0x830b5fb 0x1a111f65 0xee1f9696 0x11e0696a 23.993578
3 0x830b5fb 0x1a111f65 0xee1f9696 0x11e0696a 23.993578
4 0x830b5fb 0x1a111f65 0xee1f9696 0x11e0696a 23.993578
1 0x830b607 0x1a118115 0xee1f34f2 0x11e0cb0e 23.995577
2 0x830b607 0x1a118115 0xee1f34f2 0x11e0cb0e 23.995577
3 0x830b607 0x1a118115 0xee1f34f2 0x11e0cb0e 23.995577
4 0x830b607 0x1a118115 0xee1f34f2 0x11e0cb0e 23.995577
1 0x830b611 0x1a11e2c7 0xee1ed34a 0x11e12cb6 23.997577
2 0x830b611 0x1a11e2c7 0xee1ed34a 0x11e12cb6 23.997577
3 0x830b611 0x1a11e2c7 0xee1ed34a 0x11e12cb6 23.997577
4 0x830b611 0x1a11e2c7 0xee1ed34a 0x11e12cb6 23.997577
The ZMQ0 banks:
#banks:5 Bank list:-ZMQ0W200W201W202W203-
Bank:ZMQ0 Length: 40(I*1)/10(I*4)/10(Type) Type:Unsigned Integer*4
1-> 0x000a5f1c 0x000000c4 0x00000001 0x0ebd5273 0x00000001 0x00010001 0xffffffff 0x00000000
9-> 0xffff0000 0x00000000
------------------------ Event# 10 ------------------------
#banks:5 Bank list:-ZMQ0W200W201W202W203-
Bank:ZMQ0 Length: 40(I*1)/10(I*4)/10(Type) Type:Unsigned Integer*4
1-> 0x000a5f1d 0x000000c5 0x00000001 0x0ebd5279 0x00000001 0x00010001 0xffffffff 0x00000000
9-> 0xffff0000 0x00000000
[dsproto@ds-proto-daq dsproto_daq]$ |
7
|
21 Jan 2019 13:05 |
Thomas, Pierre | Routine | Digitizer | Tests of V1725 baseline and triggering |
A little progress on a couple fronts:
1) We got the baseline DAC setting working correctly from both the CAEN command line tool and from the MIDAS
frontend. Needed to add some extra sleep before the DAC settings were modified.
2) We figured out how to set the threshold for self-triggering on each channel. It is actually register 0x1n60
for this firmware. The threshold is defined relative to the online calculated baseline. The threshold is
settable from the ODB. However, the polarity of the triggering is currently hard-coded to be negative (bit 6 of
register 0x1n64).
3) We could confirm that the LVDS outputs from the V1725 appeared and disappeared as expected when the
self-trigger threshold was changed.
4) We added some basic documentation in Markdown here:
https://bitbucket.org/ttriumfdaq/dsproto_daq/src/master/ |
11
|
07 Feb 2019 17:30 |
Thomas | Routine | Software | Testing the maximum data throughput |
First check the maximum trigger rate and maximum data rate for different sample lengths (for each channels):
sample length Maximum rate MB/s CPU % (per thread)
16us 0.44kHz 231 20
6.4us 1.04kHz 214 20
3.2us 1.95kHz 198 22
1.6us 3.12kHz 160 26
0.8us 4.88kHz 127 30 (what are these threads doing?)
Look at the code more. See that there is a maximum size for the block transfer of 10kB. Increase this to 130kB
(which is the maximum amount that this board can make per event). Now find
sample length Maximum rate MB/s CPU % (per thread)
16us 0.68kHz 346 7
6.4us 1.46kHz 300 10
1.6us 3.6kHz 190 25
Good. So for long samples we are actually slightly above the maximum transfer rate of 85MB/s*4 = 340MB/s
Tried writing out the data to disk at the maximum 345MB/s rate; the DAQ can't keep up. Maximum rate was more
like 270MB/s.
I think the mlogger was actually fine. But I think the write-to-disk speed of the harddrive could not keep up.
So I think we are limited
by hardware in that case. We would need a large raid array to be able to write faster. |
3
|
13 Dec 2018 11:02 |
Thomas | Routine | Hardware | Testing V1725 digitizers |
Couple weeks of work documented in one elog...
V1725 serial numbers: 455, 392, 460, 462, 474
firmware: DPP-ZLE+
The 3818 kernel module not getting loaded on start-up... it is in /etc/rc.local, but not getting called
[root@ds-proto-daq ~]# grep 3818 /etc/rc.local
# Load A3818 driver...
/sbin/insmod /home/dsproto/packages/A3818Drv-1.6.0/src/a3818.ko
Called manually for now...
Reworked and cleaned up DEAP version of V1725 code
- Updated register map
- Removed smartQT code
Quick test: the V1725 seems to be getting busy at a maximum rate of 10kHz (with no samples being saved though).
Got preliminary documentation from CAEN for ZLE-plus firmware... posted here:
/home/dsproto/packages/CAEN_ZLE_Info
In particular, manual shows how the data structure is different for ZLE-plus data banks (as compared to V1720 ZLE data banks).
Fixed the /etc/rc.local setup so that the A3818 driver is loaded and mhttpd/mlogger is started on reboot.
Looking at V1725-ZLE register list. I don't entirely understand how we are going to do the trigger outputs and the busy. The manual makes it clear that the triggers from each pair of channels are combined together and send to the trigger logic. So there should be 8 trigger primitives from the board. The LVDS IO connector allows to configure groups of 4 outputs as being for either the trigger outputs or the busy/veto outputs. So I guess I will configure the first two groups to output the trigger primitives and the third group to output the BUSY information.
Added code to do the ADC calibration; added extra equipment for reading out ADC temperatures periodically.
Renewed the lets-encrypt SSL certificate... but haven't set up automatic renewal yet...
[root@ds-proto-daq ~]# certbot renew --apache
[root@ds-proto-daq ~]# systemctl restart httpd
Analyzer program basically working. Pushed to bitbucket:
https://bitbucket.org/ttriumfdaq/dsproto_analyzer/src |
46
|
26 Oct 2019 07:33 |
Sam Hill | Problem | Software | Test of IV Script |
People: Simone, Sam, Tom, Edgar
Tested IV curve python script that runs using MIDAS. Measured resistance consistant with resistor specification. elog:46/1
The resistance is attached to ch11, and we called the script (channels go from 0 to 24):
chnum=11 ; python3 iv_curve.py --no_steering --caen_chan $chnum --stop_v 3 --step_v 0.001 --filename ivcurve_`date +%s`_$chnum.txt
Issues:
No readout of trip condiotion therefore python script overides power supply trip and attemps to bring back voltage to next value. Potentially dangerous. Script only terminates with the final voltage value. See attached plot elog:46/1
Script terminated with error message:
Traceback (most recent call last):
File "iv_curve.py", line 287, in <module>
iv.run()
File "iv_curve.py", line 269, in run
self.set_caen_and_wait_for_readback(voltage)
File "iv_curve.py", line 223, in set_caen_and_wait_for_readback
raise RuntimeError("CAEN HV didn't respond to request to set voltage to %s; latest readback voltage is %s" % (voltage, rdb))
RuntimeError: CAEN HV didn't respond to request to set voltage to 2.976; latest readback voltage is 0.052000001072883606
|
Attachment 1: IV_curve_29K.png
|
|
24
|
28 Mar 2019 02:18 |
Pierre | Configuration | Trigger | Test |
|
15
|
05 Mar 2019 10:36 |
Thomas | Routine | Digitizer | Switched to standard V1725 firmware |
It turns out that the ZLE V1725 firmware we are using only supports reading out up to 4000 samples per channel.
We need 80000 samples to readout 200us, which is requirement.
So we switch the V1725s to use the backup firmware on the board, which is the standard waveform firmware.
Firmware version is 17200410.
Expected data size for event with 200us of data: 200000ns * 1/4 ns/sample * 16 ch * 4 boards * 2 bytes/sample =
6.4MB per event
Measured max event rate of 60Hz with 385MB/s with 200us readout.
Needed to increase max event size, set buffer organization to 6 and set almost full to 32 in order to
accommodate the larger event size.
Changed some registers for different firmware:
- V1725_SELFTRIGGER_LOGIC
More tests needed |
18
|
06 Mar 2019 15:10 |
Thomas, Pierre | Routine | Trigger | Setup of chronobox |
Summary of setup of chronobox on network (mostly done by Pierre):
1) Hook up USB connection from chronobox to ds-proto-daq. Start serial-USB connection by doing
/home/dsproto/online/dsproto_daq/serialusb
can login through serial link. Added the ssh key for dsproto@ds-proto-daq to the authorized_keys file on
chronobox linux.
ctrl-a, ctrl-x to stop picocom
2) On ds-proto-daq, setup dhcpd server. Configuration in this file
/etc/dhcp/dhcpd.conf
dhpcd is bond to the second NIC only. Configure DHCP to give IP 192.168.1.3 to chronobox. In /etc/hosts set
192.168.1.3 to have hostname chronobox
Power cycle chronobox; it successfully gets IP:
[dsproto@ds-proto-daq dsproto_daq]$ ping chronobox
PING chronobox (192.168.1.3) 56(84) bytes of data.
64 bytes from chronobox (192.168.1.3): icmp_seq=1 ttl=64 time=0.180 ms
3) Can see the chronobox webpage locally as
http://chronobox:8080
4) Some esper tool to access data: did following to setup esper
734 yum install python2-pip
735 pip install esper-tool
736 yum install ncurses
738 yum install ncurses-devel
739 pip install esper-tool
Can then connect to the chronobox by doing
esper-tool interactive http://chronobox:8080
This is as much as I understand at this point... more exploring now...
5) Pierre unplugged the SD card to take it back to Bryerton's room. But I guess this was bad.
lots of errors on serialUSB link now and the webpage doesn't work anymore:
[ 1246.665269] blk_partition_remap: fail for partition 2
Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.904770] EXT4-fs error: 339 callbacks suppressed
[ 1246.679162] blk_partition_remap: fail for partition 2
Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.904780] EXT4-fs error (device mmcblk0p2):
ext4_find_entry:1437: inode #2: com[ 1246.692884] blk_partition_remap: fail for partition 2
m syslogd: reading directory lblock 0
[ 1246.709020] blk_partition_remap: fail for partition 2
Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.929199] blk_partition_remap: fail for partition 2
[ 1246.717394] blk_partition_remap: fail for partition 2
Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.942971] EXT4-fs error (device mmcblk0p2):
ext4_find_entry:1437: inode #2: com[ 1246.731255] blk_partition_remap: fail for partition 2
m syslogd: reading directory lblock 0
Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.953760] blk_partition_remap: fail for [ 1246.747337]
blk_partition_remap: fail for partition 2
partition 2
Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.967532] EXT4-fs error (device mmcblk0p2):
ext4_find_entry:1437: [ 1246.763481] blk_partition_remap: fail for partition 2
inode #2: comm syslogd: reading directory lblock 0
Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.978320] blk_partition_rem[ 1246.779511] blk_partition_remap:
fail for partition 2
ap: fail for partition 2
Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.992091] EXT4-fs error (device mmcblk0p2): ext4_find[
1246.795586] blk_partition_remap: fail for partition 2
_entry:1437: inode #2: comm syslogd: reading directory lblock 0
Jan 1 00:20:46 buildroot user.warn kernel: [ 1243.002885] blk_[ 1246.811671] blk_partition_remap: fail for
partition 2
partition_remap: fail for partition 2
Jan 1 00:20:46 buildroot user.crit kernel: [ 1243.016656] EXT4-fs error (device mmcblk0p[ 1246.827750]
blk_partition_remap: fail for partition 2 |
19
|
06 Mar 2019 18:19 |
Bryerton Shaw | Routine | Trigger | Setup of chronobox |
The SDcard is currently required for operation of the device, the ext3/4 filesystem will immediately fail upon removal.
> Summary of setup of chronobox on network (mostly done by Pierre):
>
> 1) Hook up USB connection from chronobox to ds-proto-daq. Start serial-USB connection by doing
>
> /home/dsproto/online/dsproto_daq/serialusb
>
> can login through serial link. Added the ssh key for dsproto@ds-proto-daq to the authorized_keys file on
> chronobox linux.
>
> ctrl-a, ctrl-x to stop picocom
>
> 2) On ds-proto-daq, setup dhcpd server. Configuration in this file
>
> /etc/dhcp/dhcpd.conf
>
> dhpcd is bond to the second NIC only. Configure DHCP to give IP 192.168.1.3 to chronobox. In /etc/hosts set
> 192.168.1.3 to have hostname chronobox
>
> Power cycle chronobox; it successfully gets IP:
>
> [dsproto@ds-proto-daq dsproto_daq]$ ping chronobox
> PING chronobox (192.168.1.3) 56(84) bytes of data.
> 64 bytes from chronobox (192.168.1.3): icmp_seq=1 ttl=64 time=0.180 ms
>
> 3) Can see the chronobox webpage locally as
>
> http://chronobox:8080
>
> 4) Some esper tool to access data: did following to setup esper
>
> 734 yum install python2-pip
> 735 pip install esper-tool
> 736 yum install ncurses
> 738 yum install ncurses-devel
> 739 pip install esper-tool
>
> Can then connect to the chronobox by doing
>
> esper-tool interactive http://chronobox:8080
>
> This is as much as I understand at this point... more exploring now...
>
> 5) Pierre unplugged the SD card to take it back to Bryerton's room. But I guess this was bad.
>
> lots of errors on serialUSB link now and the webpage doesn't work anymore:
>
> [ 1246.665269] blk_partition_remap: fail for partition 2
> Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.904770] EXT4-fs error: 339 callbacks suppressed
> [ 1246.679162] blk_partition_remap: fail for partition 2
> Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.904780] EXT4-fs error (device mmcblk0p2):
> ext4_find_entry:1437: inode #2: com[ 1246.692884] blk_partition_remap: fail for partition 2
> m syslogd: reading directory lblock 0
> [ 1246.709020] blk_partition_remap: fail for partition 2
> Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.929199] blk_partition_remap: fail for partition 2
> [ 1246.717394] blk_partition_remap: fail for partition 2
> Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.942971] EXT4-fs error (device mmcblk0p2):
> ext4_find_entry:1437: inode #2: com[ 1246.731255] blk_partition_remap: fail for partition 2
> m syslogd: reading directory lblock 0
> Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.953760] blk_partition_remap: fail for [ 1246.747337]
> blk_partition_remap: fail for partition 2
> partition 2
> Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.967532] EXT4-fs error (device mmcblk0p2):
> ext4_find_entry:1437: [ 1246.763481] blk_partition_remap: fail for partition 2
> inode #2: comm syslogd: reading directory lblock 0
> Jan 1 00:20:46 buildroot user.warn kernel: [ 1242.978320] blk_partition_rem[ 1246.779511] blk_partition_remap:
> fail for partition 2
> ap: fail for partition 2
> Jan 1 00:20:46 buildroot user.crit kernel: [ 1242.992091] EXT4-fs error (device mmcblk0p2): ext4_find[
> 1246.795586] blk_partition_remap: fail for partition 2
> _entry:1437: inode #2: comm syslogd: reading directory lblock 0
> Jan 1 00:20:46 buildroot user.warn kernel: [ 1243.002885] blk_[ 1246.811671] blk_partition_remap: fail for
> partition 2
> partition_remap: fail for partition 2
> Jan 1 00:20:46 buildroot user.crit kernel: [ 1243.016656] EXT4-fs error (device mmcblk0p[ 1246.827750]
> blk_partition_remap: fail for partition 2 |
1
|
11 Dec 2018 15:17 |
Thomas | Configuration | Software | Setup elog for ds-proto-daq |
1) Install and tweak elog:
[root@ds-proto-daq ~]# cat /etc/elogd.cfg
[global]
port = 8084
MTP host = trmail.triumf.ca
Use Email Subject = {$logbook} $Subject
Remove on reply = Author
Quote on reply = 1
URL = https://ds-proto-daq/elog/
[DS Prototype]
Theme = default
Comment = ELOG for DS Prototype MIDAS DAQ
Attributes = Author, Type, Category, Subject
Options Type = Routine, Problem, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Digitizer, Trigger, MIDAS, Software, Other
Extendable Options = Category, Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Email all = lindner@triumf.ca
[root@ds-proto-daq ~]# systemctl start elogd.service
[root@ds-proto-daq ~]# systemctl is-active elogd.service
active
[root@ds-proto-daq ~]# systemctl enable elogd.service
2) Tweak apache and restart
[root@ds-proto-daq ~]# grep elog /etc/httpd/conf.d/ssl-ds-proto-daq.conf
ProxyPass /elog/ http://localhost:8084/ retry=1
[root@ds-proto-daq ~]# systemctl restart httpd
3) change MIDAS to use elog
[dsproto@ds-proto-daq bin]$ odbedit
[local:dsproto:R]/>cd Elog/
[local:dsproto:R]/Elog>create STRING URL
String length [32]: 256
[local:dsproto:R]/Elog>set URL https://ds-proto-daq.triumf.ca/elog/DS+Prototype/ |
2
|
11 Dec 2018 15:20 |
Thomas | Configuration | Software | Setup elog for ds-proto-daq |
1) Install and tweak elog:
[root@ds-proto-daq ~]# cat /etc/elogd.cfg
[global]
port = 8084
MTP host = trmail.triumf.ca
Use Email Subject = {$logbook} $Subject
Remove on reply = Author
Quote on reply = 1
URL = https://ds-proto-daq/elog/
[DS Prototype]
Theme = default
Comment = ELOG for DS Prototype MIDAS DAQ
Attributes = Author, Type, Category, Subject
Options Type = Routine, Problem, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Digitizer, Trigger, MIDAS, Software, Other
Extendable Options = Category, Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Email all = lindner@triumf.ca
[root@ds-proto-daq ~]# systemctl start elogd.service
[root@ds-proto-daq ~]# systemctl is-active elogd.service
active
[root@ds-proto-daq ~]# systemctl enable elogd.service
2) Tweak apache and restart
[root@ds-proto-daq ~]# grep elog /etc/httpd/conf.d/ssl-ds-proto-daq.conf
ProxyPass /elog/ http://localhost:8084/ retry=1
[root@ds-proto-daq ~]# systemctl restart httpd
3) change MIDAS to use elog
[dsproto@ds-proto-daq bin]$ odbedit
[local:dsproto:R]/>cd Elog/
[local:dsproto:R]/Elog>create STRING URL
String length [32]: 256
[local:dsproto:R]/Elog>set URL https://ds-proto-daq.triumf.ca/elog/DS+Prototype/ |
109
|
10 Nov 2019 08:40 |
Edgar Sanchez | Routine | General | S1 data taking without field |
Run 1041
Gas pocket: OFF
Fields: OFF
Threshold: 100 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 360 Hz
Run 1042
Gas pocket: OFF
Fields: OFF
Threshold: 200 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 340 Hz
Run 1043
Gas pocket: OFF
Fields: OFF
Threshold: 250 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 290 Hz
Run 1044
Gas pocket: OFF
Fields: OFF
Threshold: 400 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 240 Hz
Run 1045
Gas pocket: OFF
Fields: OFF
Threshold: 600 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 170 Hz
Run 1046
Gas pocket: OFF
Fields: OFF
Threshold: 800 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 140 Hz
Run 1047
Gas pocket: OFF
Fields: OFF
Threshold: 1000 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 110 Hz
Run 1048
Gas pocket: OFF
Fields: OFF
Threshold: 150 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 400 Hz
Run 1049
Gas pocket: OFF
Fields: OFF
Threshold: 100 ADCc below baseline
Trace length: 30us total, 5 us pre-trigger
Threshold extend: 5x16 = 80ns
TPC Pressure: 340 mbarg
SiPM HV: 65 V
Number of events: 50k
Rate: 400 Hz |