Uh oh!
There was an error while loading. Please reload this page.
Change addConsNode to (also) accept ExprCons - #418
Conversation
fserra
commented
Aug 25, 2020
thanks. I think it would make sense to factor out the code that creates the linear constraint since it also appears in Regarding the name and if it should also be part of An alternative would be to remove |
CharJon
commented
Aug 25, 2020
Personally I think the addPyCons naming is a bit confusing, as the |
I prefer having a nice and easy-to-use method |
I created a new method |
mattmilten
left a comment
There was a problem hiding this comment.
Looks good to me. Just the CHANGELOG entry is missing.
SanielDous
commented
Jul 20, 2022
Did this find its way into master branch already? Would be really nice |
I am implementing the branch and price where I need to add a linear constraint to the newly created node in branching rule. I am facing the exact same problem stated here. |
SanielDous
commented
Aug 23, 2022
zzy-opt
commented
Aug 23, 2022
@SanielDous Thank you. It seems this cannot be fixed in short term. Maybe I had better figure out how to use cython and change source code myself. |
Based on discussion in #416
To keep the prototype simple a new addExprConsNode method is added.
Do you prefer having addConsNode accept ExprCons only or both (Constraint and ExprCons)?