|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
10 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
10 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
11 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
11 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
16 Jul 2019, Konstantin Olchanski, Bug Report, a3818 and signals, Frontend killed at stop of run
|
16 Jul 2019, Konstantin Olchanski, Bug Report, a3818 and signals, Frontend killed at stop of run
|
|
Message ID: 1597
Entry time: 08 Jul 2019
Reply to this: 1598
|
Author: |
Vinzenz Bildstein |
Topic: |
Bug Report |
Subject: |
Frontend killed at stop of run |
|
|
I wrote a c++ frontend to read data from CAEN VX1730 digitizers which is used in
parallel with the GRIFFIN frontend to read out DESCANT.
After a long overnight run to check that the frontend runs smoothly for a longer
time, I stopped the run and the frontend was killed by midas. I am not sure why
this happened, as the end_of_run function returned successfully (at least the
print statement right before "return SUCCESS;" appeared right away). So
something else must have timed-out and caused it to be killed, I guess?
Any suggestions on where to look to find out what causes this?
Thanks in advance for your help! |