[3dem] Add random noise to reconstruction

[Vladan Lucic]

Hi Stelnar,


Perhaps you have double (overlapping) particles, as a result of double 
picking or translations during refinement for example. A quick way to 
check for this is to make particle half-sets from different tomograms 
(split tomograms in two groups and make each half particle set from one 
group). In this way, double particles will always be in the same 
particle half-set. If the FSC between these halves goes to 0, it's 
double particles.


Just a guess, hope it helps


Best,

Vladan


On 11/2/18 5:44 PM, Steinar Halldorsson wrote:
>
> Hi all
>
>
> I have something which looks like an artefact in my FSC curves from 
> tomography data calculated in Relion. Basically the curves hover 
> around 0.1 instead of reaching 0... And this is not coming from my 
> mask btw. There is quite a lot of information (protein) outside of the 
> mask, you can see clear but slightly smeary density from neighbours in 
> the final maps, and I wonder if this is causing these correlations? 
> One way I have thought to test this is to take my two half maps, 
> somehow add random noise to parts outside of my region of interest and 
> then recalculate my FSC.
>
>
> Firstly, does this sound like a reasonable thing to try?
> Secondly, does anyone have a suggestion of how to actually do the 
> random noise addition outside of my region of interest?
>
> Cheers,
>
> Steinar
>
>
> ---
>
> Steinar Halldorsson
>
> Postdoctorate Fellow
>
> Rosenthal lab
>
> The Francis Crick Institute
> London, United Kingdom
>
> The Francis Crick Institute Limited is a registered charity in England 
> and Wales no. 1140062 and a company registered in England and Wales 
> no. 06885462, with its registered office at 1 Midland Road London NW1 1AT
>
>
> _______________________________________________
> 3dem mailing list
> 3dem at ncmir.ucsd.edu
> https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ncmir.ucsd.edu/pipermail/3dem/attachments/20181102/42ae2e0e/attachment.html>