Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dimax number of recorded frames is dropping #4

Closed
tfarago opened this issue Aug 12, 2014 · 7 comments
Closed

Dimax number of recorded frames is dropping #4

tfarago opened this issue Aug 12, 2014 · 7 comments
Labels

Comments

@tfarago
Copy link

tfarago commented Aug 12, 2014

When auto trigger mode and external acquire mode the camera can be allowed or disallowed from recording frames by low-level TTL signal on acq. enable input. When I try to use it the number of recorded frames is dropping (see the Concert screenshot):

dimax > camera.start_recording()

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > trigger.on()

dimax > trigger.off()

dimax > camera.recorded_frames
<Quantity(2700, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(2685, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(2669, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(2649, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(2596, 'dimensionless')>
@tfarago tfarago added the bug label Aug 12, 2014
@matze
Copy link
Contributor

matze commented Aug 12, 2014

Is it consistent if you stop recording? I could imagine, that the reported number is anything but a good indicator for the currently number of recorded frames. In any case, there isn't much magic going on, when reading that number.

@tfarago
Copy link
Author

tfarago commented Aug 12, 2014

Then it is consistent, you are right. However, the value which you get after you stop recording is still less then what was really recorded. For example I acquired in sequence record mode and waited until the camera buffer was filled. Then it stopped recording itself, but gave 0 recorded frames. to illustrate this in a simpler manner when I stop the camera:

dimax > camera.start_recording()

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > trigger.on()

dimax > trigger.off()

dimax > camera.recorded_frames
<Quantity(193, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(126, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > camera.stop_recording()

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

So now I neither know how many frames I recorded neither can I read out the full buffer with Concert if num_frames is None, i.e. I want to read out everything.

@tfarago
Copy link
Author

tfarago commented Aug 12, 2014

OK I could just read out until I get an exception from camera, but that's a dirty workaround.

@tfarago
Copy link
Author

tfarago commented Aug 12, 2014

I also noticed the value in recorded frames is one too many. E.g. if the camera tells you n you can actually read n - 1 images. Is that normal behavior for PCO?

@matze
Copy link
Contributor

matze commented Aug 12, 2014

FYI: to stop dropping frames, camera.storage_mode must be set to RECORDER and not FIFO_BUFFER.

@tfarago
Copy link
Author

tfarago commented Aug 12, 2014

Thanks, I will try.

@tfarago
Copy link
Author

tfarago commented Aug 13, 2014

Yeah it works.

@tfarago tfarago closed this as completed Aug 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants