You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, discretize is not a dependency, and all could be done with utils.TensorMesh. However, this leads sometimes to confusion, and the gain is little. The main reasons why discretize has not been made a dependency are removed:
So I think it is time to go all-in and make it a hard dependency (adjust docs and website) as soon as all boxes above are ticked and a release happened (pin the version then); utils.TensorMesh should then only be used internally.
I think the best would be to do in emg3d.meshes
from discretize import TensorMesh
and then rename the meshes.TensorMesh to meshes._TensorMesh, for internal use of the solver only.
Adjust accordingly:
emg3d.meshes
emg3d.io save/load
example-gallery
website
REAMDE
install instructions in docs
The text was updated successfully, but these errors were encountered:
Currently,
discretize
is not a dependency, and all could be done withutils.TensorMesh
. However, this leads sometimes to confusion, and the gain is little. The main reasons why discretize has not been made a dependency are removed:matplotlib
is no longer a hard dependencypymatsolver
is no longer a dependency (Remove pymatsolver simpeg/discretize#193)conda
numpy
So I think it is time to go all-in and make it a hard dependency (adjust docs and website) as soon as all boxes above are ticked and a release happened (pin the version then);
utils.TensorMesh
should then only be used internally.I think the best would be to do in
emg3d.meshes
and then rename the
meshes.TensorMesh
tomeshes._TensorMesh
, for internal use of the solver only.Adjust accordingly:
The text was updated successfully, but these errors were encountered: