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
Running load_video_frames on different operating systems leads slightly different values.
For example,
vs.
on linux vs. mac with the same ffmpeg version (4.4.3) and same python environment.
Value differences are off by 2 at a max (diffs are either 0, 1, or 2). The loaded frames look the same to the naked eye but are enough to generate slight differences in model predictions.
For example, the bounding boxes are almost identical but the confidences are on either side of the threshold we use for selecting frames for distance estimation (0.25).
The label with the max probability is the same, but the exact values differ.
It's unclear exactly what's causing this difference and how to resolve it. For now, it's worth knowing that we don't have exact replicability across operating systems.
The text was updated successfully, but these errors were encountered:
Running
load_video_frames
on different operating systems leads slightly different values.For example,
vs.
on linux vs. mac with the same ffmpeg version (4.4.3) and same python environment.
Value differences are off by 2 at a max (diffs are either 0, 1, or 2). The loaded frames look the same to the naked eye but are enough to generate slight differences in model predictions.
For example, the bounding boxes are almost identical but the confidences are on either side of the threshold we use for selecting frames for distance estimation (0.25).
These differences in the frame selection model will have downstream impacts on depth and species predictions.
For example
vs.
The label with the max probability is the same, but the exact values differ.
It's unclear exactly what's causing this difference and how to resolve it. For now, it's worth knowing that we don't have exact replicability across operating systems.
The text was updated successfully, but these errors were encountered: