Amin Sadeghi
Amin Sadeghi
Basically, it's not obvious that the user should do `obj.regenerate_models()` after `obj.add_model_collection(mods)`, and `OpenPNM` doesn't inform the user what's wrong. The end result is that the algorithm can't run since...
```python import numpy as np import openpnm as op np.random.seed(10) np.set_printoptions(precision=5) ws = op.Workspace() ws.settings["loglevel"] = 10 proj = ws.new_project() shape = [13, 29, 1] net = op.network.Cubic(shape=shape, spacing=1e-4) mods...
We used to have this, but seems to have been removed in v3 changes.
It might be useful to publish nightly builds to `conda-forge`, ex. `openpnm-dev` or `openpnm-nightly`, which essentially installs the latest dev version.
For carrying out direct numerical simulations, it would be handy if we had a `DNS` geometry tailored for that purpose. It would simply be a bunch of cubic models (volume,...
When running a script twice (or just running that specific line where the BCs are being applied twice), `OpenPNM` complains that some of the pores already have some BCs assigned.
When using gauge pressure, some models break down silently, for instance the diffusivity model for `Air`. Maybe we should advertise somewhere so users don't use gauge pressure at all.
The solution object is already attached to the algorithm, so I think no need to return it as well. Plus, the `run` method doesn't imply returning anything, so nobody really...