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
Description:
I was examining the Jupyter notebooks in Kimera-Evaluation when I noticed something strange. The feature count hovers around 300, then has periodic dips to as low as 100 features. After doing a little sleuthing, I discovered that these dips happen every maxFeatureAge number of keyframes, regardless of other factors. I suspect that when you initialize many features at once (like on startup or after a period of motion blur), they all expire at once and must be replaced. I suspect that the only features still being tracked at that point are ones generated from motion-- old features falling out of frame and being replaced by new ones.
Additional files:
Here are the feature graphs for a maxFeatureAge of 25, varying the intra_keyframe_time. Note that the periodic spikes always coincide with a multiple of 25 keyframes.
intra_keyframe_time = 0.2
intra_keyframe_time = 0.12
intra_keyframe_time = 0.1
intra_keyframe_time = 0.05
Console output:
I also ran the same inputs, but online. Here's a sample of the timing output. Note the huge disparity between max and average time-- I suspect this is because every maxFeatureAge of keyframes, a large number of features die off and must be recomputed.
Description:
I was examining the Jupyter notebooks in Kimera-Evaluation when I noticed something strange. The feature count hovers around 300, then has periodic dips to as low as 100 features. After doing a little sleuthing, I discovered that these dips happen every maxFeatureAge number of keyframes, regardless of other factors. I suspect that when you initialize many features at once (like on startup or after a period of motion blur), they all expire at once and must be replaced. I suspect that the only features still being tracked at that point are ones generated from motion-- old features falling out of frame and being replaced by new ones.
Command:
Additional files:
Here are the feature graphs for a maxFeatureAge of 25, varying the intra_keyframe_time. Note that the periodic spikes always coincide with a multiple of 25 keyframes.
intra_keyframe_time = 0.2
intra_keyframe_time = 0.12
intra_keyframe_time = 0.1
intra_keyframe_time = 0.05
Console output:
I also ran the same inputs, but online. Here's a sample of the timing output. Note the huge disparity between max and average time-- I suspect this is because every maxFeatureAge of keyframes, a large number of features die off and must be recomputed.
Please give also the following information:
The text was updated successfully, but these errors were encountered: