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
The process graph introduced in #540 exposes some places where our code does not align with a pure bipartite graph model, where processes produce and consume whole products, without modification. For instance, the two-view correspondences are triangulated in a class method before the BundleAdjustment Process takes over, which we had to hack around in the graph with a "Triangulated Points" Product with no source.
Another issue arises in the Image Retriever/Loader system, where Retriever takes Loader as an argument and then simply calls Loader over a directory. This makes Loader both a Process and a input "Product" of Retriever. We can accept this as a weird quirk or potentially merge Retriever and Loader into one Process.
These should be resolved by changing the underlying code to conform to the process/product model, then fixing the UiMetadata objects in the right classes.
The text was updated successfully, but these errors were encountered:
The process graph introduced in #540 exposes some places where our code does not align with a pure bipartite graph model, where processes produce and consume whole products, without modification. For instance, the two-view correspondences are triangulated in a class method before the BundleAdjustment Process takes over, which we had to hack around in the graph with a "Triangulated Points" Product with no source.
Another issue arises in the Image Retriever/Loader system, where Retriever takes Loader as an argument and then simply calls Loader over a directory. This makes Loader both a Process and a input "Product" of Retriever. We can accept this as a weird quirk or potentially merge Retriever and Loader into one Process.
These should be resolved by changing the underlying code to conform to the process/product model, then fixing the UiMetadata objects in the right classes.
The text was updated successfully, but these errors were encountered: