Leginon

Gabe,

I don't see any recent change in rct or libcv at all in branch 2.1. Are you talking about trunk? There is a change in r16069. It was done to fix the bug reported in #1291 If it is causing problem for you, we might have to revert it back. Craig wasn't able to fix the infinite loop problem with his more optimized algorithm for #1291 so he revert it to use another one that he thought safe to use. I tested it out and did not have problem with test images but I guess it does work right for you.

Please revert it back and see if it goes away. Does this happen all the time or just with some images?

I am running latest r17745 for RCT, but still have the same problem. I don't understand what Gabe's solution means.

Hi,

I installed latest trunk, 17823, but still got the same problem.

In csfit.c, I found the line 127 also has one more 'AffineTransformImage' and I changed it also to "SeparableAffineTransform" and reinstall libCV. But still got the same problem.

BTW, the libCV is installed in /usr/lib64/python2.6/site-packages/libcv since my PC is 64bit. I don't if it matters.

THX Jian,

Your screen shot of the terminal running Leginon does not show the same error the original Issue has. This might not be a bug but a parameter settings issue.

Please take screen shots of RCT node during setup like the ones shown in RCT_node_set-up. It will help with diagnosis. Take the screen shot like the last one you did, with both Leginon gui and terminal where some libcv info would be printed out. Make sure your grid is at Eucentric height, too.

Python seems import libcv from right place:
<module 'libcv' from '/usr/lib64/python2.6/site-packages/libcv/__init__.pyc'>

I followed the RCT_node setup page and I got a "libcv.FindRegions failed" error. I went through the C source files in libCV module and didn't find any function named FindRegions, but only a similar one is FindMSERegions.

Anchi,

I freshly install a new CentOS PC and latest version of Leginon, 17921. However I am still plagued by this libCV.MatchImages error. Can you take a look at it?

Many Thanks,
Jian

The tilt axis is horizontal in Leginon, but vertical in DM.

Attached a pair of images. I ran runlibCV.py with them, it finished and gives results
[ 4.25937500e+01 8.17187500e+00 3.90625000e-03 2.00781250e+00
7.81250000e-03 2.34375000e-02 6.25000000e-02 1.21093750e-01
3.90625000e-03 9.76562500e-02]
Total: 5.309375 +/- 12.6616438159

I also try following code:
[cbis@spirit libcv]$ python
Python 2.6.6 (r266:84292, Jul 10 2013, 22:48:45)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
import leginon.libCVwrapper
import pyami.mrc
tl = pyami.mrc.read('hl_tilt.mrc')
utl = pyami.mrc.read('hl_untilt.mrc')
result = leginon.libCVwrapper.MatchImages(tl, utl, 50, 0.8)

Image min and max are 0 402929
Image 1: keypoints: 1102; descriptors: 1657
Image min and max are 0 375920
Image 2: keypoints: 1447; descriptors: 2241
Found 482 matches between images
Found matrix that fit 20 out of the 482 matches.
Freeing all mem
1.38 0.03 0.00
-0.01 1.00 0.00
-183.59 -16.46 1.00

I put raise, or raise PublishError(e) or print e in the exception, but nothing printed out.

The MatchImages error occurs after first tilted parent image was taken. I don't understand where I did wrong.

Jian's solution worked.