Dominik Dachs

I just want to confirm the need for the bounding box info in the observations.csv table. I guess the format is rather secondary, as long as it is defined, because...

I recommend the YOLO format to be used. This way the coordinates will be independent of the image size (which can vary)

@ben-norton Thanks for your thoughts on this. To give you context: We discussed this issue today in a [trapper ](https://gitlab.com/trapper-project/trapper) meeting. We were wondering how to deal with this. In...

A lively dicussion, I like it! @peterdesmet Options 1 & 2 is what we (and I guess what we all do now). I really like option 3 (creating a designated...

To add another scenario with failure times: A defective flash! Currently we would have to create a deployment for the daylight period of every day. We typically have 3-4 month...

@kbubnicki correct!

1. **object** is a spatial region in a picture or video frame. 2. a temporal region to me in clearly an **interval**. (I got used to [lubridates terminology](https://lubridate.tidyverse.org/reference/lubridate-package.html#timespans)) 3. good...

In this context, I would prioritize the object rather than the interval, as the object is of primary interest. The combination of objects and their temporal presence is particularly relevant...

good point! I would see more categories though: -no flash -white LED flash -infrared LED flash -black LED flash -white Xenon flash A Xenon white flash is very different from...

I agree with @Tim-Hofmeester on this. Settings are very manufacturer specific. To be honest, I feel like we could put the attributes of interest into the observationTags column? Just to...