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

Use more neutral term for captureMethod motionDetection #360

Closed
peterdesmet opened this issue Oct 27, 2023 · 2 comments · Fixed by #361
Closed

Use more neutral term for captureMethod motionDetection #360

peterdesmet opened this issue Oct 27, 2023 · 2 comments · Fixed by #361

Comments

@peterdesmet
Copy link
Member

We currently allow 2 values for captureMethod:

timelapse
motionDetection

@dhobern indicated that timelapse is pretty straightforward, but motionDetection might be a bit too narrow a term to express that the camera automatically detected something, resulting in a trigger that captured the media. PIR sensors use a combination of motion and heat to trigger the camera and if we want to eventually allow audio sensors, then it might just be sound (not motion) that is used to capture a media file.

We could rename to:

I prefer detection.

I would also rephrase cameraDelay:

Predefined duration after a trigger detection when activity detected by the camera is ignored. Expressed in seconds.

To remove the term trigger altogether

@ben-norton
Copy link
Member

It would be ideal to somehow use the infared heat detection aspect of the capture event. That is important in the broader community that animals like reptiles aren't readily detected using PIR sensors. If you went with detection then you lose that infared context. It becomes somewhat arbitrary how the animal was detected. A new technology/technique might make its way down the pipeline to camera traps that's distinctly different than infared. Maybe infaredDetection, thermalDetection?

@peterdesmet
Copy link
Member Author

peterdesmet commented Oct 31, 2023

Discussed with @kbubnicki. We want to keep the very broad categorization for this term. More specific (infrared, thermal, etc.) might be harder to provide by users and there is currently no use case for it. Suggested changes:

  • Rename value to activityDetection to express the broad concept of "sensor detected activity through undefined method". This would then also include the audio detection of a non-moving stridulating grasshopper, which is would be excluded by the current term motionDetection.
  • Remove "trigger" from cameraDelay and rephrase as:

    Predefined duration after detection when further activity is ignored. Expressed in seconds.

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

Successfully merging a pull request may close this issue.

2 participants