Factoring database - Page 61

10metreh · 2010-01-19, 18:21

Quote:

Originally Posted by smh

I did a quick diff between all open ended sequences from last week and this morning and I get the following

Code:

<snip>

Also 789090, 792820, 789816. It seems that someone has a grudge against us (the aliquot project) - they clearly know about Subproject #3 and the effort on 4788.

Mini-Geek · 2010-01-19, 18:27

Quote:

Originally Posted by 10metreh

Also 789090, 792820, 789816. It seems that someone has a grudge against us (the aliquot project) - they clearly know about Subproject #3 and the effort on 4788.

Weird.

I wasn't aware we had enemies...at least the set prime button has been taken offline for now.

frmky · 2010-01-19, 18:29

And 790308 step 341. And some incorrect work was submitted afterward.

axn · 2010-01-19, 19:18

Well... does anyone remember the Bill Gates incident?

mdettweiler · 2010-01-19, 19:30

Did anyone by chance ask Syd whether he could find out the culprit from logs? If we could get an IP, or better yet a FactorDB username, it might be possible to connect the dots to a mersenneforum member. That way, when the Set Prime feature is eventually turned back on (hopefully in a more blunder- and vandal-proof way), we'll know whose privileges need to be revoked before we do so.

Andi47 · 2010-01-19, 19:38

Quote:

Originally Posted by mdettweiler

Did anyone by chance ask Syd whether he could find out the culprit from logs? If we could get an IP, or better yet a FactorDB username, it might be possible to connect the dots to a mersenneforum member. That way, when the Set Prime feature is eventually turned back on (hopefully in a more blunder- and vandal-proof way), we'll know whose privileges need to be revoked before we do so.

I have asked Syd when I sent him some emails yesterday evening and today in the morning, but he seems to be too busy at the moment, so he seems just to have repaired alq4788. (In my mail I have written too, that there are a couple more vandalized sequences, and that he should also look to this thread - let's hope that he finds some time to do so in the near future.)

frmky · 2010-01-19, 20:19

Rather than fix them all manually, it might be easier to implement a "Retest Primality" button. There is a legion of volunteers here willing to hunt down the bad entries and click the button.

10metreh · 2010-01-19, 20:26

Quote:

Originally Posted by Andi47

I have asked Syd when I sent him some emails yesterday evening and today in the morning, but he seems to be too busy at the moment, so he seems just to have repaired alq4788. (In my mail I have written too, that there are a couple more vandalized sequences, and that he should also look to this thread - let's hope that he finds some time to do so in the near future.)

That was post 666 in this thread - I can only think that the devil has something to do with this

database vandalism.

RichD · 2010-01-21, 01:44

Quote:

Originally Posted by 10metreh

No, they aren't: sequence 13596 has a "p91" that already has factors submitted but is still listed as prime.

That's been stuck at the top of the worker queue for quite some time now.

Like at least a month or two.

Batalov · 2010-01-21, 03:09

It would be nice to run a mysql procedure on all current number objects, and if they are even (except 2, of course), drop the prime flag. If they are stored wordwise, that would be easy to code looking just at the last limb.

Otherwise, it is too painful to check all the vandalized sequences. There's thousands of them.

mdettweiler · 2010-01-21, 03:32

Quote:

Originally Posted by Batalov

It would be nice to run a mysql procedure on all current number objects, and if they are even (except 2, of course), drop the prime flag. If they are stored wordwise, that would be easy to code looking just at the last limb.

Otherwise, it is too painful to check all the vandalized sequences. There's thousands of them.

Of course, if Syd can find out who did this, he could possibly look up all numbers flagged as prime by that user in the database (assuming it actually records that), and drop it for those, thus forcing them to be retested automatically as per the normal process. That way, we could be sure to get all of them, not just the even ones.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Database for k-b-b's:	3.14159	Miscellaneous Math	325	2016-04-09 17:45
Factoring database issues	Mini-Geek	Factoring	5	2009-07-01 11:51
database.zip	HiddenWarrior	Data	1	2004-03-29 03:53
Database layout	Prime95	PrimeNet	1	2003-01-18 00:49
Is there a performance database?	Joe O	Lounge	35	2002-09-06 20:19

2010-01-19, 18:29	#663
frmky Jul 2003 So Cal 11×193 Posts	And 790308 step 341. And some incorrect work was submitted afterward.

2010-01-19, 19:18	#664
axn Jun 2003 3²·5·113 Posts	Well... does anyone remember the Bill Gates incident?

2010-01-19, 19:30	#665
mdettweiler A Sunny Moo Aug 2007 USA (GMT-5) 3·2,083 Posts	Did anyone by chance ask Syd whether he could find out the culprit from logs? If we could get an IP, or better yet a FactorDB username, it might be possible to connect the dots to a mersenneforum member. That way, when the Set Prime feature is eventually turned back on (hopefully in a more blunder- and vandal-proof way), we'll know whose privileges need to be revoked before we do so.

2010-01-19, 20:19	#667
frmky Jul 2003 So Cal 11·193 Posts	Rather than fix them all manually, it might be easier to implement a "Retest Primality" button. There is a legion of volunteers here willing to hunt down the bad entries and click the button.

2010-01-21, 03:09	#670
Batalov "Serge" Mar 2008 Phi(4,2^7658614+1)/2 9,497 Posts	It would be nice to run a mysql procedure on all current number objects, and if they are even (except 2, of course), drop the prime flag. If they are stored wordwise, that would be easy to code looking just at the last limb. Otherwise, it is too painful to check all the vandalized sequences. There's thousands of them.