Re: [micro-manager-general] Saving images at high speed

[Nico S. <nic...@uc...>]

Hi Pavak,

> This conversation led me to do a little bit of low stakes testing. 
> Turns out that by default, the JRE on my system selects the parallel 
> GC (it seems that this is an automated choice based on core counts and 
> OS). The parallel GC supposedly supports the maximum throughput in 
> memory turnover, but can cause long-ish stop-the-world pauses during 
> this. The "blips" I observed during high framerate acquisitions were 
> probably these events.

Great detective work!  I did not yet get to the GC chapter my book, but 
clearly experimenting is always the best approach, and please keep us 
updated with your findings.

The errors you see are likely related to timing issues between different 
threads.  One of the main reasons for me to switch to 2.0 was the 
display and horrible issues in the display code. Mark refactored thing 
very nicely and managed to isolate the ImageJ drawing code (interfacing 
with it well is difficult) very well. Those issues will persist in 1.4, 
but when you see them in 2.0, please let us know how to reproduce.

Also looks like you are testing with real hardware (rare for people to 
still have access!).  I am testing using the Democamera.  First 
configure the camera how you want it and snap an image.  Then set the 
"FastImage" property to 1.  The camera will now re-use the image it has 
in an internal buffer, hence no cpu cycles are spend generating the image.


Best,


Nico