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
Increase Precision in Failing Doctests #17238
Comments
comment:1
With
and Sage-6.4.beta6 installed I have the following doctest failures
which appear to be precision related. |
Branch: u/strogdon/increase_precision |
Commit: |
comment:3
Here is a partial push that may not work for everyone. It does work here. I'm not quite sure how to handle the failure
New commits:
|
comment:6
Replying to @strogdon:
Clearly, the intention of the test is to show that the zeros really are zeros. So I would replace it by
Don't forget your Author name. |
comment:7
I need a little more fixes on ppc64. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
Ahh! The nameless author(s). New commits:
|
Author: Steven Trogdon |
comment:10
Any idea why the test
was failing before? At first sight I see no reason... |
comment:11
The only thing that jumped out at me was that one of the zeros had no imaginary part. But I don't know why that would cause it to fail. No adjusting of the precision would allow it to pass unless I used abs(f(z)) Maybe something else is up? |
comment:12
Replying to @strogdon:
Because
doesn't match
no matter what the floating point numbers are. |
comment:13
Oh, I see... |
comment:14
Same issue with polynomials:
doesn't match
no matter the tolerance. |
Changed branch from u/strogdon/increase_precision to u/jpflori/ticket/17238 |
comment:16
For me there are now missing whitespaces in
|
comment:17
Oops, I indeed modified that one. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:20
This now works here. |
comment:21
Jeroen: would you mind having a final look at this? I basically agree with what Steven did and added minimal changes so that everything is fine on ppc64. |
comment:22
OK, I'm going to assume that it does indeed fix the problems you are having. |
comment:23
Please rebase this on top of #17126. |
Reviewer: Jeroen Demeyer |
comment:25
Done. Note that I also added a forgotten fix for ppc64 (in a separate commit)... |
comment:26
(As far as #17126 is concerned, the merge slightly increases the tolerance.) |
comment:28
Sure, in fact for all the tolerances I used, I checked it was the minimal one needed on ppc64. |
comment:29
And it only goes from 1e-13 to 4e-13. |
comment:30
In the |
comment:31
Yes I think we can. |
comment:32
I'm changing the doctest now. |
comment:33
But I'll also have to use |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:35
I've harmonized everything with #17126. |
Changed branch from u/jpflori/ticket/17238 to |
Certain doctests may now fail due to precision issues. This is apparently a consequence of #16858. For reference see
https://groups.google.com/forum/#!topic/sage-release/jdhuVBY7rLU
CC: @jpflori
Component: doctest coverage
Author: Steven Trogdon, Jean-Pierre Flori
Branch/Commit:
ec64d52
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/17238
The text was updated successfully, but these errors were encountered: