pschultzendorff

> Hello again everyone, > > if I have understood correctly so far this is actually not a feature request but a bug. Today I moved photos within the app...

> @pschultzendorff: I did not really think through the example spe11.py that is included in the PR. My instinct is that all two-phase models should be created through the compositional...

Just my two cents: ``save_data_time_step`` also calls ``solver_statistics.save`` in addition to exporting data. Removing ``self.save_data_time_step()`` from ``after_nonlinear_failure`` would eliminate any trace of failed time steps. Then one could no longer...

I discussed this briefly with @vlipovac yesterday, and we agreed that it's not urgent and better be done once some more things are in place. This issue serves mostly as...

To expand on Yury’s approach: In `vizviewer`, the standard view displays all method calls in hierarchical order as they occur during runtime. To find the methods with the longest runtime...

TODO - Yury creates a 2D and a 3D poromechanics benchmark - Peter writes a script that runs viztracer and vizviewer on a chosen benchmark and allows some simple user...

An argument against performance tracking with github actions: We have neither a guarantee that github consistently employs the same resources, nor can we find out which resources it employs. In...

@keileg Yes, that is done by PorePy and the required information is actually stored as a variable at some point. However, when creating the subdomains, this information gets lost. See...

Good to hear that it will stay relevant, as I definitely need it for my two-phase flow code :D I assume you are referring to #760 regarding the inconsistencies @vlipovac?...

The second point is addressed by #1471 , currently without the functionalities introduced by #1448 though