-
Notifications
You must be signed in to change notification settings - Fork 67
Add new analysis to calculate finite difference #753
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
Conversation
… X values directly.
… keyword to write that to a file.
…is command and new integrate option 'intout'.
…command option intout (also fix up the integrate command entry in general).
This pull request fixes 1 alert when merging 78a5ea7 into c38a771 - view on LGTM.com fixed alerts:
|
All of the build failures appear to be related to external dependencies. E.g. a Travis failure:
This leads to a The appveyor failure happens when trying to download and compile NetCDF:
This could be a temporary hiccup so I'll try to retrigger that. Not sure what to do yet about Travis.. could be a temporary network issue or something deeper. |
Appveyor issue was actually |
This pull request fixes 1 alert when merging 2d58723 into c38a771 - view on LGTM.com fixed alerts:
|
Unimaginatively named
slope
(because I don't want to keep typingfinitedifference
):This PR also slightly reorganizes the
integrate
command and underlying routines. The integrate functions have been moved from DataSet_Mesh to DataSet_1D, which I think makes more sense (and avoids having to convert any given set to Mesh any time you want to integrate). Theintegrate
command now saves the integral values to a data set (not sure why I didn't do that in the first place) and has a new keyword to write these values to a file,intout <file>
.Documentation updated for both. Test added for
slope
.