Talk:Cuban primes: Difference between revisions
Content added Content deleted
m (→Python not correct: added a comment.) |
m (→Python not correct: reported on fixed typo) |
||
| Line 14: | Line 14: | ||
: I've included a <big> <nowiki> {{incorrect|Python}} </nowiki> </big> statement to flag the Python entry as incorrect. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 20:35, 9 June 2019 (UTC) |
: I've included a <big> <nowiki> {{incorrect|Python}} </nowiki> </big> statement to flag the Python entry as incorrect. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 20:35, 9 June 2019 (UTC) |
||
:: Looks like whomever translated it managed to put a variable name "u" in place of a "v" in the "mx = int(math.sqrt(v))" statement. Works a lot better now. Also the mx var was from 1 instead of 0, but it's unknown if that contributed to the issue.--[[User:Enter your username|Enter your username]] ([[User talk:Enter your username|talk]]) 02:16, 10 June 2019 (UTC) |
|||
Revision as of 02:16, 10 June 2019
Why so large?
I don't know why to choose such a big number "show the 100,000th cuban prime." It take me above 2min runtime. the 6635th cuban prime 4293894169 is the last < 2^32. --Horst.h (talk) 11:33, 1 February 2019 (UTC)
- My theory is that Gerard lives in the upper midwest of the US and is trying to heat his house with his processor. 🤔 --Thundergnat (talk) 13:44, 1 February 2019 (UTC)
- That specific number was the only cuban prime of any substance that could be verified as being correct. If anyone had a reputable web page that has a reference to a smaller number, I would've used that instead. So Thundergnat's theory falls flat. -- Gerard Schildberger (talk) 14:10, 1 February 2019 (UTC)
- Darn! :-) --Thundergnat (talk) 14:37, 1 February 2019 (UTC)
Python not correct
For instance, output includes 91.--Steenslag (talk) 14:05, 9 June 2019 (UTC)
- I've included a {{incorrect|Python}} statement to flag the Python entry as incorrect. -- Gerard Schildberger (talk) 20:35, 9 June 2019 (UTC)
- Looks like whomever translated it managed to put a variable name "u" in place of a "v" in the "mx = int(math.sqrt(v))" statement. Works a lot better now. Also the mx var was from 1 instead of 0, but it's unknown if that contributed to the issue.--Enter your username (talk) 02:16, 10 June 2019 (UTC)