dreyling

Results 9 issues of dreyling

If the the HOSTNAME variable is not set as the (local) IP, then the RunControl can send something to the connected components, but the communication back is not working. This...

bug
enhancement
1.X

It happened that the trigger ID was not completely read out by the MimosaDAQ (due to a short cable probably the last bit is missing), therefore the TLU Data and...

enhancement
2.X

It happened that in the conf-file the connection parameter to the DataCollector was missing. If there is no online monitoring/feedback as for the TLU Producer, then the user is not...

enhancement
Main Library
2.X

We had this in EUDAQ1 using ctests, see Manual. Would be nice to reactivate that.

enhancement
2.X

After pressing (stop, reset) terminate, the application - probably euRun - "stopped unexpectedly", see screenshot: ![screenshot from 2018-05-11 15-36-56](https://user-images.githubusercontent.com/10775275/39927092-7ecdab9c-5531-11e8-80e0-c3879b238b32.png)

bug
GUI
2.X

Advantages could be: - maintained communication - defined interface for other languages http://zeromq.org/ is a canditate

enhancement
2.X

Users have observed and logged 3 (in DESY TB21, Datura) and 6 (in DESY TB22, Duranta) EUDAQ crashs (= EUDAQ run control quits, but DataCollector and DataTaking resumed). EUDAQ and...

OnlineMonitor was successfully started on Ubuntu 14 machine of DESY TB21 DATURA. When RunControl and DataCollector receives data (TLU and Mimosas), OnlineMonitor crashed. > Initialized geometry: 6 planes. *** buffer...

I experienced a segmentation violation after terminating the RunControl, if a Producer (ExampleProducer, NIProducer, TLUProducer, ..) is connected. In a minimal setup (DataCollector and LogCollector), it terminates properly. Maybe with...

bug
enhancement
Main Library