Thanks for the response!
I have a question about the JuMP model in my modified OBBT code and I am not sure here is the right place to ask it. I took your word about adapting OBBT code with the model constructor in PowerModelsAnnex. I added the model constructor in PowerModelsAnnex as a function to the OBBT code and passed several flags into the function (i.e., modelconstructor) to select which objective at which direction to be optimized.
The adapted OBBT code works properly and obtains the same solution that original OBBT obtains. However, the code gets super sluggish as it goes forward. Every time that the function (i.e., modelconstructor) gets called in the code, following warning shows up for all variables in the model:
Warning: A variable or constraint named va is already attached to this model. If creating variables programmatically, use the anonymous variable syntax x = @variable(m, [1:N], ...).
After each iteration variable’s bound get updated and there is no need to old model. Is there any way to get rid of the older model and build a new one for the next iteration in order to prevent the issue. I will appreciate your response!
All the best,