Open jvavrek opened 8 years ago
Jayson,
Can you post the versions of ADAQ libraries and ADAQAcquisition that you are using as well as OS, compiler, CAEN hardware, etc? Is there a specific "trigger action" that causes this error? I've seen this a few times in different places but thought we had resolved it.
Right off the bat I'll recommend making sure that you have the most up-to-date ADAQ (v1.8.1) and ADAQAcquisition (1.6.10).
We're running ADAQAcquisition v1.6.10 with ADAQ v1.8.1 on Ubuntu 14.04. We compiled using g++ (gcc version 4.8.4). The CAEN hardware is a DT5790M desktop digitizer/power supply. I don't recall any specific trigger action.
Everything seems in order in terms of the setup. Can you attempt to replicate this behavior and be careful to note when and what causes it? I suspect that it may have something to do either with the "settings" feature (save/load widget settings) or with the persistent storage of data feature. I can't really do anything without a more definitive indication of what's wrong.
Sure, no problem. I’ll look into it on Monday/Tuesday when we have access to the digitizer again.
On Jul 27, 2016, at 1:28 PM, Zach Hartwig notifications@github.com wrote:
Everything seems in order in terms of the setup. Can you attempt to replicate this behavior and be careful to note when and what causes it? I suspect that it may have something to do either with the "settings" feature (save/load widget settings) or with the persistent storage of data feature. I can't really do anything without a more definitive indication of what's wrong.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zach-hartwig/ADAQAcquisition/issues/29#issuecomment-235658890, or mute the thread https://github.com/notifications/unsubscribe-auth/AHU-5v3MZhS1nst60jqIuiOWaTCVA3sCks5qZ5VOgaJpZM4JVfYR .
Encountered this issue today, just wanted to add a couple of details since I found a way to produce this error consistently. We were running the current "master" of both ADAQ and ADAQAcquisition, with the CAEN DT5790M, and the issue of all radio buttons and check boxes clearing could be very consistently caused by aborting a timed run. Just wanted to quickly write this down here while I'm thinking about it; I will also dig into the code a bit to see if I can figure this out.
Occasionally while using the interface, all radio buttons will have their values reset (not to defaults, but completely cleared). This prevents acquisition until the user manually tracks down all radio buttons across the five settings tabs and resets them.