Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simultaneous solvers use same CSMC / Tree? #673

Open
dehann opened this issue Apr 4, 2020 · 2 comments
Open

Simultaneous solvers use same CSMC / Tree? #673

dehann opened this issue Apr 4, 2020 · 2 comments

Comments

@dehann
Copy link
Member

dehann commented Apr 4, 2020

Picking up from #459 (comment)

@dehann dehann added this to the v x.0.0 milestone Apr 4, 2020
@dehann dehann changed the title Should multiple solvers use the same CSMC and Tree? Should multiple simultaneous solvers use the same CSMC and Tree? Apr 4, 2020
@dehann dehann changed the title Should multiple simultaneous solvers use the same CSMC and Tree? Should simultaneous solvers use the same CSMC and Tree? Apr 4, 2020
@dehann dehann changed the title Should simultaneous solvers use the same CSMC and Tree? Should simultaneous solvers use the same CSMC / Tree? Apr 4, 2020
@dehann dehann changed the title Should simultaneous solvers use the same CSMC / Tree? Should simultaneous solvers use same CSMC / Tree? Apr 4, 2020
@dehann dehann changed the title Should simultaneous solvers use same CSMC / Tree? Simultaneous solvers use same CSMC / Tree? Apr 4, 2020
@dehann
Copy link
Member Author

dehann commented Apr 6, 2020

Note, building a tree requires temporary changes in the factor graph object and hence only one tree can be built at a time, however, multiple trees can be used simultaneously on the same factor graph object after they have been built.

For most flexibility it might be best to try support both models as far possible (short of rebuilding the tree building process in the short term).

@dehann
Copy link
Member Author

dehann commented Apr 13, 2020

For trees, work towards a DFG style where TreeClique has all data common all solvers, but then TreeCliq contains a field as ::Dict{Symbol, BTND} used for each of the different solvers. This implies elements like potentials (#680) should move up to TreeClique, etc.

@dehann dehann modified the milestones: v x.0.0, v0.x.0 Jul 19, 2020
@Affie Affie removed this from Parametric Solver Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant