![]() |
Some terminations/merges are missing in 1st post.
[code] 757110 unconnected 21 Dec 2009 91 2605 Prime 767430 Batalov 13 Dec 2009 89 1907 Prime 748496 Batalov 10 Dec 2009 80 3075 Prime 737490 unconnected 10 Dec 2009 85 2926 Prime 799788 kar_bon 12 Nov 2009 86 1974 Prime 739368 Batalov 31 Oct 2009 84 1849 Merge with 39852 [/code] |
740106 reached 101 digits now.
I report it now that the milestone is not delayed. It lost the 2^2*7 driver at 99 digits, so i will keep it a while to see what happens. |
757416 at 100 digits, 2*3
757560 at 100 digits, 2^4*31*3 Taking 757728, 758010 |
[QUOTE=unconnected;200615]Some terminations/merges are missing in 1st post.
[code] 757110 unconnected 21 Dec 2009 91 2605 Prime 767430 Batalov 13 Dec 2009 89 1907 Prime 748496 Batalov 10 Dec 2009 80 3075 Prime 737490 unconnected 10 Dec 2009 85 2926 Prime 799788 kar_bon 12 Nov 2009 86 1974 Prime 739368 Batalov 31 Oct 2009 84 1849 Merge with 39852 [/code][/QUOTE] We already have a terminations thread, so I've deleted the superfluous list that was in this thread. If you think I should put it back, say so. |
757722 done (2^2*3*7)
Taking 758022 |
[quote=10metreh;200655]We already have a terminations thread, so I've deleted the superfluous list that was in this thread. If you think I should put it back, say so.[/quote]
Ok, it is good to put all terminations in one thread. :smile: 748488 and 749754 are done 748488: i291->i1927, size 100, 2^2*7 749754: i493->i2683, size 101, 2*3*5 |
757728 done (2^3*3*5)
758022 done (2^3*3) 758562 done (2*3^2) Taking 764592, 764622, 764844 |
Last take for the weekend
760590 762030 762840 763176 764346 These are already done: 758646 (Tom), 761516, 761880, 763728; take them off the list, pls. |
764622 done, 2^3*3*5. Taking 764544.
750672 at 110 digits, 2*3*5; taking 764292 |
Oh, No! I'm at the top of the list!:sorry:
Actually, 747768 is over 100 digits, but I haven't been able to update the db, so I'm just letting it work some more... As to 753732, I don't know what's going on. My machine keeps jumping out of ggnfs for varying reasons and even though it ecmed all day while I was out, it didn't come up with any factors for a c93 portion of the current iteration. I plan to run it (somewhat) supervised tomorrow, maybe even on two (or 3) machines to see if I can get anything. Take Care, Ed |
[quote=EdH;200727]Oh, No! I'm at the top of the list!:sorry:
Actually, 747768 is over 100 digits, but I haven't been able to update the db, so I'm just letting it work some more... As to 753732, I don't know what's going on. My machine keeps jumping out of ggnfs for varying reasons and even though it ecmed all day while I was out, it didn't come up with any factors for a c93 portion of the current iteration. I plan to run it (somewhat) supervised tomorrow, maybe even on two (or 3) machines to see if I can get anything. Take Care, Ed[/quote] Try adding 10000 or so to the q-ranges in test.job within the current GNFS folder. That should skip the current range (thus skipping the part that makes it crash) and move on to the next. Usually that works for me. |
| All times are UTC. The time now is 22:54. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.