Felix Hennings

FYI: the problem no longer consists in `latest`

I though a little about this, and I think your expectation does make sense. However, I'm curious on what should happen if the multiplication does involve two variables. Currently `level...

After some more time spend on this, I found at least two solutions/work arounds for this. Both create a corresponding `linopy.LinearExpression` instead of a `linopy.Variable`, but that's fine for me....

@FabianHofmann Thanks for the fast response! `level.loc[ind]` was exactly what I was looking for, thanks a lot! It's also reasonably fast compared to standard `.roll(time=1)`. However, I'm a little confused...

Good question. I'm not sure about the logger, as it would produce just noise for those who are aware. Also it wouldn't have helped me, as you need to accidentally...

I would be happy to adjust the documentation (and also incorporate the result of the discussion in #257 ) :slightly_smiling_face: However, I will probably not have time today and next...

Hi @odow, thanks for the link. From my point of view, a summary of the part relevant for this issue would be: > Tolerances and presolving may influence the feasibility/infeasibility...

@fwesselm Thanks for the check and also the tip with the feasibility tolerance. This helps a lot as a work-around!

@fwesselm Thanks for the analysis. I didn't expect that lowering the `mip_feasibility_tolerance` tolerance would resolve both this issues as well as #1959 . It also fixed all the other (unreported)...

A short update: Some weeks ago, we updated the scaling of some of the constraints in the model generation for our application. On a larger test set of instances (400+)...