-
Notifications
You must be signed in to change notification settings - Fork 29
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
adjoint tests sometimes fails for Gadgetron #637
Comments
likely a border case on the numerical threshold as there's nothing special for that job as far as I can see. |
It's only that one job https://travis-ci.org/github/SyneRBI/SIRF/builds/679325850 |
@AnderBiguri I'll have a look later, unless you volunteer... |
@KrisThielemans im happy to have a look. |
@KrisThielemans I cannot reproduce. Gadgetron adjoint test always return results 2 orders of magnitude lower ( |
@AnderBiguri the job listed in the first comment here is a linux job actually. It's more than likely that you cannot reproduce it as the other jobs are fine. i don't see anything in the flags really. I think best thing to do is to write diagnostics to stdout when the test fails. Otherwise we're just in the dark. |
@KrisThielemans fair. The fucntion has |
any reason we wouldn't have a test like this if not is_operator_adjoint(am, verbose=true):
... (or whatever appropriate Python syntax is) |
@KrisThielemans yes, what I mentioned in my previous comment. In any case, we can always increase the error bound by doing |
are you sure that By the way, I think the |
Ah @KrisThielemans my bad. Still a lot of these things elude me. Defaulting to |
no sure. let's see the diagnostics first! |
funny. the relevant job now passed. let's wait for the OSX tests but this update is good in any case. |
This seems to have disappeared, even though the only change in #638 was making verbose output the default. As there are no job failures anymore, I'll close this. |
@AnderBiguri We have one with a failure
seems indeed that our threshold is just too optimistic. Change it to 0.0002? |
(at least) one job on linux is failing after #636 https://travis-ci.org/github/SyneRBI/SIRF/builds/679325885. Error is simply
https://travis-ci.org/github/SyneRBI/SIRF/jobs/679325894#L31331
It'd be more useful to have some diagnostics as well then.
The text was updated successfully, but these errors were encountered: