This is a cross post from Github azure-spatial-anchors-samples
Description
I would like to have a better understanding of the values ReadyForCreateProgress and RecommendedForCreateProgress from Microsoft.Azure.SpatialAnchors.SessionStatus.
From what I've tested:
- ReadyForCreateProgress has a maximum of 2,5
- RecommendedForCreateProgress has a maximum of 2
- IsReadyForCreate on SpatialAnchorManager changes to true ReadyForCreateProgress is 1 and RecommendedForCreateProgress is 1.25
Questions
1. Is there is difference between using ReadyForCreateProgress and RecommendedForCreateProgress except that they have a different scale?
2. Can you explain how the values connect to tracking accuracy? E.g.: Is the scale linear so a if I have RecommendedForCreateProgress of 2 instead of 1 it will be double as good for recognizing it again?
3. Is it possible to increase the maximum to increase recognition?
4. We have a procedure in place that after a important anchor was created it has to be found again multiple times. This is to check if it works but also to improve the recognition rate. Has finding an anchor the same effect as having a higher ReadyForCreateProgress when saving, especial if the environment, like lighting stays the same?
5. When the maximum for ReadyForCreateProgress or RecommendedForCreateProgress is reached will the point cloud data still be refined or will the algorithm just stop?
Development information
- OS: Android \ iOS
- Development Platform\Version: Visual Studio 2019, Unity 2020.3.11f1
- Azure Spatial Anchors SDK version: 2.9.0