Factoring database

[Jayder]

So it's a twin prime. Maybe there's a reason, but why should multiples of it be entered into the database?

I haven't noticed any repeat factors lately, but if this problem of ours does persist, is there any way that we can pretest a number before it proceeds with factoring? For example, before starting factoring on a C88, it would check to see if the P35 I mentioned earlier is a factor before proceeding. Might the perl script be adapted in some way?

I'm really just a beginner coder but I will look into it myself if nobody else thinks it's worth it. It sucks spending 10 minutes each on 20 numbers that all could have been factored in less than a second.

[henryzz]

I think they might still be being added. I modified my ecm perl script to check for this factor in batches of 100 composites(that is all the database will give me at once now ). I am finding lots of them. I run the script again and there are more(I have checked I am reporting right and that they are different numbers). I am sequentially going through the list of composites.
I am not finding any for 88999999999999999999999999999999999 they must have all been factored.

If there are any more factors being flooded let me know and I will factor those composites.
If you are using a perl script I can give you the code to check a number before factoring it.

edit: I seem to have stopped finding the new factors. Maybe the person adding them has run into the limits for this hour. I will run the script again in a while.

[firejuggler]

I just spent the last three nights factoring composite below C90, with the help of your script. That may have help the problem.

[kar_bon]

Currently hundreds of numbers with factor 89000000000000000000000000000017217 in it.

[cmd]

Originally Posted by kar_bon

Currently hundreds of numbers with factor 89000000000000000000000000000017217 in it.

|==1

ne><t : 890000000000000000000000000000|||8|
t|/\/;n +2

Kar b°n ;f y°u wr;te t|-|;s ... \/\/e st°p ;t

[firejuggler]

*frustrated*
working on them, hoping the flood will stop soon

[henryzz]

Originally Posted by kar_bon

Currently hundreds of numbers with factor 89000000000000000000000000000017217 in it.

Gone.
Also the twin 89000000000000000000000000000017219.
I am going through it factoring manually some numbers and testing loads for the same factors. I am finding hundreds of factors.

[henryzz]

I can't see any more patterns in the unfactored numbers. I killed most of the c70s.

[chris2be8]

If you-know-who gets a kick out of doing this sort of thing then he *really* needs to get a life.

Of course he really deserves a different sort of kick. Or failing that having his internet connection disconnected for abuse.

Chris

[LaurV]

Originally Posted by Jayder

Is somebody doing this maliciously?

Not necessary, it can be ignorance. But the fact is that from time to time some poor soul (ignorance) or some idiot (malice) does this, and we have to clean behind.

[LaurV]

Originally Posted by Jayder

Is somebody doing this maliciously?

Not necessary, it can be ignorance. But the fact is that from time to time some poor soul (ignorance) or some idiot (malice) does this, and we have to clean behind.

edit limit, sorry, busy here at job: I did not see the last page when I replied... so it is indeed cmd... this guy is not malicious, nor even childish. He - or his brain - is just FUBAR.

I wonder (like in repeated times before) why Syd does not give the passwords to some guy who actually knows and have time to implement that "user authentication" properly... maybe this is all our problem. And then the "beginners" or the "trolls" will be limited to fewer ID per day, but serious users will be able to login and push their sequences. I feel that such measure would make the DB a bit faster and friendlier for "average" users like myself, too.