Factoring database

[Syd]

Originally Posted by schickel

Hmmmm...I have been only inserting one and with "Insert in background" checked, also.

After repairing both seqeunces, any indication on what borked them?

Still no idea. Both sequences contained numbers with non-existant factors, so joining returned "NULL"-values.

Originally Posted by 10metreh

And it's factored too!

They are busy sieving 6603209657...<128> , the current cofactor of sequence 162126.

[10metreh]

A huge number of ECM jobs have just entered the queue.

[schickel]

Originally Posted by Syd

Still no idea. Both sequences contained numbers with non-existant factors, so joining returned "NULL"-values.

OK, so something as simple as a 1-bit hiccup in transit could do it....

Next question then becomes, if a sequence has such an error, would re-submitting it fix it, or does it have to be repaired from your end?

[schickel]

Originally Posted by 10metreh

The longest sequence at the point of reaching 80 digits?

I hadn't actually seen that, since I dropped it well before having a graph program, but its interesting how it loafs around a loo-oo-ooong time before heading up.

It's among the longest single sequences; I had great hopes when it escaped 2^2 * 7, but, unfortunately, 2^3 * 3 came along and took it quickly up to 135 digts.....

Maybe I should pick it back up, since I have more horsepower now than I did a couple of years ago.

[Syd]

Originally Posted by schickel

OK, so something as simple as a 1-bit hiccup in transit could do it....

Next question then becomes, if a sequence has such an error, would re-submitting it fix it, or does it have to be repaired from your end?

I believe its a race condition, any maybe I just found & fixed it. Maybe

No re-submitting does not fix it, I have to correct this manually.

[Andi_HB]

There is again a factorized Number in Low priority work Queued pos. 2
( the 96 digit Number 397700671781343958658291384907039335537257313440265976141650720653353417420978200108651386552531 )

[Syd]

Originally Posted by Andi_HB

There is again a factorized Number in Low priority work Queued pos. 2
( the 96 digit Number 397700671781343958658291384907039335537257313440265976141650720653353417420978200108651386552531 )

If a factor is submitted manually, the work is not removed from queue. It gets removed once a worker picks it up, maybe worth changing.

[Andi_HB]

Ahh OK - then it`s no Problem - it only looks like something is working wrong.

[schickel]

Originally Posted by Syd

I believe its a race condition, any maybe I just found & fixed it. Maybe

:fingers crossed:

No re-submitting does not fix it, I have to correct this manually.

OK. I'll just double-check any I submit.... And hey, gotta admit, a couple of errors out of how many uploads is really fantastic!

[axn]

Originally Posted by schickel

:fingers crossed:OK. I'll just double-check any I submit....

Probably a good idea to run aliqueit on the elf file before uploading.

[10metreh]

Originally Posted by Andi_HB

There is again a factorized Number in Low priority work Queued pos. 2
( the 96 digit Number 397700671781343958658291384907039335537257313440265976141650720653353417420978200108651386552531 )

That was me. Normally I run the ECM on my aliquot sequence numbers, but if it is near the end of the day, I set Syd's workers to run it so I have results in the morning. In that case, I found a P29 myself with ECM at 25e4 shortly after I put the composite in the workqueue. I split the remaining C67 with QS.