-
Notifications
You must be signed in to change notification settings - Fork 18
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
Parameter defaults update #48
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Does generate-defaults.py still work?
God damn it 😂 |
What's the rationale behind excluding parameters with inf defaults? |
I can't quite recall. At one point I was using comparison with defaults to generate a run name automatically e.g. |
I'll test it out and see how it goes |
If you're referring to the functionality provided by I tested this with two logs, one with TimeLimit=15, and the other with defaults (so TimeLimit=inf). The "Infinity" values are default so they're never picked up as a changed parameter and the resulting log names were:
Is there a chance I've missed something? Assuming this works ok, I'll modify generate_defaults.py to allow infinite valued parameters then regenerate the new json files with the script. |
Sounds good, not sure what I was thinking there. Makes sense to have the infinite defaults included as well. |
Addresses #47
I have just dumped all parameters into the JSON, whose value is not an empty string, including ones that are not useful for gurobi-logtools, such as Tune*.
Perhaps a bit overkill, but from what I can tell it won't hurt, and makes life easier.