Hi Mark,
She’s currently in a testing/development stage where she (and I) are running the experiments on our laptops without a functional labjack.
Well, that explains it, but it would have been super helpful if someone had mentioned that at the beginning of this discussion.
If I understand all this correctly, sounds like the issue is that assert. Yes?
Correct.
Re: new code: we just made the first cut at these changes this last Fri and it hasn’t been tested with live Labjack hardware yet either.
OK. But obviously this wasn’t part of the problem, since there was no actual LabJack hardware involved.
Chris
Also, can I ask how that assertion has only just become an issue, since it’s been in the code for at least 13 years? Or have you been force-quitting MWServer during your testing stage all that time?
Hi Chris,
Sorry, I am realizing that I was unclear about our setup. The force-quitting is a recent issue in the lab, as we have moved to testing code on personal laptops. As a heads up, I am new to submitting bug reports and interacting with software at the development level, as I primarily have been working as an experimentalist. Let me know if you think there is a better way to communicate. I am happy to get on the phone and if anything I am asking is outside of the scope of your support just let me know.
Thanks for all the help thus far, we really appreciate it and I will try to be more thorough in my explanations of issues moving forward.
Nina
Hi Nina,
OK, no worries.
Also, regarding this:
Once, after the experiment had been running for maybe 20-30 minutes, I pressed the stop button, but the experiment wouldn’t stop. After a minute or so, I got a message from macOS saying my system was out of application memory, and I had to force quit MWServer.
This seems to be an issue with macOS 14.1. I’m currently trying to pin it down, but I’m certain it has nothing to do with your lab’s LabJack plugin.
Cheers,
Chris