You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I encounter identical sequenceID's for several timeLapse photo's and motionDetection sequences. When retracing these sequences in Agouti, I arrive at the timeLapse image, instead of the sequence of the detection of the animal. Which is ofcourse not desired.
Could you explain the reasoning behind this, or is this an issue to fix.
I am using the alternative installer though github, provided by marcus rowcliffe in december, which downgrades camtraptor 1.0 to 0.1.6. Due to compatibility issues with a research project from EFSA.
Also see the following message after loading data:
The dataset uses Camtrap DP version 1.0, it has been converted to 0.1.6.
The text was updated successfully, but these errors were encountered:
Hi @lrdijkhuis, sorry for the late response. What you describe might be a bug in Agouti. Can you provide some examples of a sequenceIDs that is (re)used for a timelapse and detection sequence?
Currently, I encounter identical sequenceID's for several timeLapse photo's and motionDetection sequences. When retracing these sequences in Agouti, I arrive at the timeLapse image, instead of the sequence of the detection of the animal. Which is ofcourse not desired.
Could you explain the reasoning behind this, or is this an issue to fix.
I am using the alternative installer though github, provided by marcus rowcliffe in december, which downgrades camtraptor 1.0 to 0.1.6. Due to compatibility issues with a research project from EFSA.
Also see the following message after loading data:
The text was updated successfully, but these errors were encountered: