![]() |
41982 : 1718 has a 3*19 factor (57 is still considered composite)
following line is 3382153428399072538847573742821380566489993749198821606892113307360201528260648170388959018172518183906152274 (c109) |
Could you please run this to 110 digits anyway?
|
[QUOTE=Andi47;218140]Unreserving 40224 at index 2483, size 113, [COLOR="Red"]2*3[/COLOR]*<small factors>*c82 (with little ECM on the c82)[/QUOTE]
Extended to i2502: 114 digits with 2*3 and C101, ECM upto B1=50k complete with yafu |
41982 ran to 110 digits
broken at 1718 cause of 3*19 [quote] 1719 . 3382153428399072538847573742821380566489993749198821606892113307360201528260648170388959018172518183906152274 = 2 * 3 * 103 * 235307 * 984397 * 50957807 * 150985867 * 494958570131 * 29536746246151 * 5748706603693543321393759 * 36538526574911668859346950717 [/quote] taking 49950 |
Releasing 43578 and 44160
I'll run 90K - 100K to 110 digits over the next couple of weeks. It will run unattended so no promises on how far it will get. |
reserving 49950
|
sorry, i took 49950 and i'm almost done look a few post above
|
[QUOTE=firejuggler;218624]sorry, i took 49950 and i'm almost done look a few post above[/QUOTE]
Oops, so I'll take 49868 as a try. |
firejuggler reserved 49950 in an edit, but after Mini-Geek had read his post and removed 41982 from the list. I think this might be a good idea:
[b]When making an edit to a post containing reservations/releases, write a separate post if the first piece of information has already been taken into account in the first post. Otherwise edit the post as usual.[/b] |
[QUOTE=10metreh;218664][b]When making an edit to a post containing reservations/releases, write a separate post if the first piece of information has already been taken into account in the first post. Otherwise edit the post as usual.[/b][/QUOTE]
Yes, I agree. The only problem with that is that if it's happening over a short time period, even this may not help. Imagine that: at 2:30:00 someone makes a post releasing a number at 2:30:05 I see that post and begin editing the first post to reflect the release at 2:30:07 the person wants to reserve a new number, checks that the first post hasn't been updated yet, and starts editing to reserve a new number at 2:30:10 I finish my edit at 2:30:12 they finish their edit In a case like this, your rules were never broken by either person, but their new reservation would still be ignored. (I know that's not what happened here due to the time periods, but it's probably happened; in any case, it's not terribly unlikely that it could happen.) So maybe what you wrote, but with the addition of something like: [B]Always check that any releases/reservations you added in edits are added to the first post when the earlier part of your post is. If it's not, repost it in a new post to bring it to the attention of the mods.[/B] |
yeah, that's what happened, sorry.
releasing 49950, c111, 2^6*127 driver (ecm'ed a bit @ 25e4) taking 42144 and 49320 |
| All times are UTC. The time now is 21:52. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.