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.

Sign up for GitHub

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

Jump to bottom

Decision: how to measure the size of a problem #86

Closed
GiggleLiu opened this issue Aug 22, 2024 · 2 comments
Closed

Decision: how to measure the size of a problem #86

GiggleLiu opened this issue Aug 22, 2024 · 2 comments
Assignees
@SciCodePhy @c-allergic

Comments

@GiggleLiu
Copy link
Owner

So that we can measure the performance of a reduction rule properly.
@GiggleLiu
Copy link
Owner Author

@c-allergic @SciCodePhy please list the complexity of existing reductions.

@GiggleLiu
Copy link
Owner Author

We use a named tuple to annotate the size of a problem, e.g. (num_vertices = 5, num_edges = 10)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SciCodePhy SciCodePhy

@c-allergic c-allergic

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@GiggleLiu @SciCodePhy @c-allergic