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

Revisit hyperedge representation #104

Open
cmalinmayor opened this issue Jul 18, 2024 · 1 comment
Open

Revisit hyperedge representation #104

cmalinmayor opened this issue Jul 18, 2024 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@cmalinmayor
Copy link
Contributor

No description provided.

@cmalinmayor cmalinmayor added the enhancement New feature or request label Jul 18, 2024
@cmalinmayor cmalinmayor added this to the v1.0 milestone Jul 24, 2024
@cmalinmayor
Copy link
Contributor Author

Done improvements: Define HyperEdge as set of in nodes and set of out nodes, and add Type alias for these things.

Conclusion/TODO: Make a different collections for edges and hyperedges in TrackGraph and a different set of variables in the Solver. Mostly, Constraints want to treat them the same, but Costs generally need to handle them separately. This is more explicit, since you need to check which kind of edge you have anyways usually when handling them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant