Leginon

I closed my previous MotionCor2 ticket (http://emg.nysbc.org/boards/6/topics/3079), so am opening a new one.

I downloaded the MotionCor2 binary from here: http://msg.ucsf.edu/em/software/motioncor2.html

and compiled and installed Cuda 8 from: https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/

MotionCor2 is linked against an older version of libtiff, libtiff.so.3. Most Ubuntu users seem to be employing the hack:

ln -s /usr/lib/x86_64-linux-gnu/libtiff.so.5  usr/lib/x86_64-linux-gnu/libtiff.so.3

I tried this and it seemed to work, but thought it a bad idea, and harvested a copy of libtiff.so.3.9.4 from a CentOS 6 VM to install in /usr/local/lib.

As soon as I switched to using the "correct" libtiff library, MotionCor2 started complaining about a missing libjpeg.so.62, but this is available as an Ubuntu 16.04 package.

Now the issue: this version of MotionCor2 doesn't appear to work with Appion no matter which libtiff.so it is using!

My users had a functional MotionCor2 on another machine, and when I compared the file sizes, they are obviously completely different:

Current version:

root@kraken:/usr/local/bin# ls -l MotionCor2-1.0.0 
-rwxrwxr-x 1 root root 2140704 Jul  5  2017 MotionCor2-1.0.0

Version harvested from another machine:

root@kraken:/usr/local/bin# ls -l motioncor
-rwxrwxr-x 1 cnsit cnsit 1167759 Jan 30  2017 motioncor

The harvested version (origin unknown) produces what appear to be correct results when used in Appion, the newly downloaded one doesn't seem to do anything. Not sure what to make of this, but thought I should report it.