Avoid dependent inputs in IncrementalMapperImpl #3043
Merged
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.
As mentioned in #3042, there are some dependencies in the graph that we need to take care of to avoid inconsistency, notably:
ObservationManager
andDatabaseCache
shares a sameCorrespondenceGraph
object, so should not be listed as input together to a static methodObservationManager
has a reference to theReconstruction
object, so should not be listed as input together with aReconstruction
object to a static methodThis PR contains the updates as follows:
NumCorrespondencesForImage
fromCorrespondenceGraph
rather thanObservationManager
to avoid dependent inputReconstruction
object to theObservationManager
class to avoid dependent input.