MotionCor2 1.4.7-GCCcore-10.3.0-CUDA-11.3.1

MotionCor2 correct anisotropic image motion at the single pixel level across the whole frame, suitable for both single particle and tomographic images. Iterative, patch-based motion detection is combined with spatial and temporal constraints and dose weighting. Cite publication: Shawn Q. Zheng, Eugene Palovcak, Jean-Paul Armache, Yifan Cheng and David A. Agard (2016) Anisotropic Correction of Beam-induced Motion for Improved Single-particle Electron Cryo-microscopy, Nature Methods, submitted. BioArxiv: https://biorxiv.org/content/early/2016/07/04/061960

Accessing MotionCor2 1.4.7-GCCcore-10.3.0-CUDA-11.3.1

To load the module for MotionCor2 1.4.7-GCCcore-10.3.0-CUDA-11.3.1 please use this command on the BEAR systems (BlueBEAR, BEARCloud VMs, and CaStLeS VMs):

module load MotionCor2/1.4.7-GCCcore-10.3.0-CUDA-11.3.1

BEAR Apps Version

2021a

Architectures

EL8-haswellEL8-icelake

The listed architectures consist of two part: OS-CPU.

  • BlueBEAR: The OS used on BlueBEAR is represented by EL and there are several different processor (CPU) types available on BlueBEAR. More information about the processor types on BlueBEAR is available on the BlueBEAR Job Submission page.
  • BEAR and CaStLeS Cloud VMs: These VMs can have one of two OSes. Those with access to a BEAR Cloud or CaStLeS VM should check that the listed architectures for an application include the OS of VM being used. The VMs, irrespective of OS, will use the haswell CPU type.

More Information

For more information visit the MotionCor2 website.

Dependencies

This version of MotionCor2 has a direct dependency on: CUDA/11.3.1 GCCcore/10.3.0 libjpeg-turbo/2.0.6-GCCcore-10.3.0 LibTIFF/4.2.0-GCCcore-10.3.0 zlib/1.2.11-GCCcore-10.3.0

Required By

This version of MotionCor2 is a direct dependent of: RELION/3.1.3-foss-2021a-CUDA-11.3.1

Other Versions

These versions of MotionCor2 are available on the BEAR systems (BlueBEAR, BEARCloud VMs, and CaStLeS VMs). These will be retained in accordance with our Applications Support and Retention Policy.

Last modified on 17th June 2022