mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   FactorDB (https://www.mersenneforum.org/forumdisplay.php?f=94)
-   -   Factoring database (https://www.mersenneforum.org/showthread.php?t=11119)

antiroach 2009-04-28 15:05

Ive come across a weird issue when looking up the aliquot sequence 230160. I get a whole bunch of warnings when viewing the page. When I go to look at the entire sequence in text format the last line shows up as shown:

[code]
577. 1023454652312001611766910550013704020685493130800688375380960244 = Error: NULL
[/code]

Is this a known issue?

CRGreathouse 2009-04-28 17:13

Odd. Even its 'large' semiprime factor
1023454652312001611766910550013704020685493130800688375380960244 = 4164052965990289247 * 2646359592417793011903541521980925671377
errors out for me.

Andi47 2009-04-28 17:34

"queue" for very large ECM jobs
 
Seems the "queue" (is it a queue when new ones are queued into the first position?) for very large ECM jobs needs to be fixed, see [URL="http://www.mersenneforum.org/showpost.php?p=171254&postcount=93"]this post[/URL] and the following posts of that thread.

Two issues:
First, the "run now" button rises the temptation for "fights" (i.e. two or more people keeping clicking "run now" for their own factorizations)

Second, with the queue continuously growing and new composites to be queued to the first position, older composites will literally wait *forever* to be factored. (30 composites in the queue and counting...)

10metreh 2009-04-28 17:38

[quote=Andi47;171357]Seems the "queue" (is it a queue when new ones are queued into the first position?) for very large ECM jobs needs to be fixed, see [URL="http://www.mersenneforum.org/showpost.php?p=171254&postcount=93"]this post[/URL] and the following posts of that thread.

Two issues:
First, the "run now" button rises the temptation for "fights" (i.e. two or more people keeping clicking "run now" for their own factorizations)

Second, with the queue continuously growing and new composites to be queued to the first position, older composites will literally wait *forever* to be factored. (30 composites in the queue and counting...)[/quote]

As I suggested, random shuffling might be an idea, with each new composite entering at a random place, and the queue getting shuffled every few minutes.

jrk 2009-04-28 17:59

[QUOTE=Andi47;171357](is it a queue when new ones are queued into the first position?)[/QUOTE]
No. It's a LIFO.

[QUOTE=10metreh;171358]As I suggested, random shuffling might be an idea, with each new composite entering at a random place.[/QUOTE]
I like that idea.

10metreh 2009-04-28 18:10

[quote=jrk;171364]I like that idea.[/quote]

You'll like it even more with the edit, if you didn't realise what I meant :razz:

CRGreathouse 2009-04-28 18:23

Why keep an order if you're just going to shuffle? Simply select a random job and work on it.

jrk 2009-04-28 20:29

[QUOTE=CRGreathouse;171376]Why keep an order if you're just going to shuffle? Simply select a random job and work on it.[/QUOTE]
You could even do that on a per-worker basis, so that the workers aren't necessarily all working on the same number.

Syd 2009-04-29 09:02

The modulo function (%) is in now, I remember someone suggested this one here. Accessing the last iteration's value is somewhat more complex, queued this one for later adding.

[quote=CRGreathouse;170620]
I noticed the database claiming a lie, though:
[URL]http://factorization.ath.cx/search.php?id=23314886[/URL]
is called a "CF" when it's clearly "FF". I verified that the factors displayed divide the number, that their product is the number, and that they are individually prime (verified with Pari's APRCL and Pocklington-Lehmer*).

How did this come to be, and how can it be 'reset'?
[/quote]

[quote=antiroach;171316]Ive come across a weird issue when looking up the aliquot sequence 230160. I get a whole bunch of warnings when viewing the page. When I go to look at the entire sequence in text format the last line shows up as shown:

[code]
577. 1023454652312001611766910550013704020685493130800688375380960244 = Error: NULL
[/code]Is this a known issue?[/quote]

This two are caused by a race condition I haven't found yet, until then: fixed manually.

[quote=jrk;171409]You could even do that on a per-worker basis, so that the workers aren't necessarily all working on the same number.[/quote]

Shuffle the entire queue would need mayor changes in code - an easy one I can set right now is: Do 50% work from top place, 25% from #2, 12,5% from #3 and so on.

The new aliquot code is still buggy, I need another few days to add it.

kar_bon 2009-04-30 07:11

if nobody do it, so i do!

does anybody noticed the 'new' on Syd's database?

No!?

take a closer look!

... a bit closer...

ahhhh....

there're new factoring functions: under the menu 'Sequences' you can find the possibility to calculate sequences for Home Primes too!

i've inserted the HP49 for base 10!

still good work!

Andi47 2009-04-30 08:23

[QUOTE=kar_bon;171625]

i've inserted the HP49 for base 10!
[/QUOTE]

I just added the p+/-1 efforts which Alex and I did in spring 2008.

For P+1, I mis-counted the number of 0's - Alex did B2=10^17, not 10^14. @Syd, can you please correct that?


All times are UTC. The time now is 21:04.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.