Online uncaging analysis does not work

Bug #623009 reported by meganbkratz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
acq4
Fix Released
Undecided
Unassigned

Bug Description

The following error occurs when online uncaging analysis is enabled. (The NIDAQ Warning occurs whether or not the uncaging analysis is enabled, so may or may not be related.

NIDAQ Warning:
('Clock rate specified is so high that it violates the settling time requirements for the acquisition.\n\nReduce the clock rate, or the accuracy of the measurement might be compromised.', '')
Traceback (most recent call last):
  File "C:\Documents and Settings\Experimenters\luke\acq4\lib\modules\ProtocolRunner\analysisModules\Uncaging\interface.py", line 61, in newFrame
    self.currentProt.addFrame(frame)
  File "C:\Documents and Settings\Experimenters\luke\acq4\lib\modules\ProtocolRunner\analysisModules\Uncaging\interface.py", line 180, in addFrame
    camInfo = frame['result'][camDev]['frames'][self.state['frame1Spin']].infoCopy()
KeyError: None

Earlier in this function is the line:

camDev = self.ui().cameraDevice()

This is setting camDev to None (which creates the KeyError). This is happening in an if/else block at line 136 in the same file.

Revision history for this message
lcampagn (luke-campagnola) wrote : Re: [Bug 623009] [NEW] Online uncaging analysis does not work

Probably just caused by not telling the uncaging analysis module what camera
device to use (?) It would be nice if this printed a useful error message
and handled the exception gracefully.

On Mon, Aug 23, 2010 at 17:00, meganbkratz <email address hidden> wrote:

> Public bug reported:
>
> The following error occurs when online uncaging analysis is enabled.
> (The NIDAQ Warning occurs whether or not the uncaging analysis is
> enabled, so may or may not be related.
>
> NIDAQ Warning:
> ('Clock rate specified is so high that it violates the settling time
> requirements for the acquisition.\n\nReduce the clock rate, or the accuracy
> of the measurement might be compromised.', '')
> Traceback (most recent call last):
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\modules\ProtocolRunner\analysisModules\Uncaging\interface.py",
> line 61, in newFrame
> self.currentProt.addFrame(frame)
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\modules\ProtocolRunner\analysisModules\Uncaging\interface.py",
> line 180, in addFrame
> camInfo =
> frame['result'][camDev]['frames'][self.state['frame1Spin']].infoCopy()
> KeyError: None
>
>
> Earlier in this function is the line:
>
> camDev = self.ui().cameraDevice()
>
> This is setting camDev to None (which creates the KeyError). This is
> happening in an if/else block at line 136 in the same file.
>
> ** Affects: acq4
> Importance: Undecided
> Status: New
>
> --
> Online uncaging analysis does not work
> https://bugs.launchpad.net/bugs/623009
> You received this bug notification because you are the registrant for
> acq4.
>

Changed in acq4:
status: New → Invalid
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.