Skip to content

iterative ref: zero pad to avoid ctf aliasing #30

@geoffwoollard

Description

@geoffwoollard

I suggest developing with n_pix=32 or 64 to start with. real data will be more like 128 or 256. Can have issues with ctf at small pixels and need to zero pad to avoid artefacts. The artefacts from the ctf can arise from it not going to zero at edges, and the sinusoidal ctf rippling too fast.

See Penczek, P. A., Fang, J., Li, X., Cheng, Y., Loerke, J., & Spahn, C. M. T. (2014). CTER-Rapid estimation of CTF parameters with error assessment. Ultramicroscopy, 140, 9–19. http://doi.org/10.1016/j.ultramic.2014.01.009

One can

  • zero pad the real space inputs
  • take the fft on the zero padded inputs
  • make the ctf arrays on the lager sized array

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions