New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use scooby for Versions #792
Conversation
Btw, what do you think about having the same in |
Or what if it were only in |
I changed
to
I assume SimPEG is moving to numpydoc-style too, right? |
No, I don't think that is good. SimPEG is the main package. So it should have it. It is where everything comes together. discretize could have it too, as it can be used standalone, but not necessary. Because always when you use discretize then you will use something else too; e.g. SimPEG, or emg3d, or similar. And those tools should have it, IMO. |
That makes sense so that SimPEG could specify specific packages and hardware which might not be relevant to other packages leveraging |
Codecov Report
@@ Coverage Diff @@
## simulation #792 +/- ##
===========================================
Coverage 71.22% 71.22%
===========================================
Files 118 118
Lines 19092 19092
===========================================
Hits 13599 13599
Misses 5493 5493 Continue to review full report at Codecov.
|
We might think of renaming it from The reason is that @banesullivan and I think/hope/expect that Just thinking out loud, ideas/opinions welcome. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @prisae and @banesullivan for making this happen 🎉
Just one comment wrt making it a soft dependency rather than putting it in the setup.py
. Other than that, this looks great!
Also 👍 from me on renaming to be consistent with scooby
going forwards. It is a straightforward change in people's code, so might as well take care of it right away
setup.py
Outdated
@@ -43,6 +43,7 @@ | |||
'vectormath>=0.2.0', | |||
'discretize>=0.4.0', | |||
'geoana>=0.0.4' | |||
'scooby>=0.3.0', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think of making this a soft dependency? Since it isn't strictly necessary for running simulations or inversions with SimPEG, I would be inclined to make it a soft rather than a hard dependency
Yes, I was thinking about making it a soft dependency just like matplotlib in discretize. I opted not to, as scooby is tiny compared to matplotlib. I'll implement that! If not today than later in the week. |
A very quick implementation, not really tested yet... |
My input, FWIW: while yes, we are still house-training Why? Lately, PyVista has been gaining a lot of users that don't have a strong Python background and they've been happy to report bugs/generate issues but it was becoming an challenge to work with numerous users to report everything we needed to know about the environment and the computer. My solution: have So I guess Edit: a minority of our users leverage anaconda, so that's really where the issue arose |
@banesullivan thanks for the input. @lheagy I can leave the soft dependency in or make it hard again, depending on what you folks want. Maybe you can raise it today at the meeting? Either way: The Also, |
There is actually a much simpler way in this case than
This is all that is needed to make it a soft dependency. And it prints the useful info. Edit: I edited the implementation to avoid a name-clash with the actual Report class later. |
@prisae - I like that soft dependency implementation a lot! Maybe we should tag that for |
Yes, like this it is very minimal. We could even put it on the |
Maybe just the docs - maybe make an issue over there so we don't forget about this? |
Done: banesullivan/scooby#32 |
I believe the fail is ones again related to the Google Cloud SDK thingy... |
Thanks for pushing on this! I am at a conference this week and am again behind on things... but I will jump back in in a week or two |
Two warnings from the Travis-log (run 10 - docs) which might need some action?
|
@jcapriot , could this PR (or the branch |
I'm going to switch the merge request to the simulation branch, and merge those changes into here to check, but I don't think this will cause any issues. A few things, cython is not technically a requirement for SimPEG, it is a requirement of discretize. The old |
Great, thanks @jcapriot ! |
# Conflicts: # SimPEG/__init__.py # SimPEG/utils/printinfo.py # docs/content/api_core/api_Utils.rst # examples/06-dc/plot_dc_schlumberger_array.py # examples/06-dc/read_plot_DC_data_with_IO_class.py # examples/07-fdem/plot_loop_loop_2Dinversion.py # examples/09-tdem/plot_inductive_src_permeable_target.py # requirements_dev.txt
Use
scooby
internally forVersions
. Now that scooby exists (thanks @banesullivan ) we should use it to simplify our lives. This removes lots of code from SimPEG, and will make maintenance easier down the road.It is a bit a shame this comes only a few days after https://github.com/simpeg/simpeg/releases/tag/0.11.5 - but the development of scooby came a bit unexpected and fast.
However, there is absolutely NO change to the API / for the user. Everything remains the same.
In the end, the work we did with
Versions
inSimPEG
(and inempymod
/emg3d
) all led toscooby
, so it was well invested time ;-)