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

validate run time limit for all problem instances/tasks #50

Open
jp7745 opened this issue Dec 9, 2024 · 1 comment
Open

validate run time limit for all problem instances/tasks #50

jp7745 opened this issue Dec 9, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@jp7745
Copy link
Member

jp7745 commented Dec 9, 2024

No pull requests until after 10-Dec deliverables.

ensure all run time limits are set to reasonable values. This values determines if a solver succeeds or fails at solving a problem.

fixing problem instances in place is OK. any other scripts that generate problem instance JSON files should be updated as well.

@jp7745 jp7745 added the enhancement New feature or request label Dec 9, 2024
@jp7745
Copy link
Member Author

jp7745 commented Dec 17, 2024

@aakunitsa and @jtcantin reminder about this issue:

All of our time_limit_seconds fields for tasks are either 86400 (1 day) or 172800 (2 days). I want to revisit this for all Hamiltonians and determine if this blanket requirement is too tight and should be relaxed for some larger Hamiltonians (e.g., time_limit_seconds = 604800 (1 week)).

The time limit is important because it dictates whether a solver (or resource estimate) passes or fails in terms of "solving" the problem.

You can revisit the Hamiltonians manually or systematically, but either way, please use your subject matter expertise and experience to suggest reasonable time limits that suggest utility.

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

3 participants