iOS best practices for only tracking long recordings

Posted by AP on
URL: http://official-rtab-map-forum.206.s1.nabble.com/iOS-best-practices-for-only-tracking-long-recordings-tp10300.html

I am working on a project recording movement in an irregular outdoor space. I am doing 20+ minute recordings on iOS in a rugged, outdoor area with the phone attached to a person.

I am interested in a reliable and robust track without any drift, but I do not need much in terms of 3D scan results. I need just enough reference geometry to align multiple tracks together and align them to a photogrammetry scan of the same region. In the end I am taking the motion data into VFX tools (Blender -> Unreal Engine).

I have been using some of the basic ARKit-based apps, but I have been having issues with crashing and lost data, overheating etc. It occurred to me that RTAB-Map may be just the tool.

I have been testing the various settings and reading documentation but I was wondering if anyone could point me to best practices for this use case? Ideally biasing towards lowest possible RAM and performance, battery etc. impacts while capturing, with a reliable offline post-processing stage.

Do you have any recommended best practices for this use case based on the iOS app on the App Store?