Project

General

Profile

Image path problem

Added by Steve Wilson almost 12 years ago

Hi,

We are installing myami-2.2-redux in a mixed Windows/Linux (Ubuntu 12.04) environment. We've tried several combinations for setting paths in leginon.cfg on the Windows microscope computer and the Linux workstation but we can't find one that will work for us.

The path on the Linux server is:
/em/leginon-data/leginon
There is a Samba share named "leginon-data" that makes available /em/leginon to the Windows PC as drive Z:.

leginon.cfg (on both the Linux and Windows boxes) has:
[Images]
path: /em/leginon-data/leginon

[Drive Mapping]
Z: /em/leginon-data

This almost works; the image files are transferred to the Linux box but the path stored in the database is a path like the following:
z:/test3/rawdata/test3_00007a_0.mrc
and the Leginon image viewer (running on the Linux box) obviously fails to locate this file. The file is actually located here on the Linux box:
/em/leginon-data/leginon/test3/rawdata/test3_00007a_0.mrc

I'm sure we must have something configured wrong. Any help would be greatly appreciated!

Thanks,
Steve


Replies (8)

RE: Image path problem - Added by Anchi Cheng almost 12 years ago

Maybe it is just a typo, but you said the Samba share named leginon-data makes available /em/leginon to Windows PC. However, you have /em/leginon-data on the linux path but no /em/leginon.

Drive mapping is not used much as we recommend running Leginon main program on Linux box rather than Windows PC. Is there a reason that you must work on the Windows?

Where is the database?

RE: Image path problem - Added by Anchi Cheng almost 12 years ago

Also, if you have done it right, when you open z drive on Windows, you should see leginon as a subdirectory,

RE: Image path problem - Added by Jim Pulokas almost 12 years ago

I have one way that I was able to partially reproduce the problem you have:

During the session setup wizard, you are given a default image path, and are allowed to modify it. However, it can be modified in a way that Leginon is not able to cope with. In your case, the default given would be: "Z:\leginon". If you change it to "z:\leginon" (make z lowercase), then it will insert improperly into the database, but still save the image in the expected location. Still not sure about the missing directory "leginon" in the database path.

I have just fixed the upper/lower case issue, committed in r17390. So if this is in fact your problem, then you can either get this new update, or just be sure to always use the same case for the drive letter in Leginon as you did in the config file.

Jim

RE: Image path problem - Added by Steve Wilson almost 12 years ago

Jim,

When the path is stored properly into the database, does it still contain the drive letter? It seems like that in itself would be a problem (apart from the missing higher-level directories) when attempting to open an image file under Linux. Or do the routines that read image files strip off the drive letter?

I'll check tomorrow with the Windows admin to see what he used for the default image path when running the setup wizard.

Thanks,
Steve

RE: Image path problem - Added by Steve Wilson almost 12 years ago

Hi Anchi,

Yes, there was a typo in my original post. /em/leginon should have been /em/legion-data.

We are trying to set up our environment like "Configuration A" in the Complete Installation documentation. The database is located on the Linux system.

Steve

RE: Image path problem - Added by Anchi Cheng almost 12 years ago

In that case, map drive is not needed. In actual operation, you will only be reading and saving image files from the Linux box. Just proceed to the next step. On the leginon.cfg on the Linux box, you just put in the full linux path "/em/leginon-data/leginon" for [Images]

RE: Image path problem - Added by Jim Pulokas almost 12 years ago

A path which is properly stored in the database will always be in linux based format. Windows based formats should only show up in the graphical interface, if it is running on Windows.

RE: Image path problem - Added by Steve Wilson almost 12 years ago

Thanks for all the help. I think our problem was (as Anchi pointed out) that we were trying to run Leginon for image capture on the Windows box rather than just running the client there. We have some more time next week scheduled on the microscope so hopefully we'll be able to finish the installation then.

Steve

    (1-8/8)