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

Documentation missing on some autonight params #13

Open
martinbutt opened this issue Sep 22, 2022 · 4 comments
Open

Documentation missing on some autonight params #13

martinbutt opened this issue Sep 22, 2022 · 4 comments

Comments

@martinbutt
Copy link

The j, w, 1, 2, and 3 params for autonight.c aren't documented in the usage(). I would add them myself, but I can't work out from the code their exact meanings.

@martinbutt
Copy link
Author

I've taken a stab at them. Let me know if these look correct and I'll open a PR.

-1 <max_exposure> - The max_exposure required to turn night mode on
-2 <min_exposure>,<min_iridix>,<wait_seconds> - The min_exposure and min_iridix required to turn nightmode off. State must be maintained for wait_seconds to trigger.
-3 <min_white_balance>,<max_iridix>,<wait_seconds> - The min_white_balance and max_iridix required to switch nightmode off. State must be maintained for wait_seconds to trigger.
-j <jitter_percentage> - Percentage change in exposure to be considered too high for a gradual change in light to day/night, and therefore ignored.
-w <wait_seconds> - Number of seconds to wait after changing to/from nightmode before checking again.

@HaLo2FrEeEk
Copy link

Any ideas what "min_iridix" and "max_iridix" mean? Google is no help

@HaLo2FrEeEk
Copy link

Also it seems that the -w wait_seconds param is completely ignored, somehow. I've looked through the autonight.c code and it should respect it, but I've set mine to 15 and yet the moment that the exposure goes above the value in the -1 param, it switches.

@martinbutt
Copy link
Author

Any ideas what "min_iridix" and "max_iridix" mean? Google is no help

No idea, sorry. I just went with the variable name in the code.

I've looked through the autonight.c code and it should respect it

I'm not sure about this either. You can try running it with -v to see some output. You can also set up the Openmiko build container. Once you pull the submodules in you'll find a submodules/ingenic_videocap directory where you can add debug code to autonight.c. Follow the rest of the build instructions and it will generate you a new demo.bin that can be flashed to a camera for testing.

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