You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for making the case study from your paper available! I'm trying to update the code to work against Julia 0.5.0, JuMPChance 0.3.0 and JuMP 0.14.1. I hope to work towards some computational tests of the CC/RCC approaches against scenario sampling to incorporate uncertainty.
I tried to fix al the depreciation warnings (Julia base / JuMP macro rename), but the problem seems infeasible now (all time steps). I tried both Gurobi and CPLEX, CC and RCC, both the reformulation and cut techniques (for CC).
Furthermore, It seems the meaning of the 'with_probability' keyword was switched (epsilon to 1-epsilon)?
I will send a pull request. In any case, thank you for your time and the contribution of this case study to the community! Tips/ hints welcome to solve this issue.
The text was updated successfully, but these errors were encountered:
frederikgeth
pushed a commit
to frederikgeth/RobustCCOPFSupplement
that referenced
this issue
Sep 21, 2016
See
Updating to be compatible with latest versions of Julia/JuMP/JuMPChance
mlubin#3
Updating for Julia 0.5.0, JuMPChance 0.3.0 and JuMP 0.14.1.
fix al the depreciation warnings
fix with_probability
Dear Miles,
Thank you for making the case study from your paper available! I'm trying to update the code to work against Julia 0.5.0, JuMPChance 0.3.0 and JuMP 0.14.1. I hope to work towards some computational tests of the CC/RCC approaches against scenario sampling to incorporate uncertainty.
I tried to fix al the depreciation warnings (Julia base / JuMP macro rename), but the problem seems infeasible now (all time steps). I tried both Gurobi and CPLEX, CC and RCC, both the reformulation and cut techniques (for CC).
Furthermore, It seems the meaning of the 'with_probability' keyword was switched (epsilon to 1-epsilon)?
I will send a pull request. In any case, thank you for your time and the contribution of this case study to the community! Tips/ hints welcome to solve this issue.
The text was updated successfully, but these errors were encountered: