Sequence 713160 finally got out of the guide 2^3*5 only to pick up the 2^2*7 driver at 111 digits. I have retired it from my collection of sequences to follow.

[quote=10metreh;200924]...
This mystery worker is getting a bit annoying. They obviously know someone else is working on this range because others are updating the DB. If by any chance you're reading this thread, please could you reply? I won't be cross with you or anything.[/quote]

I hope I didn't give the impression that the line above was from someone else working on my number. I have not noticed any alternate work on any of the numbers I've reserved. I had just noticed line 866 from my elf file at one of my updates.

Speaking of updates, they certainly aren't happening as promptly as a couple weeks ago, but they do seem to eventually show up. Is the db being worked really hard or possibly having to be manually tended?

I am going to keep 748356 at 113 digits, 2^3*3^4*5 for a little while longer, but it is done for this project

releasing 760542 size 102, i1431, 2[sup]2[/sup] * 3 * 7 * 6659 * c96

reserving 761112

index 1 of 761112 is "odd" in the db. It shows:

[code]
1. 5^8*4+8 = 2^2 * 3^2 * 43403
[/code]It should read:

[code]
1. 1562508 = 2^2 * 3^2 * 43403
[/code]I tried "Repair sequence..." with no change.

Although the value is the same, Aliqueit errors out.

Should this be changed?

[QUOTE=EdH;201020]index 1 of 761112 is "odd" in the db.

Should this be changed?[/QUOTE]

Just change it to 1562508. This is common.

[quote=EdH;200989]I hope I didn't give the impression that the line above was from someone else working on my number. I have not noticed any alternate work on any of the numbers I've reserved. I had just noticed line 866 from my elf file at one of my updates.

Speaking of updates, they certainly aren't happening as promptly as a couple weeks ago, but they do seem to eventually show up. Is the db being worked really hard or possibly having to be manually tended?[/quote]

No, I was replying to richs. I should have made it clearer.

[QUOTE=EdH;201020]index 1 of 761112 is "odd" in the db. It shows:

[code]
1. 5^8*4+8 = 2^2 * 3^2 * 43403
[/code][/QUOTE]It's a feature, not a bug....[QUOTE]It should read:

[code]
1. 1562508 = 2^2 * 3^2 * 43403
[/code][/QUOTE]If a number has a "short" form, that is displayed, instead of the decimal expansion.[QUOTE]I tried "Repair sequence..." with no change.

Although the value is the same, Aliqueit errors out.

Should this be changed?[/QUOTE]Only in your local copy of the file....

Reserving 760956, 760968

Edit: 760956 was recently (according to internal index of the factordb) already computed up to 108 digits (c106). releasing.

done with 760218
reserving 760584

reserving 761202

Done with 748500, 108 digits, 2^4*31

760584 merges with 572282!!!!
which merges with 209400 and 98180. not terminated, actually at 101 digits. it has [tex]2*3^2*5^2*7[/tex] - is that a driver?
also is the 98010 range being worked on by anybody? if not and if it's not a driver i think i'll keep it.

reserving 760620

[QUOTE=Buzzo;201114]760584 merges with 572282!!!!
which merges with 209400 and 98180. not terminated, actually at 101 digits. it has [tex]2*3^2*5^2*7[/tex] - is that a driver?
also is the 98010 range being worked on by anybody? if not and if it's not a driver i think i'll keep it.

reserving 760620[/QUOTE]

It's the 2 * 3 driver. The 50k-100k range is maintained by Clifford Stern; I suggest you email him at ax810 at lafn dot org.

Done 760968
Reserving 763926

[QUOTE=10metreh;201131]It's the 2 * 3 driver. The 50k-100k range is maintained by Clifford Stern; I suggest you email him at ax810 at lafn dot org.[/QUOTE]
thanks, i'll release it then.

Done with 760116 sz 101; [COLOR="Red"]2^2[/COLOR] * 3^2 * [COLOR="Red"]7[/COLOR] * 17 * c97

Done with 748422, 108 digits, 2^4*31

FYI, 770k-780k range is ~90% done.

[QUOTE=unconnected;201177]FYI, 770k-780k range is ~90% done.[/QUOTE]

Have you got the dates when you started 770k-775k, finished it, and started 775-780k? I need them for the milestones list.

[quote=10metreh;201181]Have you got the dates when you started 770k-775k, finished it, and started 775-780k? I need them for the milestones list.[/quote]

Approximately 25th Dec I started some sequences from 775k-780k, then I liked that and I decided to take the whole 10k range. Work with 770k-775k started 1st Jan.
I'll post detailed results when all sequences finishes.
775k-780k done except 2 or 3 seqs, and in 770k-775k I've ten or so sequences.

Finished with 748752, 102 digits, 2^4*31

reserving
763168, 763320, 763480, 763512, 763668

[URL="http://factordb.com/aliquot.php?type=1&aq=753732"]753732[/URL] - top of the list again.:sad:

Sorry, but this one is proving tough for me. It's scared of the hundred mark!

It's currently headed back down. I just moved it to one of my machines that is now on 24/7. Let's see what it does with it...

765000 is alraedy at 105 digits and complete for this subproject...

Nevertheless it looks neat and i would like to reserve it to see what happens with the 2^5 * 3 * 5 in near future.

@EdH:
Don't worry. Sometimes you get a strong increasing driver and proceed from 80 to 100 within a few hours; sometomes it is growing very slowly and takes long time on many large composites near 100.
In this case you can be happy that you got the downdriver, that is good news.

[quote=biwema;201255]@EdH:
Don't worry. Sometimes you get a strong increasing driver and proceed from 80 to 100 within a few hours; sometomes it is growing very slowly and takes long time on many large composites near 100.
In this case you can be happy that you got the downdriver, that is good news.[/quote]

Well, it had quite a run from that downdriver before heading back up, too. It made it all the way to 44 digits this time, before putting on its now steep climb.

[URL="http://factordb.com/search.php?se=1&aq=753732&action=range&fr=2250&to=2280"]753732[/URL] is finally done for this project! After reaching 98 digits, it did a steep dive all the way down to 8 digits. Then at i2267, it merged with 506016 (i58) and is now sitting at 100 digits, i3271, 2[sup]2[/sup] * 7 * 11 * 17 * 199 * c94

There were three other merges listed:

Merge at n=2524 with 236472, n=486
Merge at n=2528 with 186496, n=2
Merge at n=2529 with 60676, n=4

How many places should I note this merge? I imagine it should be posted in the terminations thread; any others?

Take Care,
Ed

reserving 760770

[quote=EdH;201409]How many places should I note this merge? I imagine it should be posted in the terminations thread; any others?[/quote]
I'm not too picky. Just here would do. :smile: (just here for subproject work, or just in the terminations thread for 'main project' work.

[quote=Mini-Geek;201412]I'm not too picky. Just here would do. :smile: (just here for subproject work, or just in the terminations thread for 'main project' work.[/quote]
oops! I put a post in the terminations thread, as well, as you probably saw. I'll try to be more reserved if there's a next time...

Taking 765018.

done with 760620
reserving 760800

releasing 761112, size 101, i671, 2 * 3 * 5[sup]2[/sup] * 271 * c96

Done with 763168, 105 digits, 2^2*7
Done with 763320, 100 digits, 2*3*7

Taking 768360, 765528, 769224, 769368.

Reserving 767000

Done with 760182 sz 101; 2^2 * 3 * 7 * p2 * c98

reserving 761040

done with 760800
reserving 761478

Done 763926 Size 107, c99 2* 3^2

Unreserving 765000 Unreserving Size 118, C112 2^3 * 3^2

Reserving 761748

I'll take 769068, 769560, 769656, 769992.

Edit: 769560 is done.

769068 is done.
I'll take 761592, 761628.

I'm on 769992 up to 814 c88 currently. I'll take 768888 instead i guess.

[QUOTE=Joshua2;201585]I'm on 769992 up to 814 c88 currently. I'll take 768888 instead i guess.[/QUOTE]
You actually had it at 99 digits already. A few more steps took it to 100.
769992 is done.

761592 is done.
I'll take 766290, 766688, 766776, 766848, 766880.

760344 is done with sz 100; 2^3 * 3 * 11 * c98

I felt like this was on Mr. Toad's Wild Ride, see the [URL="http://factordb.com/aliquot.php?type=1&aq=760344&big=1"]graph[/URL]

Reserving 765336.

Done with 765336.

761628, 766290, 769656 are done.

76888 is at c95 * c8
taking 768600, 768696

Done 767000 Size101, c99, 2^3 * 3 * 5

whats it mean when u get a lot of WARNING: couldn't find factor in factor.log?

both previous complete taking 768270, 768510

Done with 763480, 108 digits, 2^4*3*31
Done with 763512, 102 digits, 2^3*3

releasing 761202, size 100, i1044, 2 * 3[sup]3[/sup] * 13[sup]2[/sup] * c96

766688, 766776, 766848 is done.
I'll reserve 765380, 765384, 765456, 765504, 765600.

765018: i2300->i2461, size 117, 2^2*7
769224: i1474->i1695, size 100, 2*3
768360: i1577->i1727, size 107, 2^8 <- i'll keep it for more

[QUOTE=Joshua2;201681]whats it mean when u get a lot of WARNING: couldn't find factor in factor.log?[/QUOTE]I'm going to assume here that it happened while the composite was small? If so, there are some numbers in the 20-25 digit range that msieve has problems with. Do you also have yafu installed? If so, aliqueit will switch over to yafu, which can usually factor the composite when msieve can't.

And welcome back!

[QUOTE=Joshua2;201681]whats it mean when u get a lot of WARNING: couldn't find factor in factor.log?[/QUOTE]

That means that yafu has failed to factor a number. This generally happens with small composites like c25 which were split off by P-1. When this happens, aliqueit calls msieve instead. If msieve fails too, you will get WARNING: couldn't find factor in msieve.log and aliqueit will run into an endless loop. In this case, find the composite in aliqueit.log and split it separately with ECM. Then restart aliqueit with the extra switch -f <one_of_the_factors>.

Also, you don't need to post your .elf files. Just submit them to [url]factordb.com[/url] by running aliqueit <the_sequence> -s 0.

766880, 765380, 765456 are done.

I'm going to try a truly automated run overnight, so I'll take all of
765624, 765732, 765864,
767296, 767520, 767550, 767640, 767802,
768042

I made a download that includes the elf or alq files for all open aliquot sequences. The elf files had a program run over it that removes the 'shorthand' values (ones with +,*,^,#,!, etc on the left side of the equation). Also the final partial line is gone as this causes issues in windows.

You can find it posted below under 'All the open aliquot sequences'. It is current as of Jan 11, 2009. It also includes at least part of the two 'broken' sequences in the database - 417336 and 749320 from a previous download.

Note that it is post #14 that has the up to date ones.

[QUOTE=Greebley;201771]Also the final partial line is gone as this causes issues in windows.[/QUOTE]

I thought that bug had been fixed - I only get a "WARNING: @index ***: partial last line. Resuming..." message and then things proceed as normal.

taking 780066, 780330, 780576, 780930

[QUOTE=unconnected;201782]taking 780066, 780330, 780576, 780930[/QUOTE]

BTW, how is 770k-780k getting on?

[quote=10metreh;201781]I thought that bug had been fixed - I only get a "WARNING: @index ***: partial last line. Resuming..." message and then things proceed as normal.[/quote]

For windows, it doesn't correctly put in a new line so you get two indices on the same line. So it does continue, but you have to go back and add the newline in or the db is missing one index. I am pretty sure this wasn't ever fixed.

It is my understanding that everything works for unix.

765384, 765504, 765600, 765624, 765732, 767296 are done.

[quote=10metreh;201785]BTW, how is 770k-780k getting on?[/quote]
It is ready but I need time to upload data into DB and make detailed report.

[QUOTE=unconnected;201808]It is ready but I need time to upload data into DB and make detailed report.[/QUOTE]

For the milestones, have you got the dates when each 5k half (770k-775k and 775k-780k) finished?

[quote=Greebley;201789]For windows, it doesn't correctly put in a new line so you get two indices on the same line. So it does continue, but you have to go back and add the newline in or the db is missing one index. I am pretty sure this wasn't ever fixed.[/quote]

This doesn't happen to me, and I'm on Windows.

done with 761478
reserving 768072

[quote=10metreh;201809]For the milestones, have you got the dates when each 5k half (770k-775k and 775k-780k) finished?
[/quote]

770k-775k - Jan 12
775k-780k - Jan 9

[QUOTE=10metreh;201719]
Also, you don't need to post your .elf files. Just submit them to [url]factordb.com[/url] by running aliqueit <the_sequence> -s 0.[/QUOTE]
i dont have wget on my windows 7.

[quote=Joshua2;201825]i dont have wget on my windows 7.[/quote]
This is normal, since it's a GNU app normally. You can download a version of it for Windows. The [URL="http://downloads.sourceforge.net/gnuwin32/wget-1.11.4-1-setup.exe"]setup link[/URL] from [url]http://gnuwin32.sourceforge.net/packages/wget.htm[/url] should be all you need.

OK, looking for some "sage" advice.

I ran 761040 for 14 hours today without any advancement. Most of the day it seemed to say "c92: running ### ECM curves..." I won't be able to run it for a full day tomorrow, if at all. I have my 24/7 machine working on the 4788 team sieve. Next time I start aliqueit, I don't want to just rerun today. Should I start aliqueit with the -e option next time to skip that portion, or should I run ggnfs on the composite and skip letting aliqueit run the steps?

765864, 767520, 767640, 767802, 767550 are done.
I'll take 780042, 780312, 780324, 780390, 780414, 780504, 780654, 780870, 780888, 780906, 780912.

[QUOTE=EdH;201857]OK, looking for some "sage" advice.

I ran 761040 for 14 hours today without any advancement. Most of the day it seemed to say "c92: running ### ECM curves..." I won't be able to run it for a full day tomorrow, if at all. I have my 24/7 machine working on the 4788 team sieve. Next time I start aliqueit, I don't want to just rerun today. Should I start aliqueit with the -e option next time to skip that portion, or should I run ggnfs on the composite and skip letting aliqueit run the steps?[/QUOTE]

Yep, I'm in the same boat. I have a 0.8 GHz G4 Mac and would recommend running the -e option to cut my loses, but I don't have ggnfs (just yet). Only running msieve on the big boys.

I'll take 781254 781302 781950 782472 782838 782880 783804 783960 783996

[quote=EdH;201857]OK, looking for some "sage" advice.

I ran 761040 for 14 hours today without any advancement. Most of the day it seemed to say "c92: running ### ECM curves..." I won't be able to run it for a full day tomorrow, if at all. I have my 24/7 machine working on the 4788 team sieve. Next time I start aliqueit, I don't want to just rerun today. Should I start aliqueit with the -e option next time to skip that portion, or should I run ggnfs on the composite and skip letting aliqueit run the steps?[/quote]
Definitely go with -e. I've noticed that aliqueit's formula for estimating GNFS time (which it uses for calculating ECM amounts) somewhat heavily overestimates on numbers smaller than C95 or so, thus leading to too much ECM. Last time a new version of aliqueit was released, the crossover to QS was around C95--and for numbers below that, aliqueit's QS estimation formula is much more accurate, whether you're actually going to do QS or GNFS with 11e. However, unfortunately there's no easy way that I know of to tell it to use the QS formula for C<95 while leaving the GNFS cuttoff at 85. Anyway, the upshot of this is that if it was running for more than 20-30 minutes or so doing ECM for a C92, it's probably plenty.

done with 768072

reserving 784128

768042, 780042, 780312, 780414, 780504, 780654, 780870, 768042, 780888, 780906, 780912 are done.
I'll take 781056, 781344, 781470, 781512, 781560, 782136, 782394, 782628, 782940, 782982.

Done with 761748 sz 108; 2^3 * 3 * 5 * p14 * c93

Reserving 783552 & 783750.

780324, 781470, 782394, 782628, 782940 are done.

Reserving 784896

I got all my previous ones done and submitted with wget. I had to add that folder to the path, but I'm not sure how to do it permanetly.
taking 784782, 784842, 784950
is there a way to use wget to download the past work done?

[QUOTE=Joshua2;201968]
is there a way to use wget to download the past work done?[/QUOTE]
[CODE]
#!/bin/sh

wget -O alq_${1}.elf "http://www.factordb.com/search.php?se=1&aq=${1}&action=all&fr=&to=&raw=1&text=Text"
[/CODE]
If you don't want to use it as a bash script, replace ${1} with the sequence you want to retrieve. If a step has an algebraic formula instead of a number that will need to manually corrected, but that's fortunately rare.

780390, 781056, 781512, 781560, 782136, 782982 are done.
I'll take 783024, 783264, 783390, 783930, 783948,784056, 784350, 784368, 784488, 784494, 785010.

cool, but bash scripts don't work in windows do they? can you make a batch file script or something? why not add it straight to aliq program

[QUOTE=Joshua2;201978]cool, but bash scripts don't work in windows do they? can you make a batch file script or something? why not add it straight to aliq program[/QUOTE]

Bash is available for Windows. For example, [URL="http://win-bash.sourceforge.net/"]http://win-bash.sourceforge.net/[/URL]

Here's how I get them:

[code]wget "http://factorization.ath.cx/search.php?se=1&aq=276&action=all&text=Text"
grep -F " = " "search.php@se=1&aq=276&action=all&text=Text" > alq_276.elf
grep -i "ended" "search.php@se=1&aq=276&action=all&text=Text" > alq_276.mp
grep -i "Merge" "search.php@se=1&aq=276&action=all&text=Text" >> alq_276.mp
del "search.php@se=1&aq=276&action=all&text=Text"
sleep 3[/code]It finds all the lines with equal on them with grep so it removes some extra stuff and just gives you the series. Does the raw=1 in the example above do that automatically?

In the above case I use the *.mp file to determine whether the sequence is open ended a merge or prime - it stores the 'result' line near the top in text mode. This has html in it.

[quote=Greebley;202002]It finds all the lines with equal on them with grep so it removes some extra stuff and just gives you the series. Does the raw=1 in the example above do that automatically?[/quote]
Yep, basically. See for yourself: [url]http://factorization.ath.cx/search.php?se=1&aq=276&action=all&text=Text&raw=1[/url] What the DB returns with raw=1 and text=1 is almost exactly like the .elf format. The only things that can cause problems are that sometimes the left side will be represented as a formula instead of a simple number (e.g. on 276 index 13, it prints "3^9+1" instead of "19684"), which makes aliqueit unable to read it, (and makes it error out) and that the partial last line can cause some bad behavior in aliqueit.

reserving 789966

760770 done: size 100, i1107, 2[sup]2[/sup] * 7 * 37 * 173 * 191 * c92

reserving 785556

781344, 783024, 783264, 783390, 783930, 783948, 784056, 784350, 784368, 784488, 784494, 785010 done.
I'll take 785112, 785142, 785232, 785248, 785428, 785622, 785694, 785946, 785970, 786024, 786072, 786210.

Greg, you should tweak on your "terminating-ness" prediction software. :rolleyes:
At the rates you are testing, you should get one, anyway, any day now. (I guess one out of ~50 of these should terminate.)

I'll take 786688 786720 787024 787158 787284 788304 788448 788868 789594

finished and submitted all but 784950
taking 786330

[QUOTE=Batalov;202057]Greg, you should tweak on your "terminating-ness" prediction software. :rolleyes:
At the rates you are testing, you should get one, anyway, any day now. (I guess one out of ~50 of these should terminate.)
[/QUOTE]
680094 (which I did illicitly) was a wild ride, closest I've come so far, but no dice.

[QUOTE=frmky;202080]680094 (which I did illicitly) was a wild ride, closest I've come so far, but no dice.[/QUOTE]Don't worry....I started running sequences in November '06 and didn't get a downdriver run until March '07. After coming [I]very[/I] close with [URL="http://factordb.com/aliquot.php?type=1&aq=48462&big=1"]48462[/URL] (9 digits twice and no merge!). It wasn't until June '09 that I caught a [URL="http://factordb.com/aliquot.php?type=1&aq=163716&big=1"]termination[/URL]. (Of course, I've been doing sequences from >100 digits all along, so there haven't been many chances.....maybe I should do some of these sequences [right after I factor a c124, a c128, and a c139])