Jon Niehof
Jon Niehof
55% - readepochs is untested - lots of hard-to-test plotting stuff
45%. - Huge chunks of stuff when have_libspacepy=False, should be easy (test twice and twiddle have_livespacepy between) - assoc_mult - applyRefractory More difficult: - plot_mult, maybe integration test - plot,...
This is hard to completely untangle because of the sub-imports, and I think a lot of these might depend on integration testing or another way of testing plots.
Coverage is at 51%. Some functions are completely untested; there's also a fair bit of plotting stuff that might require an integration test.
67%, big chunks untested that should be addressible.
Information from https://bugs.launchpad.net/ubuntu/+source/pam-shield/+bug/1455061 "Allow statements in the configuration file (/etc/security/shield.conf) aren't correctly matched against the connecting client if an IP-address or network has been entered." 'I tracked it down to...
This PR contains updates to the ISTP handling in datamodel, in particular adding support for parsing units strings and providing for output to a pandas DataFrame. Basically followup from #661....
Currently SpacePy warnings do not specify a stacklevel. That means the warning appears to be raised _in spacepy_ instead of the code we're warning about. We should use the `stacklevel`...
f2py on numpy 1.26+ and Python 3.12+ requires meson. I evaluated meson for migrating off distutils and it didn't meet our needs, so it doesn't make a lot of sense...
Quite a bit of our code assumes we have access to the files that make up SpacePy. In theory we should be able to import from a zip...this will probably...