mersenneforum.org Odd result
 Register FAQ Search Today's Posts Mark Forums Read

 2009-12-04, 02:34 #1 1997rj7     Sep 2003 22×3×29 Posts Odd result I have noticed in the past that when I submit factors that have been found (trial factoring or P-1) through the manual pages, the server always says "Insufficient information for accurate CPU credit." For trial factoring, it seem to do OK assigning credit, but for P-1 it always assumes the factor was found in Stage #1 with B1=800000, even though the result that I send has the true information. Can someone explain this? Today I had an even stranger thing happen, a P-1 factor was credited as a trial factor. Here are the lines from the results.txt file: Code: [Tue Dec 01 13:56:58 2009] P-1 found a factor in stage #2, B1=605000, B2=17393750. UID: 1997rj7/compq, M51200911 has a factor: 390126913731778984073, AID: F16547D743B533B97C9EBCA541EFDDF8 and here is the result that came back from the server: Code: Factors found: 1 Processing result: M51200911 has a factor: 390126913731778984073, AID: F16547D743B533B97C9EBCA541EFDDF8 Insufficient information for accurate CPU credit. For stats purposes, assuming factor was found by trial factoring using prime95. CPU credit is 1.0510 GHz-days. What gives?
2009-12-04, 03:27   #2

"Richard B. Woods"
Aug 2002
Wisconsin USA

22×3×641 Posts

Quote:
 Originally Posted by 1997rj7 I have noticed in the past that when I submit factors that have been found (trial factoring or P-1) through the manual pages, the server always says "Insufficient information for accurate CPU credit." For trial factoring, it seem to do OK assigning credit, but for P-1 it always assumes the factor was found in Stage #1 with B1=800000, even though the result that I send has the true information. Can someone explain this?
It used to be even stranger: I had factors found by P-1 credited as though found via ECM.

Quote:
 Today I had an even stranger thing happen, a P-1 factor was credited as a trial factor. Here are the lines from the results.txt file: Code: [Tue Dec 01 13:56:58 2009] P-1 found a factor in stage #2, B1=605000, B2=17393750. UID: 1997rj7/compq, M51200911 has a factor: 390126913731778984073, AID: F16547D743B533B97C9EBCA541EFDDF8 and here is the result that came back from the server: Code: Factors found: 1 Processing result: M51200911 has a factor: 390126913731778984073, AID: F16547D743B533B97C9EBCA541EFDDF8 Insufficient information for accurate CPU credit. For stats purposes, assuming factor was found by trial factoring using prime95. CPU credit is 1.0510 GHz-days. What gives?
You probably got more credit as an assumed TF result than you would have had as an assumed ECM result. :-)

2009-12-04, 08:48   #3
S485122

Sep 2006
Brussels, Belgium

22·383 Posts

Quote:
 Originally Posted by 1997rj7 I have noticed in the past that when I submit factors that have been found (trial factoring or P-1) through the manual pages, the server always says "Insufficient information for accurate CPU credit." For trial factoring, it seem to do OK assigning credit, but for P-1 it always assumes the factor was found in Stage #1 with B1=800000, even though the result that I send has the true information. Can someone explain this?
Since you have assignment ID's (AID) why don't you just move the .spl file from the computer that does not communicate directly with PrimeNet to a computer that does ? You just have to check that the computer you move the file to has communicated and thus has no .spl file of his own, then after moving the file you initiate the communication with the server or just wait for the next automatic communication. You will not need to use the "Manual Communication" pages and your results will be accepted as they are.

Jacob

 Similar Threads Thread Thread Starter Forum Replies Last Post stebbo PrimeNet 23 2017-06-03 11:14 swellman YAFU 15 2016-02-25 00:38 Unregistered Information & Answers 6 2013-04-16 21:52 yoyo GMP-ECM 1 2009-08-08 07:09 R.D. Silverman NFSNET Discussion 1 2005-04-19 23:45

All times are UTC. The time now is 14:23.

Thu Jul 9 14:23:16 UTC 2020 up 106 days, 11:56, 1 user, load averages: 2.59, 2.02, 1.69