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

bound behaviour for irace's target-runner #5

Open
DE0CH opened this issue Dec 30, 2023 · 1 comment
Open

bound behaviour for irace's target-runner #5

DE0CH opened this issue Dec 30, 2023 · 1 comment

Comments

@DE0CH
Copy link
Owner

DE0CH commented Dec 30, 2023

Current Logic

check the [bound] in irace's target-runner. If the surrogate predicts larger than bound, return bound + 1, else return the surrogate prediction

For context, irace's target-runner command line args

<id.configuration> <id.instance> <seed> <instance> [bound] <configuration>

Future Task

A better solution would be to check if "prediction>=bound" and "status=timeout" (the surrogate returns some extra info, I think we looked into it previously). This is to avoid cases where the prediction is exactly as bound, i.e., cplex solves the instance within exactly [bound] time, but I think it's unlikely, so we may be able to skip that.

This is not needed for now, we can just skip it and add it in later if needed.

@ndangtt
Copy link

ndangtt commented Mar 4, 2024

@DE0CH: based on Manuel's reply:
MLopez-Ibanez/irace#66 (comment)

we should return bound + 0.1 in the target-runner (for both fields: solution quality and runtime) if the surrogate returns timeout.

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

No branches or pull requests

2 participants