Something that shouldn't happen, I thought I fixed this one. Well...

[QUOTE=Mini-Geek;176579]
By the way, I just noticed that the graphs are now smoothed by a log scale instead of blocky to the digit. Nice update, Syd! :smile:[/QUOTE]

Thanks :smile:

That just happened again on 233760:
[url]http://factorization.ath.cx/search.php?query=&se=1&aq=233760+&action=last&fr=&to=[/url]
(I noticed factors from it were being processed and then saw that it stopped there, I didn't run it, mataje did. I repaired the line that was squared.)

Might be considered too soon to bump, but according to his profile Syd has visited the forum since I posted this and it's still not fixed, so...[quote=Mini-Geek;176772]That just happened again on 233760:
[URL]http://factorization.ath.cx/search.php?query=&se=1&aq=233760+&action=last&fr=&to=[/URL]
(I noticed factors from it were being processed and then saw that it stopped there, I didn't run it, mataje did. I repaired the line that was squared.)[/quote]
:bump:

[QUOTE=Mini-Geek;176967]Might be considered too soon to bump, but according to his profile Syd has visited the forum since I posted this and it's still not fixed, so...
:bump:[/QUOTE]

Please give me some time, I want to use this one to track down the bug.

[quote=Syd;176975]Please give me some time, I want to use this one to track down the bug.[/quote]
Ok, no problem, just wanted to make sure you didn't miss it. :smile:

Feature Request
 

Syd, could you make it so that, the "Show whole sequence (text)" uses <PRE> </PRE> tag instead of the current option of listing lines with <br>.

This would vastly simplify the parsing of that page by software.

[QUOTE=axn;177054]Syd, could you make it so that, the "Show whole sequence (text)" uses <PRE> </PRE> tag instead of the current option of listing lines with <br>.

This would vastly simplify the parsing of that page by software.[/QUOTE]

Now it does. Maybe adding "&raw=1" to the query is also useful for you

[URL="http://factorization.ath.cx/search.php?query=&se=10&aq=49&action=alltext&fr=&to=&raw=1"]raw[/URL]

@Mini-Geek

Fixed your sequence, but could not track the bug down yet

[QUOTE=Syd;177074]Now it does. Maybe adding "&raw=1" to the query is also useful for you

[URL="http://factorization.ath.cx/search.php?query=&se=10&aq=49&action=alltext&fr=&to=&raw=1"]raw[/URL]
[/QUOTE]

Awesome!! That's what I am talkin about!

it seems to me that for a little while the server has been stopping at t30 ecm for 95-99 digit numbers
the minimum limit for t35 is listed on workerstatus as 95 digits

for some reason my workers have duplicated
i restarted the client and it hasn't gone away
the workers that haven't returned work for quite a while under my name can be removed

Syd,

The database is a remarkable piece of work! I just discovered it yesterday and am having a lot of fun with it. :smile:

There are a couple of factorizations that I am "stuck" on that there is no way to have your database automatically queue them up for factoring. They are:

2293*2^317-1
2293*2^325-1

I've done all of the trial factoring on them and then done the low, medium, high, and very high ECM's as well as the P-1 and P+1 for good measure. Both have been factored down to remaining composites that are 91 and 90 digits respectively.

What happens is that the only buttons that are now provided are: "ECM to low limits", "ECM to medium limits", "ECM to high limits", "P-1", and "P+1".

There is no "ECM to very high limits" or "sieve" button so that I can queue them up to find the final factors when workers are available. To manually keep doing the ECM to high limits would be very time consuming and quite ineffeicient for your workers. I tried that a few times and quickly found it to be futile.

This problem seems to occur only for approximately 87-95 digit factors but it doesn't always happen. For factors below that, there always seems to be a "sieve" button available. For factors above that, there seems to always be an "ECM to very high limits" button available; both which allow work to be queued up for processing.

These 2 factorizations are now the only incompleted ones for 2293*2^n-1 up to n=325 in the database so I'd really like to get them completed. :-) This sequence is interesting to me because 2293 is the smallest k-value where k*2^n-1 has no known prime as of yet up to n=4M!

If anyone else can check this and just tell me if I'm not understanding something, that would be great too. Otherwise, it seems like a "bug" or "feature" of the system at the current time.


Thank you,
Gary