Fabian Hofmann

@leuchtum thank you for your issue. You are totally right, I and cannot remember why I did not named the keyword consistently with xarray... :( I would be very happy...

hey @robingirard, whereas linopy does not explicitly allow for tranposing the variables, you could do something like, ```python x + x.loc[x.coords["b"], x.coords["a"]] == 0 ``` Hope that helps!

very good that you look into this @apfelix, there is some inconsistency indeed. However, I would not fully have the same expectation on the operations. 1. In my point of...

Interesting, let me think about it. I would like to have the API change as small as possible, as changes can lead to very much unexpected behaviour.

Good point! This is one of the most important things on the list of missing features. In meanwhile, if you use `gurobi`, you can use the function ```python m.compute_set_of_infeasible_constraints() ```...

Interesting workaround :) However that would not work for indexed variables / constraints, as far as I can see. It would only insert the name. But given your thoughts, we...

Hey @apfelix, have you played around with .groupby("time.day") (this requires to have a date time index) with a subsequent rolling operation? Something like previous_level = level.groupby("time.day").roll(time=1) Or you can create...

Thanks for the nice feedback @apfelix :) happy to hear that. You are right about making this overriding feature clearer to the user base. From your direct experience now, where...

very good, thanks for the feedback! I will keep this issue then open (renamed it) and try to tackle that asap. If in the meanwhile you would like to make...

Sounds great! I will make a PR that fixes the remaining inconsistency discussed in #257