Seems reasonable; even if we jump straight into 2330M, we won't start it until September and won't finish it until Jan/Feb '20. 2,1165+ won't get attention from us for poly select until winter solstice, unless we're poly selecting sooner for Greg to sieve.

[QUOTE=VBCurtis;521357]Seems reasonable; even if we jump straight into 2330M, we won't start it until September and won't finish it until Jan/Feb '20. 2,1165+ won't get attention from us for poly select until winter solstice, unless we're poly selecting sooner for Greg to sieve.[/QUOTE]

Someone with access will need to reorder the yoyo inputs.

[QUOTE=R.D. Silverman;521353]I see that someone queued additional trials for 2,1165+ with yoyo.

Given Greg's comments about queuing 2,2150M, 2,2158L, and 2,1084+ it seems
that these should have ECM priority. Greg is likely to get to them before this
forum gets to 2,1165+ so it seems that finishing ECM on the latter can be postponed...
Finishing ECM on 2,2330M OTOH is somewhat more immediate.

Comments??[/QUOTE]

I was the one who queued the numbers in yoyo. Tried to finish what had been started and then move into the new priorities. But if a reordering is desired then I will have to go to Yoyo directly - he’s the only one who can edit the queue once it’s in place.

What do folks want to queue first?

[QUOTE=swellman;521424]I was the one who queued the numbers in yoyo. Tried to finish what had been started and then move into the new priorities. But if a reordering is desired then I will have to go to Yoyo directly - he’s the only one who can edit the queue once it’s in place.

What do folks want to queue first?[/QUOTE]

My $.02 :

Finish 2,2330M, then queue Greg's suggestions.

[QUOTE=R.D. Silverman;521430]My $.02 :

Finish 2,2330M, then queue Greg's suggestions.[/QUOTE]

Oops. Error! This should be 2,2210M.....

Following Curtis suggesting on helping on post processing I was wondering how fast these new 12c/24t AMD Ryzen’s would be since I think I have now conditions to purchase a machine after a long term, since 2012, without buying any computers and after investing on a desk, a chair and a 27” screen for my wife PhD study room. Need to treat myself too.

[QUOTE=R.D. Silverman;521432]Oops. Error! This should be 2,2210M.....[/QUOTE]

Yoyo kindly killed the rest of the CN queue. I’ll update it tomorrow night with 2,2210M as the focus.

[QUOTE=swellman;521536]Yoyo kindly killed the rest of the CN queue. I’ll update it tomorrow night with 2,2210M as the focus.[/QUOTE]

My $.05

It's already half done.

It should then be followed by the four numbers Greg wants to do (2,2150M, 2,2158L,
2,1084+, 2,1157+) before returning to finish 2,1165+.

[QUOTE=R.D. Silverman;521556]My $.05

It's already half done.

It should then be followed by the four numbers Greg wants to do (2,2150M, 2,2158L,
2,1084+, 2,1157+) before returning to finish 2,1165+.[/QUOTE]

BTW, does anyone know what is happening with 2,2102L? It had already been
sieved, now it seems to be sieving again. Of course sometimes relations fall short
and a number needs additional sieving, but the resieve effort for 2,2102L has been
going on for sufficiently long that I suspect this is not the case.

Project update:
Starting about a week from now, I will be substantially less able to look after this project for a couple of weeks. I have granted logon access to a couple of forumites whom I have collaborated with in the past, and they have collectively agreed to keep an eye on the project and give the server a kick if needed.

Our yield has been a fair amount better than expected, which shifts downward our target Q-value to change from I=16 to I=15. I estimate this Q-value at 190M or so, with 1400M raw relations found by then. Since I am not confident I'll be available to do this changeover later, on Sunday 21st I will be changing the server over to I=15.

It would be nice to get to 1400M relations by that time, but it's not like the project will suffer noticeably if we don't get there. I=15 will be substantially faster, a bit faster than the first few days of the project were. We will sieve to something like Q=850M, with yield dropping from nearly 3 to around 1.5 by the end.

I choose the crossover point by matching the sec/rel of the last Q-range at I=16 with the last (expected) Q-range at I=15. I expect I=15 to produce 10% more duplicates (this is a made-up number, based very loosely on comparisons of NFS@home 15e queue vs 16e), so I added 10% to the I=15 timing. This makes us indifferent whether our slowest relation is found with I=16 or I=15; seemed as good a reason as any.

Remdups on Q from 8M to 150M: 746M unique. Our target is 1800M unique, which will almost surely require more than 2700M raw.
This is the first time I've ever seen largest dimension used over 2500 in remdups.