Re: [micro-manager-general] Live view freezing during MDA acquisition

[Seamus H. <sea...@ep...>]

Hi Nico,

Sorry for the slow reply! I've now managed to narrow it down a bit

>> I just updated to the latest nightly build (from an ~ 1 yr old version),  and I am noticing issues with live view.
>>
>> Live view seems to work fine before acquisition. When I run acquisition,  it runs fine, but live view freezes after a few frames. If I zoom in or  zoom out, live view starts working again for a few frames, then freezes  again. There doesnt seem to be that much in the logs, but I did notice  this error occuring quite frequently: 2014-03-19T14:21:16.000747 p:11472 t:11536 [dbg] >  (pop-tagged-image-timeout 20300.0 )
>>
>> Not that the data is saved fine, it's just the display.
> Image display has changed considerably in between those versions.  Our only chance of fixing this is by reproducing the problem.  So, we need to know as many details as possible:
> - What camera are you using (especially, pixel width and height, 8 or 16 bit or RGB)?
> - What were your acquisition settings?
> - Are you running live mode during acquisition or only after it ends?
>
> The time out is coming from the acquisition engine which asks the Core to "pop the next tagged image".  This suggests that your the camera is not sending an image during the period that  the Core will wait for an image.  Does this occur during an acquisition or during live mode?
>
>

So, to be clearer: live mode works fine, but during multidimensional 
acquisition the display window freezes after < 100 frames.
This occurs on the latest nightly build, for my Evolve 128 camera 
(128x128, 16bit) running at 30Hz.
MDA settings: 5000 frames, save to disk, image stack.

This also occurs with the MM demo config that ships with micromanager. 
However, very strangely, I only observe this bug if I set the demo 
camera size to 128x128. For 512x512 I do not see any error.
For the demo config, I get this in the core log for every frame:
2014-03-26T14:48:24.423422 p:611392 t:613796 [dbg] > 
(pop-tagged-image-timeout 20300.0 )
However, this is observed for both 128x128 and 512x512 (ie whether you 
get the bug or not) so I'm not sure whether it is relevant.

I have also now found a workaround: the bug only occurs when the "Slow 
Hist" option, if it is unchecked, freezing does not occur. Which is good 
enough for me - so if it's too puzzling, feel free to leave it!

Best wishes
Seamus