Talk:Metallic ratios: Difference between revisions

From Rosetta Code
Content added Content deleted
(Question the initial values for the "Lucas sequences")
Line 4: Line 4:


: Why is it that you call my 10,000 decimal digit example (REXX) an insane precision,   but 1,000,000 was extremely precise?   In any case, it has been deleted.   But, my reason wasn't to see extremely precisely calculated values of phi.     -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 01:30, 2 November 2019 (UTC)
: Why is it that you call my 10,000 decimal digit example (REXX) an insane precision,   but 1,000,000 was extremely precise?   In any case, it has been deleted.   But, my reason wasn't to see extremely precisely calculated values of phi.     -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 01:30, 2 November 2019 (UTC)

::I didn't intend to call specifically '''your''' example insane. (Though I admit, effectively I did and I apologize for that.) I just wanted to head off people adding larger and larger dumps of digits to the page. Posting the number of iterations it took to determine is cool, and is moderately interesting/useful information that is not easily found in other places. Something perhaps like:

Reached 1000 after 2395 iterations.
Reached 10000 after 23927 iterations.
Reached 100000 after 239250 iterations.
... whatever ...

::The actual value though? That's easily available in other places. I used the adjective insane because posting it here just forces '''everybody''' to scroll through huge walls of low information text. I debated even just asking for the iteration count for the stretch goal. --[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 12:37, 2 November 2019 (UTC)


== Initial values for the "Lucas sequences" ==
== Initial values for the "Lucas sequences" ==

Revision as of 12:37, 2 November 2019

Please don't add unnecessarily large outputs

If you want to demonstrate calculating the ratio to insane precision past 256 decimal places, fine, but please just put how many iterations it took, not the calculated value. It doesn't really add anything. If you really want to see extremely precisely calculated values for phi, here's it is to one million places. --Thundergnat (talk) 18:19, 1 November 2019 (UTC)

Why is it that you call my 10,000 decimal digit example (REXX) an insane precision,   but 1,000,000 was extremely precise?   In any case, it has been deleted.   But, my reason wasn't to see extremely precisely calculated values of phi.     -- Gerard Schildberger (talk) 01:30, 2 November 2019 (UTC)
I didn't intend to call specifically your example insane. (Though I admit, effectively I did and I apologize for that.) I just wanted to head off people adding larger and larger dumps of digits to the page. Posting the number of iterations it took to determine is cool, and is moderately interesting/useful information that is not easily found in other places. Something perhaps like:
   Reached 1000 after 2395 iterations.
   Reached 10000 after 23927 iterations.
   Reached 100000 after 239250 iterations.
   ... whatever ...
The actual value though? That's easily available in other places. I used the adjective insane because posting it here just forces everybody to scroll through huge walls of low information text. I debated even just asking for the iteration count for the stretch goal. --Thundergnat (talk) 12:37, 2 November 2019 (UTC)

Initial values for the "Lucas sequences"

The initial values (1, 1) do not give the actual Lucas sequences used in mathematics. The Lucas sequences U_n(P,Q) and V_n(P,Q) are defined with the following initial values: U_0(P,Q) = 0, U_1(P,Q) = 1, and V_0(P,Q) = 2, V_1(P,Q) = P.

For example, A006190(n) = U_n(3, -1), which, by definition, has the property that the ratio between successive terms converges to the bronze ratio.

On the other hand, there is no mentioning of "Lucas" or "bronze" in A003688.