OFFICIAL "SERVER PROBLEMS" THREAD - Page 175

ric · 2020-07-26, 10:05

Appreciate the new rules for extracting factors found after a specified date. However, there's a minor glitch, preventing ancient factors from being extracted.

Case in point: report factor 9012691 has two factors, not just one. And the second one, despite having a 1998-something date from history, might be present in some database with a null one.

FWIW, a similar extraction made around mid-july, when date enforcement rules were not in place, gave this other result:

Code:

9012691,15412578926341510031,2017-04-26
9012691,121781652850531001,

TIA, ric

James Heinrich · 2020-07-26, 15:23

Quote:

Originally Posted by ric

Appreciate the new rules for extracting factors found after a specified date. However, there's a minor glitch, preventing ancient factors from being extracted.

I have fixed that. I also added a little more filtering options with min/max values for exponent/date/length.

ric · 2020-07-26, 15:44

Quote:

Originally Posted by James Heinrich

I have fixed that. I also added a little more filtering options with min/max values for exponent/date/length.

Amazing speed! thanks

tha · 2020-07-26, 20:43

Post #1848:

Quote:

Originally Posted by James Heinrich

I believe the two issue are directly related, but I'll need George's input on how to resolve it. I think it should be a simple fix.

Any update on this?

James Heinrich · 2020-07-26, 20:52

Quote:

Originally Posted by tha

Any update on this?

Can you email/PM me a sample of result lines that fall into this category that I can test with, please?

Prime95 · 2020-07-26, 21:27

Quote:

Originally Posted by James Heinrich

Can you email/PM me a sample of result lines that fall into this category that I can test with, please?

I remember doing a "half fix" for this a month go. I'll resend the emails we exchanged to refresh your memory.

kriesel · 2020-07-27, 14:57

In the first portion, all is well.
In the all-cpus section of https://www.mersenne.org/workload/, CERT assignments show up as follows:

Code:

UNKNOWN WORKTYPE "200"

UNKNOWN WORKTYPE "200"

UNKNOWN WORKTYPE "200"

UNKNOWN WORKTYPE "200"

Cpu-specific sections have the same issue for CERT assignments.

James Heinrich · 2020-07-27, 15:01

I could fix that, but I don't know what a CERT assignment line looks like.
Possibly manual assignments will also need patching?

kruoli · 2020-07-27, 15:20

Quote:

Originally Posted by Prime95

Quote:

Originally Posted by kriesel

Worktodo format for prime95 verification/certificate is:

Cert=aid,k,b,n,c,what?
Cert=(redacted),1,2,97457587,-1,380694

Number of squarings (iterations).

That's what George said in the next big development thread.

James Heinrich · 2020-07-27, 15:43

Quote:

Originally Posted by Prime95

Number of squarings (iterations).

I'm not sure where to pull that magic number from, so I can't fix that (yet). Note-to-self: team workload page will need same patch.

James Heinrich · 2020-07-28, 02:33

Quote:

Originally Posted by kriesel

In the all-cpus section of https://www.mersenne.org/workload/, CERT assignments show up as follows:
UNKNOWN WORKTYPE "200"

Should be fixed now. I don't have any CERT assignments so I can't see for myself, let me know if it doesn't appear as expected.

2020-07-26, 10:05	#1915
ric Jul 2004 Milan, Ita 2×7×13 Posts	New minor glitch in Known Factors page Appreciate the new rules for extracting factors found after a specified date. However, there's a minor glitch, preventing ancient factors from being extracted. Case in point: report factor 9012691 has two factors, not just one. And the second one, despite having a 1998-something date from history, might be present in some database with a null one. FWIW, a similar extraction made around mid-july, when date enforcement rules were not in place, gave this other result: Code: 9012691,15412578926341510031,2017-04-26 9012691,121781652850531001, TIA, ric

2020-07-27, 14:57	#1921
kriesel "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 31·173 Posts	Cert work type known but unknown In the first portion, all is well. In the all-cpus section of https://www.mersenne.org/workload/, CERT assignments show up as follows: Code: UNKNOWN WORKTYPE "200" UNKNOWN WORKTYPE "200" UNKNOWN WORKTYPE "200" UNKNOWN WORKTYPE "200" Cpu-specific sections have the same issue for CERT assignments.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Official "Faits erronés dans de belles-lettres" thread	ewmayer	Lounge	39	2015-05-19 01:08
Official "all-Greek-to-me Fiction Literature and Cinema" Thread	ewmayer	Science & Technology	41	2014-04-16 11:54
Official "Lasciate ogne speranza" whinge-thread	cheesehead	Soap Box	56	2013-06-29 01:42
Official "Ernst is a deceiving bully and George is a meanie" thread	cheesehead	Soap Box	61	2013-06-11 04:30
Official "String copy Statement Considered Harmful" thread	Dubslow	Programming	19	2012-05-31 17:49

2020-07-27, 15:01	#1922
James Heinrich "James Heinrich" May 2004 ex-Northern Ontario 2⁴·3·71 Posts	I could fix that, but I don't know what a CERT assignment line looks like. Possibly manual assignments will also need patching?