search

leginon-org / leginon-redmine-archive

1 stars 0 forks source link

particle mean and std #359

Open leginonbot opened 8 months ago

leginonbot commented 8 months ago

Author Name: Scott Stagg (Scott Stagg) Original Redmine Issue: 359, https://emg.nysbc.org/redmine/issues/359 Original Date: 2010-04-16

Currently when we make a stack, there is a feature that generates a plot of mean vs. standard deviation. It seems to display the unnormalized values for both of these numbers. These are definitely important numbers, but this should be displayed for a picking run instead of for a stack.

leginonbot commented 8 months ago

Original Redmine Comment Author Name: Neil Voss (@vosslab) Original Date: 2010-04-18T23:28:36Z

That would be nice, but you cannot get the mean and standard deviation inside a particle box until you define a box size.

leginonbot commented 8 months ago

Original Redmine Comment Author Name: Scott Stagg (Scott Stagg) Original Date: 2010-04-19T10:24:29Z

You don't have to have a box size, because we require that users define a particle size. If you define a box size that is 1.5 times the size of the particle, then it should work like I have suggested.

leginonbot commented 8 months ago

Original Redmine Comment Author Name: Neil Voss (@vosslab) Original Date: 2010-04-19T13:03:33Z

I see how this would be convenient, but it would slow down the particle picking process, unless you used the binned, filtered image. I guess we prefer to create sub-stacks of the original stack, but this can fill up a hard drive.

The history of this feature is that Clint created a MATLAB script that sorted particles based on their mean and standard deviation and found that particles on the periphery of the plot were over carbon had bad CTF artifacts. So, we wrote it that way.

leginonbot commented 8 months ago

Original Redmine Comment Author Name: Scott Stagg (Scott Stagg) Original Date: 2010-04-19T13:56:26Z

You wouldn't have to do it during picking necessarily. You could do the stats. calculation after picking is finished. This wouldn't fix the CTF artifact problem, though. It still seems like this would be more valuable as a picking filter than it is as stack postprocessing. The earlier you can get bad picks out, the better.