You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a PyPlotImageViewer is attached to an experiment the frame-rate drops. As far as I understood, the PyplotImageViewer should drop frames when the drawing of an old frame is not yet finished.
Running exp.run() like this gives me 1.24s. If I detatch the live_view I get 0.0125s.
I tested it on my local machine (no ssh x-forwarding).
Can I somehow make the PyplotImageViewer less blocking? Also the asyncronous ImageWriter delays the acquisition (until now usually less than a frame with 15fps and 2k x 2k pixels). Is it possible to speed up the whole addon-consumer-pipeline?
@tfarago I thinkt this is also related to the delay that we had (have) with the pco.4000
The text was updated successfully, but these errors were encountered:
I have very inconsistent results with np.zeros. To me it seems that sometimes python optimizes that just for array reservation and sometimes it really allocates zeros. Try the following:
When a PyPlotImageViewer is attached to an experiment the frame-rate drops. As far as I understood, the PyplotImageViewer should drop frames when the drawing of an old frame is not yet finished.
Example:
Running
exp.run()
like this gives me 1.24s. If I detatch thelive_view
I get 0.0125s.I tested it on my local machine (no ssh x-forwarding).
Can I somehow make the PyplotImageViewer less blocking? Also the asyncronous ImageWriter delays the acquisition (until now usually less than a frame with 15fps and 2k x 2k pixels). Is it possible to speed up the whole addon-consumer-pipeline?
@tfarago I thinkt this is also related to the delay that we had (have) with the pco.4000
The text was updated successfully, but these errors were encountered: