Ruslan Sadykov

Yes, this is the idea: we use `update_ip_primal_sol!()` to store only improving solutions. Otherwise the same solution may be stored several times (`orig_state` is usually initialized by `dest_state` in the...

We can rename EmptyStorage to FormulationStorage. Renaming `AbstractStorageState` to `AbstractDataState` is ok for me. I would also be good to rename `RuntimeData` (`ColGenRuntimeData`, `TreeSearchRuntimeData`, etc) to something else, as now...

We need this kind of structure to keep the intermediate data which is needed only during the run of the algorithm

I agree that in column generation is not that useful. However, for example, in the tree search algorithm we need to store the tree somewhere.

Ok, thanks Guillaume for posting this issue.

Ok, thank you, Guillaume. I think however that if the subproblem is unbounded, the master solution should also be declared as unbounded, no? It is not correct to declare the...

Also, I do not understand why the solution value (64.1429) when I set `@variable(model, 1>=x[m in M_axis, j in J]>=0);` is different from the root (fractional) solution value (70.3333) when...

Ok, I understood: _x_ variables are fractional also in the subproblem.

My understanding is that there should be a storage unit which keeps the tabu list of variables forbidden to the added to the partial solution. The dive algorithm generates the...

Dear @ZhaogangSu, Thank you for reporting this bug. I could reproduce it. This is the corrected version of the `my_pricing_callback()` function in the pricing example: ```julia function my_pricing_callback(cbdata) ## Retrieve...