mersenneforum.org  

Go Back   mersenneforum.org > Factoring Projects > Operazione Doppi Mersennes

Reply
 
Thread Tools
Old 2012-09-13, 18:31   #1
ET_
Banned
 
ET_'s Avatar
 
"Luigi"
Aug 2002
Team Italia

10010101001002 Posts
Default Results

Please, insert here your results.txt files, so that we'll have a unique place to look to when in doubt.

Luigi
ET_ is offline   Reply With Quote
Old 2012-09-13, 19:17   #2
rcv
 
Dec 2011

100011112 Posts
Default

Posting here for historic purposes. George's program was not yet ready for the public, but the kernel for MM127 was working fine. George invited me to work on this range. The early kernel kept the GPU so busy, that when run on my primary video card, the video lag / system responsiveness was measured in minutes. I ran this on a secondary card to which no video was connected. Started on about August 22, 2012. Finished on September 10, 2012. (With a software upgrade in the interim.) The work used a dedicated EVGA NVIDIA GTX 570.

The actual results.txt line reported is:

Code:
no factor for M131071 from 2^68 to 2^69 [mfaktc 0.20 barrett92_mul32_gs]
In English, the above translates to

Code:
no factor for MM127 from 2^178 to 2^179 [mfaktc 0.20 barrett92_mul32_gs]
While the results line may appear bogus, George didn't yet have the complete input/output interface. "M131071" was code for "MM127". The bit-ranges were adjusted by 110. [That's why the above "translation" is provided.]

Last fiddled with by rcv on 2012-09-13 at 19:27 Reason: Emphasizing the test was per George's instructions
rcv is offline   Reply With Quote
Old 2012-09-13, 19:21   #3
science_man_88
 
science_man_88's Avatar
 
"Forget I exist"
Jul 2009
Dumbassville

8,369 Posts
Default

Quote:
Originally Posted by rcv View Post
Posting here for historic purposes. George's program was not yet ready for the public, but the kernel for MM127 was working fine. George invited me to work on this range. The early kernel kept the GPU so busy, that when run on my primary video card, the video lag / system responsiveness was measured in minutes. I ran this on a secondary card to which no video was connected. Started on about August 22, 2012. Finished on September 10, 2012. (With a software upgrade in the interim.) The work used a dedicated EVGA NVIDIA GTX 570.

The actual results.txt line reported is:

Code:
no factor for M131071 from 2^68 to 2^69 [mfaktc 0.20 barrett92_mul32_gs]
In English, the above translates to

Code:
no factor for MM127 from 2^178 to 2^179 [mfaktc 0.20 barrett92_mul32_gs]
Code:
(16:20)>(2^127-1)
%13 = 170141183460469231731687303715884105727
you tested MM17 or it appears so.

Last fiddled with by science_man_88 on 2012-09-13 at 19:22
science_man_88 is offline   Reply With Quote
Old 2012-09-13, 19:30   #4
rcv
 
Dec 2011

14310 Posts
Default

Quote:
Originally Posted by science_man_88 View Post
you tested MM17
Feel free to retest the range. The software is faster now. It should take 16.7 days on a factory-clocked EVGA GTX 570.

Last fiddled with by rcv on 2012-09-13 at 19:37
rcv is offline   Reply With Quote
Old 2012-09-13, 19:33   #5
science_man_88
 
science_man_88's Avatar
 
"Forget I exist"
Jul 2009
Dumbassville

836910 Posts
Default

Quote:
Originally Posted by rcv View Post
Feel free to retest the range. The software is faster now. It should take 16.7 days on a factory-clocked EVGA GTX 570.
I don't have a GPU, I was just saying I don't see how M131071=MM17 to one bit range is MM127 to another bit range. okay never mind I see the edit.

Last fiddled with by science_man_88 on 2012-09-13 at 19:36
science_man_88 is offline   Reply With Quote
Old 2012-09-13, 19:39   #6
ET_
Banned
 
ET_'s Avatar
 
"Luigi"
Aug 2002
Team Italia

22·1,193 Posts
Default

Quote:
Originally Posted by rcv View Post
Posting here for historic purposes. George's program was not yet ready for the public, but the kernel for MM127 was working fine. George invited me to work on this range. The early kernel kept the GPU so busy, that when run on my primary video card, the video lag / system responsiveness was measured in minutes. I ran this on a secondary card to which no video was connected. Started on about August 22, 2012. Finished on September 10, 2012. (With a software upgrade in the interim.) The work used a dedicated EVGA NVIDIA GTX 570.

The actual results.txt line reported is:

Code:
no factor for M131071 from 2^68 to 2^69 [mfaktc 0.20 barrett92_mul32_gs]
In English, the above translates to

Code:
no factor for MM127 from 2^178 to 2^179 [mfaktc 0.20 barrett92_mul32_gs]
While the results line may appear bogus, George didn't yet have the complete input/output interface. "M131071" was code for "MM127". The bit-ranges were adjusted by 110. [That's why the above "translation" is provided.]
So it seems that the early pre-alpha version run on barrett_92 kernel, after a fast hacking on the 95bit limit of the factor. Or maybe the name of the kernel was the same while its content was changed...
ET_ is offline   Reply With Quote
Old 2012-09-13, 20:08   #7
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

2·3·1,193 Posts
Default

Quote:
Originally Posted by ET_ View Post
So it seems that the early pre-alpha version run on barrett_92 kernel, after a fast hacking on the 95bit limit of the factor. Or maybe the name of the kernel was the same while its content was changed...
The early, pre-pre-alpha was a complete hack. 131071 in worktodo did mean test MM127 but add 110 to the bit levels. Output of the proper kernel range was not coded. Output of the adjusted bit levels was not coded.
Prime95 is online now   Reply With Quote
Old 2012-09-14, 05:18   #8
frmky
 
frmky's Avatar
 
Jul 2003
So Cal

40048 Posts
Default

Code:
no factor for k*2^44+1 from 2^92 to 2^93 (k range: 400T to 700T) [mmff 0.21 mfaktc_barrett96_F32_63gs]
no factor for k*2^44+1 from 2^93 to 2^94 (k range: 0Q to 1Q) [mmff 0.21 mfaktc_barrett96_F32_63gs]
frmky is offline   Reply With Quote
Old 2012-09-14, 13:48   #9
flashjh
 
flashjh's Avatar
 
"Jerry"
Nov 2011
Vancouver, WA

100011000112 Posts
Default

Don't know if you want this here, but here it is:

for assignment MMFactor=127,179,2.5e15
Code:
 
no factor for MM127 from 2^179 to 2^180 (k range: 0 to 2500000000000000) [mmff 0.20mmff mfaktc_barrett183_M127gs]
flashjh is offline   Reply With Quote
Old 2012-09-14, 18:39   #10
frmky
 
frmky's Avatar
 
Jul 2003
So Cal

22·33·19 Posts
Default

Code:
no factor for k*2^28+1 from 2^76 to 2^77 (k range: 550T to 1000T) [mmff 0.21 mfaktc_barrett89_F0_31gs]
no factor for k*2^28+1 from 2^77 to 2^78 (k range: 550T to 1000T) [mmff 0.21 mfaktc_barrett89_F0_31gs]
frmky is offline   Reply With Quote
Old 2012-09-15, 16:37   #11
Karl M Johnson
 
Karl M Johnson's Avatar
 
Mar 2010

1100110112 Posts
Default

Code:
no factor for MM89 from 2^138 to 2^139 (k range: 500T to 600T) [mmff 0.21 mfaktc_barrett140_M89gs]
no factor for MM89 from 2^139 to 2^140 (k range: 0T to 600T) [mmff 0.21 mfaktc_barrett140_M89gs]
Karl M Johnson is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
gfn results ET_ FermatSearch 8 2019-06-02 12:09
Where have all the TF results gone?... lycorn PrimeNet 22 2017-10-02 02:40
PGS Results danaj Prime Gap Searches 0 2017-08-14 18:35
CPU Results last 24 hrs Unregistered Information & Answers 3 2010-07-26 00:49
0x results... Mike PrimeNet 11 2004-05-23 12:55

All times are UTC. The time now is 04:50.

Sun Nov 29 04:50:32 UTC 2020 up 80 days, 2:01, 3 users, load averages: 1.73, 1.57, 1.44

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.