-
Notifications
You must be signed in to change notification settings - Fork 8
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
Strategy for Fortran STOP #5
Comments
I like first option the most bc it jives with the rest of the code. Can we use the existing functionality for setting the error message? @mwtoews , do you have a feel for how much effort it would be to patch these stops to be more amenable to library calls? Im happy to help on this front if you can work a strategy/approach..or we can divide and conquer? |
Wrt option 1 to refactor Fortran, I'll take a look at what John as done and see if I can catch "INVALID power variogram" as a start. But also, raise this with John when you get a chance. |
So do think most of the |
I've started some data validation strategies with d470ed5 which operate on either scalars or vectors. E.g., here for pypestutils/pypestutils/core.py Lines 187 to 194 in d470ed5
These will be expanded elsewhere later. |
As mention in #3 (comment) there are potential issues with the Fortran STOP statements, which will exit the Python process.
Find them in
src
with:There are approx. 50 of these in
src
, mostly with gslib's sgsim_code.f90.There are a few strategies:
The text was updated successfully, but these errors were encountered: