search

beifen / neurorighter

Automatically exported from code.google.com/p/neurorighter
0 stars 0 forks source link

Open-loop stim running task error after previous error #78

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
On start of attempted open-loop stimulation we received an error (as seen 
https://groups.google.com/forum/?fromgroups=#!topic/neurorighter-users/yZpinA_9v
ic )

On subsequent attempts to restart open-loop stim trials we received an error 
that was (in essence): "Cannot start task as there is a conflicting task 
already running."

The thought is that after initiating the open-loop protocol and its subordinate 
tasks, the NI-DAQ runs into an error where the RTSI cable is not configured. 
This causes it to throw an error that is caught and reported (as seen in the 
screenshot) but NeuroRighter does not *stop* the subordinate tasks. This causes 
subsequent attempts to run the open-loop trial to attempt to start a task that 
is already running.

Proposed solution: once the error is thrown, neurorighter should catch it and 
close the tasks that it began when the "start" button was pressed. This assures 
that on subsequent "starts" that there are no tasks already running.

What version of the product are you using? On what operating system?
v1.1.0.562

Please provide any additional information below.

Original issue reported on code.google.com by nlaxpat....@gmail.com on 1 May 2013 at 4:01

GoogleCodeExporter commented 9 years ago 
I'm closing this issue because it was due to the RTSI cable not being 
installed. 

The RTSI cable is required because the cards need to share clock signals. 
Otherwise slight differences in the frequency of the crystal oscillators on 
each card translate to samples being collected asynchronously.

Original comment by jonathan...@gmail.com on 1 May 2013 at 9:56

GoogleCodeExporter commented 9 years ago 
Actually, I don't think the RTSI cable caused it. The fact that it threw an 
error and then didn't close the task after the error is the problem. While the 
lack of an RTSI cable brought it out, other things could bring it out too. The 
suggestion of closing tasks after the error is thrown should prevent other 
issues from throwing this error.

Original comment by nlaxpat....@gmail.com on 1 May 2013 at 10:02