-
Notifications
You must be signed in to change notification settings - Fork 139
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
[WIP] Float tests #492
base: master
Are you sure you want to change the base?
[WIP] Float tests #492
Conversation
To do: why does |
Well, if we put it into % THIS EXAMPLE IS PART OF THE TESTSUITE. CHANGES HERE SHOULD BE APPLIED THERE AS
% WELL! (Float_1) |
The Edit: digits wise, I confirmed that there is agreement with |
Very funny indeed. It is the term
+89/18*mzv_(9,3,3)
that is the culprit. If you leave it out, it prints without the e+0 and if you include it but leave
the last term out, it just prints e.
Gotta have a good look on the linux computers, because gdb does not work on my apple.
I can leave some more terms out to just get the e, but I have not yet discovered the ‘pattern'
… On 11 Mar 2024, at 14:26, jodavies ***@***.***> wrote:
To do: why does F1 print with e+0 and F2 without? Which is the desired behaviour?
—
Reply to this email directly, view it on GitHub <#492 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJPCES4BYIDJ5YJLMYDUM3YXWWKBAVCNFSM6AAAAABEQJ5KHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYGQZTSOJXHE>.
You are receiving this because you are subscribed to this thread.
|
The ouput is truncated here: Line 950 in e99543a
If you ask for |
I was too hasty there, the issue is in the post-processing code that follows. As I understand it you would like the following:
Is this correct? |
I found the bug printing routine. One has to change Lines 962 to 963 in e99543a
to while ( n2 < n ) { *s1++ = *s2++; n2++; }
n -= (n2-n1); This will correctly truncate all trailing zeros, but leave the exponent intact. Removing "e+00" is not part of this routine. |
OK, please add the fix in your branch and lets see if the valgrind errors are gone. I can rebase this on top of your changes later. |
By the way, why is the precision of printed numbers strongly influenced by the maximum weight?
|
The final digit of pi is also not rounded correctly, is it understood why this is? |
Here I have added the example from the Madrid workshop slides.