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

Clean up how framerate is handled #18

Open
jmtayloruk opened this issue Aug 28, 2020 · 1 comment
Open

Clean up how framerate is handled #18

jmtayloruk opened this issue Aug 28, 2020 · 1 comment

Comments

@jmtayloruk
Copy link
Collaborator

Framerate is handled in several separate ways:
self.settings["brightfield_framerate"] (which is used in optical_gater_server etc, but does not set seem to be set in the .json file?)
self.settings["framerate"] (which is read in prospective_optical_gating.py, but not used elsewhere)
self.framerate (which seems to be redundant, though I'm not 100% sure it doesn't have some relevance to the Pi - though there is also camera.framerate on the Pi)

This should be consolidated - I think they are all referring to the same thing.

@ChasNelson1990
Copy link
Member

  • camera.framerate is needed for the pi
  • self.settings["brightfield_framerate"] does come from the settings json? It's definitely in the example json.
  • self.settings["framerate"] is, I think the old POG name for "brightfield_framerate" and so let's update this to be "brightfield_framerate"
  • self.framerate.... sounds like it was there when OpticalGater inherited from PiArray... so, yes, redundant now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants