Pose3SLAM benchmark nondeterministic
Open
- Dominant language
- Swift
- Stars
- 118
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that the Pose3SLAM benchmark gives me different final losses every time that I run it. As far as I know, all the computations should be deterministic.
We should get to the bottom of this because it might indicate a bug. For example, the generic factor graph datastructure uses unsafe memory operations, and we might be reading uninitialized memory somewhere.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.