-
Notifications
You must be signed in to change notification settings - Fork 7
feat: update solver settings for CBA #627
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
Changes from 16 commits
fdd6c43
1950878
46057cf
c7f5ba7
c8a9afe
ea68ca5
b25ee61
249e3bf
af08156
a36b5ef
8afdbba
b5cea15
91d9929
87d8ec6
81ece62
69c1c70
12a84b7
af9f4a1
6e7ed82
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -348,6 +348,17 @@ class SolvingConfig(BaseModel): | |
| "PreDual": 0, | ||
| "GURO_PAR_BARDENSETHRESH": 200, | ||
| }, | ||
| "gurobi-simplex": { | ||
| "threads": 32, | ||
| "method": 1, # dual simplex | ||
| "NodeMethod": 1, # if MIP | ||
| "Seed": 123, | ||
| "AggFill": 0, | ||
| "PreDual": 0, | ||
| "FeasibilityTol": 1.0e-05, | ||
| "OptimalityTol": 1.0e-05, | ||
| "ScaleFlag": 0, # 0 to turn off scaling (faster) | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. While your test have shown slight speed up with ScaleFlag 0, I am contemplating if our best option wouldn't be to let Gurobi decide automatically how to scale the model (i.e. ScaleFlag -1). It could be that the speed up that we are seeing with 0 here, is only because of the small size of the test model (1 week). The settings will be used for MSV on a whole year, will they not? |
||
| }, | ||
| "gurobi-numeric-focus": { | ||
| "NumericFocus": 3, | ||
| "method": 2, | ||
|
|
||
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.
I think one could drop the
deepcopyas we are not reading the original snakemake.params.solving again but this is more robust, so let's keep it. Memory overhead is also negligable.