Updated frontend logger intialisation #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Outline
This pull request addresses an issue discovered when images are saved for purposes of investigating feature tracking in the frontend.
Reason for change
This issue occurs when Kimera-VIO is executed consecutively with different datasets—the contents of the directories within /output_logs/frontend_images are not cleared between runs. As a result, images from previous executions can mix with the current execution, leading to misleading results.
The following sub-directories are susceptible to the issue:
Proposed fix
Erase the contents of these directories when upon starting Kimera-VIO to avoid images from consecutive runs from being mixed together.