Stephan Rave

> What I was trying to ask is why do you think torch.sparse is better if it doesn't support better formats than pydata/sparse (some generalization of CSR/CSC)? I am just...

I don't think we want to work on this any time soon, so I tagged it with the 'future' milestone.

I guess we should defer this until we have decided on how to implement #129.

This will be handled by @TiKeil.

You can definitely assume that the output functional is linear. Regarding the stiffness matrix, handling the non-symmetric case is probably most interesting. However, finding a pyMOResque way to deal with...

Hah, now that you have commented on the issue I can assign you, @TiKeil ...

What about an `estimator` with an `estimate(..., return_output_estimate=False)` method and an `estimate_output()` method, and add another `estimate_output` method to the `Model`? While we are at it: I think `estimate` is...

> While thinking about solve_dual one could also think about generally providing a DualModel which is somehow available in Model and can also be used independently of the output bound....

Will not happen before release. Moving to next release.

Is the documentation built somewhere? Can't find it on `https://docs.pymor.org/list.html`. Maybe you want to create a branch in the main repo and create a new PR?