reserving 1073310

[QUOTE=unconnected;484535]Can we assume these sequences has some ECM work before releasing?[/QUOTE]

No.
Composites are sent to hundred of volunteers fully automatic and they run always a complete yafu factorization. If composite gets too large the sequence will e released.

Statistics about yafu@home are here [url]https://boincstats.com/en/stats/121/project/detail[/url].
You can see that currently 2900 hosts are active (I assume active means they returned at least one factorization in the last 60 days).

Wow, that's a substantial computer power! I realized now why you are reserving so many sequences :smile:

Reserving 1740432

Reserving 746856 1950660

Update 887118 1780350 1943424 1585800 126000 1999500 1655904 493374 1999644
Update 142302 1635576 236400 1743624 1420464 1537038 1414944

Drop 887118 1943424 1999500 493374 1999644 142302 1635576 236400 1743624
Drop 1420464 1537038 1414944

Drop 1667820

Taking 1965024 683628

[QUOTE=unconnected;484535]Can we assume these sequences has some ECM work before releasing?[/QUOTE]
Agree, it should be nice, at least for those escaping into the upper side (for the lower/mid sides the ECM doesn't take longer, and a new asignee will do it again anyhow). Aliqueit has the "-d" and "-c" and "-b" switches that cooperate very well to achieve this goal (however I don't know if yoyo's boinc-ify uses aliqueit).

[QUOTE=yoyo;484561]No.
Composites are sent to hundred of volunteers fully automatic and they run always a complete yafu factorization. If composite gets too large the sequence will e released.

Statistics about yafu@home are here [URL]https://boincstats.com/en/stats/121/project/detail[/URL].
You can see that currently 2900 hosts are active (I assume active means they returned at least one factorization in the last 60 days).[/QUOTE]
The window was opened yesterday and the reply incomplete, I didn't refresh before posting the above. yafu can only do ecm, and it can use -e switch to skip the ECM phase, and if you use something similar to aliqueit to pass them composites, then you can use -c switch in it to tell yafu "do only ecm if the composite is larger than xxx digits". Otherwise a lot of time will be lost because everybody will have to switch to re-do ecm for all composites, because we will have no way to know which composites come from yoyo@home and which come from other "crumblers". These other "crumblers" (me included) have the habit to well-ecm composites and only abandon a sequence if a composite is large enough and it passes a certain ecm kicks and punches....

Again, no.
You can do this if you handle each composite individually. As I stated, I do a mass handling and the workflow is, that a composite is send to a volunteer to factorize it and send the factors back and the factors are reported to factordb. This is done many thousands times per day and fully automated.
To handle "some" composites different a complete new automated workflow has to be implemented.
That is not so easy as you do it by handling each composite individually.