labthings / labthings/labthings-picamera2
Small changes in exposure time may get ignored
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
In response to #4, I've implemented a tolerance for exposure time: rather than reading, and re-applying, the exposure time every time we reconfigure the camera (e.g. when switching mode), the stored value is only updated if it differs significantly from the actual value. So, the gradual decrease we were seeing (20us each time it was reconfigured) gets ignored, and the value won't drift over time.
Obviously, if we are working with very short exposures, ignoring a change from 70ms to 50ms would be a problem. This issue is a reminder that we should consider a more elegant way of dealing with this - for example, explicitly updating the relevant item in persistent_controls when we update camera properties.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review issue #4 and the camera reconfiguration path described here, focusing on how camera properties and persistent_controls are updated. Done means gradual exposure drift is ignored without masking meaningful changes such as a change from 70ms to 50ms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100