Appion

h1. File Server Considerations

A specific file tree structure has been assumed as default in Appion/Leginon.  Until v2.2 release, this can not be altered.  Here is a description of it:

# Leginon default image path is defined in leginon.cfg.  The acceptable form is */your_file_server_mount_point/whatever/leginon*.  The images are saved by sessionname under subdirectory of this directory in a form such as 

*/your_file_server_mount_point/whatever/leginon/sessionname/rawdata/*.

# Appion processing is default under appion directory parrallel to leginon directory, i.e., /your_file_server_mount_point/whatever/appion.  This relationship is hard-coded until v2.2 release.  The processing are divided by sessionname and then processingtype and then runname of the process.  Therefore, your processing results are saved in the following default appion path: */your_file_server_mount_point/whatever/appion/sessionname/processing_type/runname/*

The following permission rule is required for multi-unix-user usage of Leginon/Appion:

For Leginon:

# The web server apache user need to have read permission to all images in the rawdata directories in order to display them in the viewer.

# all users need to have permission to create directory in */your_file_server_mount_point/whatever/leginon*

# all users need to have read permission in a leginon rawdata directory that contains reference images.

# Users need to have write permission to the session they created, of course.

For Appion:

# The web server apache user need to have read permission to processing directories to display the results.

# All users need to have permission to create directory in */your_file_server_mount_point/whatever/appion*

# If more than one user will be processing data in the same session, they all need write permission to the session directory */your_file_server_mount_point/whatever/appion/sessionname/*