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

43506: i1153, size 112, [COLOR=Red]2^3*3*5[/COLOR]

Reserving 45168 45672 45708 47268

Done with 45672 47268.
Reserving 49692 48510 48720 48780 48864.

Keeping 43158, 114 digits, 2^5*3. It escaped with 2*3^2*p at 111 digits.

done with 41160
reserving 41760

releasing 42144 and 49320 since i'm away for a week
42144 at 110 digits (ecmed) 2^2*3*7,
49320 at 108 digits (ecmed) 2*3*5^3

Done with 45168 and 45708.

Done with 48510 and 48864.
Reserving 46410 and 46758.

reserving 41916

done with 49868, 113 digits, 2^2*3*7

Done with 46410, 48720, 48780.

unreserving 41916 at i=937, size 113, [COLOR="Red"]2²*3*7³[/COLOR]

taking 49320 again

Done with 43974 and 49692.

Done with 43456, 114 Digits, 2^3*3*5
Done with 43752, 110 Digits, 2*3^2*7 - Escaped from its driver for a time, but then picked up 2*3. I have had more escapes than I was expecting.

done with 49320 driver 2*3^2
taking 49236

done with 41760
reserving 42024

Done with 43758, 115 digits, 2*3 driver
reserving:
46020, 46086, 46116, 46140, 46224, 46290, 46560, 46854,

49236 has hit the downdriver at 110 digits, keeping it

done with 46758

went a bit overboard with 49236... now 121 digits, ecm'ed at 3e6(118 digits) and its driverless (2^5*3). below is the graph., started at iteration 1082

taking 42084

[QUOTE=firejuggler;220658]went a bit overboard with 49236... now 121 digits, ecm'ed at 3e6(118 digits) and its driverless (2^5*3). below is the graph., started at iteration 1082[/QUOTE]

Are you releasing it?

yup, releasing it

releasing 42084, 115 digits, 2^2*3^2*7
taking 45816

done with 45816, 2^6*127 driver
taking 42750

Done with 46020, 111 Digits, 2^2*7^2
Done with 46086, 113 Digits, 2^2*3^2*5*7
Done with 46140, 114 Digits, 2^2*7^2

releasing 42750 taking
48024, 48816

48024 and 48816 done.
taking 42192, 42448,

42192 and 42448 done, taking 49680, 49764

taking 42798

taking 49656

done with my 49764 and 49680
taking [B]49062[/B] and [B]49482[/B]

done with 42024
reserving 45570

done with [B]49062[/B] and [B]49482
[/B]
taking [B]47560 [/B]and [B]47720[/B]

taking 45678

done with 47560 and 47720

taking 45810 and 49600 (49600 already at 109 digits, 2^4*31) and... 47208

Will take 47400 49554

... and 49560

done with 45810 ,49600 and 47208
taking the last one , 49170

45678 at 111 digits, sitting happily with the 2*3 driver; C109 at iteration 1070. Done.

49656 at iteration 854, 115 digits, still 2*3 driver, C111 remaining; call it done.

42798 at iteration 1715, 111 digits, lead factor 2^5 so it's sort of stable-ish; it's done for the purposes of this project but I'm hanging on to it to see where it goes next.

49170 done... now , on subproject #6...
by the way, where is #5 (or is it 10-50 k to 120 digits?)?


edit : ah, i found it [B]Subproject #5: 800k-900k sequences to 100 digits.[/B]

47400 49554 and 49560 are done

46116 is done, 119 digits, 2^2*7
Keeping 46224, 110 digits, 2^2*3

done with 45570

Done with 46560, 120 digits, 2^3*3*7
Done with 46854, 121 digits, 2^2*3^3*5*7

Not sure why 46290 isn't appearing in the database. Need to investigate it.

46290 is now in the db, 111 digits, 2^2*3*7

[QUOTE=fivemack;222060]45678 at 111 digits, sitting happily with the 2*3 driver; C109 at iteration 1070. Done.[/QUOTE]

Just spotted this. Not sure why I missed it first time round. :redface: Oddly, it is now at 118 digits in the DB, despite the statement that it was done at 111 digits. Anyway, Subproject #4 is now complete. :smile: