Talk:GF Divisor 403134228128830952985966466566...11(65) 11

Should this be converted to a long number? Gary Barnes (talk) 13:27, 10 June 2024 (UTC)

Sure, I've filled the number with the real digits to complete the xGF 11 4 8. I found no other easier way to display and handle such long number also in view of later creating Riesel/Proth pages with Long number k-values. So I used the unique FactorDB-ID for this but it's not easy to figure out what has to be filled into a Long number entry. Entries for this number resolved. Karbon (talk) 14:24, 10 June 2024 (UTC)

Good to see. All makes sense to me. That confirms the consistency that I've observed with these. Since you are using the first 30 digits of the k in the file name before the 3 periods, I will assume that any GF Divisor k > 30 digits should have the long number logic associated with it. Thanks!

Edit correction: Any GF Divisor with k > 39 digits (not 30 digits) should have the long number logic since the total length of this k including the periods, trailing digits, and length in parenthesis totals to 39 digits. Gary Barnes (talk) 15:19, 10 June 2024 (UTC)

No, k>30 digits is correct, the digitcount could 3- or 4-digit long, I've not yet defined any specification for this, was more a test if it's functioning. The same for the length of the long number: every number<=100 digits the number is given in full representation, otherwise only as "P101" (or "C" or "U" for composite or unknown). Example see GFN_2_1-table for digits>100. All of this was yet not meant to fully functioning and usable but seems woking so far. One issue could happen: If numbers exist like "xxxxxx...xx(yy)" and the not listed digits in the "..." are different but the pagetitle of such Riesel/Proth-values would be the same! Seems extremely unlikely but could happen. Karbon (talk) 19:07, 10 June 2024 (UTC)