I recently added the "complete" model classes (EnergyBalance etc.) to top-level init. The roll-out to the code was postponed to this issue. I think we should also provide access to and use pp.PorePyModel. Do you agree, @Yuriyzabegaev?
While the implementation is straightforward, it touches enough files that we will try to time it to control the number of conflicts with other PRs.
I recently added the "complete" model classes (EnergyBalance etc.) to top-level init. The roll-out to the code was postponed to this issue. I think we should also provide access to and use pp.PorePyModel. Do you agree, @Yuriyzabegaev? While the implementation is straightforward, it touches enough files that we will try to time it to control the number of conflicts with other PRs.