The "Show graph" function doesn't work on seq 4788. It works on other sequences I have tried, though.

[url]http://factorization.ath.cx/aliquot.php?type=1&aq=4788[/url]

JpGraph Error
Cannot use auto scaling since it is impossible to
determine a valid min/max value of the Y-axis (only
null values).

[QUOTE=jrk;191202]The "Show graph" function doesn't work on seq 4788. It works on other sequences I have tried, though.

[url]http://factorization.ath.cx/aliquot.php?type=1&aq=4788[/url]

JpGraph Error
Cannot use auto scaling since it is impossible to
determine a valid min/max value of the Y-axis (only
null values).[/QUOTE]

It works fine for me.

Syd,
Do you have any idea when the worker queue will be re-opened?

Aliquot sequence 282276 has a problem at index 3605 (n=3605).

When you have it show the sequence, all that it shows is:

"Fixed index 72097231"

I have entered factors up past index 4000 on this sequence but I was able to isolate this specific index as having the problem. You can also see the same erroneous message by doing a routine search (factoring) of the value:

448148950156422828696966904235351532484348

This is the value of aliquot sequence 282276 index 3605.

I've tried multiple attempts to repair the sequence with no luck. The sequence merges with no others so there are no others to choose from.

I'm not sure if Syd checks this thread so if anyone can send me a PM with his Email address, that would be helpful. Or would sending a PM work? This is definitely different than the standard old squared-lined problem that can be easily repaired.


Thank you,
Gary

[quote=gd_barnes;191773]snip

I'm not sure if Syd checks this thread so if anyone can send me a PM with his Email address, that would be helpful. Or would sending a PM work? This is definitely different than the standard old squared-lined problem that can be easily repaired.


Thank you,
Gary[/quote]


Hi,

at his DB click on the link 'Search' -> 'Imprint' :wink:

regards,

Matthias

Has the database been intermittently going really slow for anyone else today?

[quote=MatWur-S530113;191781]Hi,

at his DB click on the link 'Search' -> 'Imprint' :wink:

regards,

Matthias[/quote]

Ah, OK. Thank you.

[quote=Mini-Geek;191785]Has the database been intermittently going really slow for anyone else today?[/quote]
It's been going very slowly (though intermittently quite quickly) for me today, especially when I refresh a home prime sequence page to see newly-added lines. I'm not sure if this is happening for any other type of sequences, or just home primes.

It's been very slow for a few days.

Submitting a file (or via aliqueit -s) advances any sequence by just several indices, even though the DB says that it knows all factors!
Stuck sequences are [URL="http://factordb.com/search.php?se=1&aq=702828"]702828[/URL] (I have it until i3447), [URL="http://factordb.com/search.php?se=1&aq=701460"]701460[/URL] (...i3596), and others. Tried submission via the text form, via file ... all the same. Tried repairing - "same difference".

[quote=Batalov;192302]It's been very slow for a few days.

Submitting a file (or via aliqueit -s) advances any sequence by just several indices, even though the DB says that it knows all factors!
Stuck sequences are [URL="http://factordb.com/search.php?se=1&aq=702828"]702828[/URL] (I have it until i3447), [URL="http://factordb.com/search.php?se=1&aq=701460"]701460[/URL] (...i3596), and others. Tried submission via the text form, via file ... all the same. Tried repairing - "same difference".[/quote]
i am guessing that that is the flurry of home prime activity slowing things down

Workers
 

The factoring data base (factordb) appears to be performing quite well. Is there any indication when workers (ECM and/or Msieve) may be allowed to come on-line again? With nearly 80 Million entries is it approaching another threshold?