By default, cryoSPARC Live sets the mask to the max particle diameter. This is typically far too small. While one could simply set the max particle width to the desired mask size, that might result in too many junk picks. The mask width is manually adjustable by killing the 2D Class Stream job, building it with the desired mask diameter, and re-launching it.
This is a non-obvious process, and it would be preferable to set the diameter while picking the number of classes.
Totally agree it’s a helpful setting and not so intuitive to find coming from regular cryosparc use, since the 2D behavior changed. In live, I tend to template pick, increase particle diameter and decrease the inter-particle distance, then play with the pick filter to remove the junk which is pretty effective.
Also, you don’t have to start and kill the 2D stream job. You can build before the first run.
100% agree with this, it is a minor irritant every time I start a Live run, feels like it is fighting against me
Wanted to bring this topic back as it is still annoying me – anything in the works to change it?
and if you build custom job and remove the masking, but then restart the job it automatically reapplies the mask despite the parameters.
and streaming 2D class of a 24h dataset often takes nearly twice as long as live processing despite bulky resources. as multiple millions of particles add up, it’s unwise to “reassign all particles”.
and it’s unfortunate that you can’t change the amount of streaming 2D resources up or down ever. for live processing workers you can simply oversubscribe, then kill individual workers, then restart them as you please.