Skip to content
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

probit transform integer return code? #817

Open
hkershaw-brown opened this issue Jan 30, 2025 · 2 comments
Open

probit transform integer return code? #817

hkershaw-brown opened this issue Jan 30, 2025 · 2 comments
Labels
QCEFF quantile conserving filters

Comments

@hkershaw-brown
Copy link
Member

hkershaw-brown commented Jan 30, 2025

why use an integer return code? For different types of failures?
The oks are logicals.
logical, allocatable :: obs_probit_trans_ok(:), state_probit_trans_ok(:)

Originally posted by @hkershaw-brown in #794 (comment)

@hkershaw-brown
Copy link
Member Author

Comment on lines +509 to +510

This is related to the question about the error code being an integer, if you had the error be a logical you could do:
call transform_to_probit(........., state_probit_trans_ok(i))

that way you there is less chance of a future person, putting something in the middle of these two statements.

call transform_to_probit(....., ierr)
call something_else_mathsie(.....,ierr)
state_probit_trans_ok(i) = (ierr == 0)

@hkershaw-brown
Copy link
Member Author

#794 (comment)

The added if(obs_probit_trans_ok(i)) & at line 511 gives you the same answer as before, because of the bnrh

fail -> ! Just return the original ensemble
I guess this is for algorithm readability?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QCEFF quantile conserving filters
Projects
None yet
Development

No branches or pull requests

1 participant