Am I doing it wrong?

kracker · 2012-07-01, 21:12

Okay, I was bored and was poking around and I found this on my factors found with TF:
It says I found the factor with P-1, when I actually did it with TF

Code:

kracker Manual testing 31321219 F-PM1 2012-07-01 20:15 0.0 325236569986535729617   1.3727

...The others are fine.

Code:

kracker Manual testing 3125237 NF 2012-07-01 18:390.0 no factor for M31252379 from 2^68 to 2^69 [mfakto 0.11-Win barrett15_75_2]   1.9129

Maybe I'm doing something wrong or this is normal? Thanks

c10ck3r · 2012-07-01, 21:52

31,321,219 is not very close to 3,125,237...is it possible the first WAS actually P-1?

Edit: You might consider upgrading to mfaktc 0.17 or 0.18 as well...

Dubslow · 2012-07-01, 21:53

No, this is a long- and well- known problem with PrimeNet's results parser. It completely ignores what program reported the factor and guesses the work type based solely on the size of the factor: anything beyond the default P95 TF, which is everything that GPU272 does, is presumed to be P-1.

James is working on fixing it.

kracker · 2012-07-01, 22:35

Quote:

Originally Posted by c10ck3r

Edit: You might consider upgrading to mfaktc 0.17 or 0.18 as well...

I run mfakto, not mfaktc

Quote:

Originally Posted by Dubslow

No, this is a long- and well- known problem with PrimeNet's results parser. It completely ignores what program reported the factor and guesses the work type based solely on the size of the factor: anything beyond the default P95 TF, which is everything that GPU272 does, is presumed to be P-1.

James is working on fixing it.

Ah ok, Thanks!

2012-07-01, 21:12	#1
kracker "Mr. Meeseeks" Jan 2012 California, USA 878₁₆ Posts	Am I doing it wrong? Okay, I was bored and was poking around and I found this on my factors found with TF: It says I found the factor with P-1, when I actually did it with TF Code: kracker Manual testing 31321219 F-PM1 2012-07-01 20:15 0.0 325236569986535729617 1.3727 ...The others are fine. Code: kracker Manual testing 3125237 NF 2012-07-01 18:390.0 no factor for M31252379 from 2^68 to 2^69 [mfakto 0.11-Win barrett15_75_2] 1.9129 Maybe I'm doing something wrong or this is normal? Thanks

2012-07-01, 21:52	#2
c10ck3r Aug 2010 Kansas 547 Posts	31,321,219 is not very close to 3,125,237...is it possible the first WAS actually P-1? Edit: You might consider upgrading to mfaktc 0.17 or 0.18 as well... Last fiddled with by c10ck3r on 2012-07-01 at 21:54 Reason: add suggestion

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Is Moore's Law wrong, or is it wrong-headed (6th time around)	jasong	jasong	12	2016-05-27 11:01
what I do wrong	pepi37	Linux	4	2015-07-12 09:13
something wrong with my RAM?	ixfd64	Hardware	13	2010-07-17 20:49
Something is very wrong...	RhymeBomb	Information & Answers	7	2010-02-28 09:53
something wrong here?	ixfd64	Lounge	2	2007-09-17 13:20

2012-07-01, 21:53	#3
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3×29×83 Posts	No, this is a long- and well- known problem with PrimeNet's results parser. It completely ignores what program reported the factor and guesses the work type based solely on the size of the factor: anything beyond the default P95 TF, which is everything that GPU272 does, is presumed to be P-1. James is working on fixing it.