PDQ Algorithm: Infinite precision best fraction within tolerance

02242019, 10:29 PM
(This post was last modified: 02242019 10:56 PM by cdmackay.)
Post: #21




RE: PDQ Algorithm: Infinite precision best fraction within tolerance
(12132013 05:09 AM)Joe Horn Wrote: Examples (performed in CAS, not Home, for perfect accuracy): (02242019 08:36 PM)smartin Wrote: Example #2: pdq(\(\pi\),14) = \(\dfrac{111513555}{35495867}\) I get pdq(\(\pi\),14) = \(\dfrac{47627751}{15160384}\), on the Android emulator (2.1.14181) in both Home & CAS, using the code that I copied and pasted directly into the program editor, from the first post in this thread. edit: I get the same on my Prime G2, and also the MacOS virtual Prime (both same firmware as above) using the hpprgm files downloaded from hpcalc. shouldn't be relevant, but: Number Format: Standard, 12 epsilon: 1e12 Cambridge, UK 41CL 12/15C DM15/16 71B 17B/BII/bII+ 28S 42S/DM42 48GX 50g 35s 30b/WP34S Prime G2 & Casios, Rockwell 18R :) 

02252019, 11:10 AM
Post: #22




RE: PDQ Algorithm: Infinite precision best fraction within tolerance
(02242019 08:36 PM)smartin Wrote: Finally inspired to try out PDQ on the Prime, but I could not get all the examples to work out. I'm using PDQ from hpcalc.org (https://www.hpcalc.org/details/7477) on a Prime with CAS ver 1.4.9 and ROM 2.1.14181. That's because you are using the builtin pi, which is less accurate than the precision you're asking for. Instead of using the builtin pi, use PI500 as your input instead; it's accurate to 500 digits. PI500 is available in the original posting. <0ɸ0> Joe 

02252019, 05:56 PM
Post: #23




RE: PDQ Algorithm: Infinite precision best fraction within tolerance
(02252019 11:10 AM)Joe Horn Wrote: That's because you are using the builtin pi, which is less accurate than the precision you're asking for. Instead of using the builtin pi, use PI500 as your input instead; it's accurate to 500 digits. PI500 is available in the original posting. Joe, how is it that I get the same value as in your post, using the inbuilt pi, but smartin gets a different value using the same expression as me? Cambridge, UK 41CL 12/15C DM15/16 71B 17B/BII/bII+ 28S 42S/DM42 48GX 50g 35s 30b/WP34S Prime G2 & Casios, Rockwell 18R :) 

02262019, 03:17 AM
Post: #24




RE: PDQ Algorithm: Infinite precision best fraction within tolerance
(02252019 05:56 PM)cdmackay Wrote: Joe, how is it that I get the same value as in your post, using the inbuilt pi, but smartin gets a different value using the same expression as me? Perhaps he accidentally keyed pdq(pi,15) instead of pdq(pi,14). That's just a guess, but it seems likely, since his result is the correct output for pdq(pi,15). <0ɸ0> Joe 

02262019, 03:45 PM
Post: #25




RE: PDQ Algorithm: Infinite precision best fraction within tolerance
(02262019 03:17 AM)Joe Horn Wrote: Perhaps he accidentally keyed pdq(pi,15) instead of pdq(pi,14). That's just a guess, but it seems likely, since his result is the correct output for pdq(pi,15). argh! Cambridge, UK 41CL 12/15C DM15/16 71B 17B/BII/bII+ 28S 42S/DM42 48GX 50g 35s 30b/WP34S Prime G2 & Casios, Rockwell 18R :) 

« Next Oldest  Next Newest »

User(s) browsing this thread: 1 Guest(s)