Leginon

h1. Using Redux to serve images on myamiweb

Install Leginon and Appion web tools for viewing images and performing image processing through the web server.

Redux is new for CentOS 6 (PHP 5.3). 

h2. Installation

* Install python filesystem abstraction for redux caching:

<pre>

sudo easy_install fs

</pre>

* Install Myami packages

<pre>

cd myami

./pysetup.sh install

</pre>

h2. Copy the myami/myamiweb directory to your Apache web directory

Example:

<pre>

cd myami

#CentOS example

sudo cp -vr myamiweb /var/www/html/ 

#this is temporary for setup, revert to 755 when finished with this page

sudo chmod 777 /var/www/html/myamiweb  

#if you have SELinux enabled this command will help

sudo chcon -R --type=httpd_sys_content_t /var/www/html

</pre>

h2. Configuration

h3. Configure Redux

<pre>

> cd /YourMyamDownload/redux

> cp redux.cfg.template redux.cfg

</pre>

* You can also copy it to /etc/myami/redux.cfg if you prefer.

* Set a writable log path by the user starting it.  In this example, we start redux as root and save the log in /var/log/redux.log

* Edit the redux.cfg file as follows:

 

<pre>

[log]

file: /var/log/redux.log

</pre>

 

* Turn on redux caching if desired:

 

<pre>

[cache]

enable: yes

path: /var/cache/myami/redux

disksize:  500

memsize: 500

</pre>

 

** *You need to make sure the cache path exists and writable by the user that starts the redux server (reduxd)*

** Input the desired disk_cache_path, disk_cache_size, and mem_cache_size in the next few lines

** Create the disk_cache_path before running redux if cache will be used

h3. Configure Web Interface (myamiweb) 

There is a setup wizard available to help you set the configuration parameters for your installation. If you prefer not to use the wizard, there are instructions for manually editing the configuration file. If this is your first time creating the web tool configuration file, we recommend using the setup wizard.

+Configuration using the setup wizard+

The setup wizard will check your database connection, create required database tables, and perform default data initialization.

* Run the online setup wizard by visiting http://yourhost/myamiweb/setup or http://localhost/myamiweb/setup to create the myami website’s config file.

 

*Tips:*

# You need to know your database setup before you start.  If you have been using the parameters in this instruction, here is a [[Explanation of Sample Names|summary]].

# To discover what the Apache user is:

<pre>

sudo egrep -iw --color=auto '^(user|group)' /etc/httpd/conf/httpd.conf

</pre>

# You also need to decide whether you would like to enable the [[appion:What does User Authentication do to myamiweb|user management system]].

+Manual configuration instructions (Advanced User)+

Go to [[appion:Install the Web Interface Advanced]] for the advanced configuration.

h3. Revert permissions

<pre>

sudo chmod 755 /var/www/html/myamiweb

</pre>

h2. Test Installation

# Using Redux to do simple input output (simple client with no reduxd server needed):<pre>redux --filename=test.jpg --oformat=PNG > test.png</pre>Make sure the resulting test.png is in fact an image and not an error message.

# Run the server:  run the following on a command line:<pre>reduxd</pre>leave it running for the following...

# Test command line client connecting to the server<pre>redux --server_host=localhost --filename=test.jpg --oformat=PNG > test.png</pre>Note: The input file name is from the perspective of the reduxd server, so be sure to give it an absolute path (unlike the first test, which was not accessing the server)

# Check the redux.log created as configured in redux.cfg.  This contains the port opened by redux server that will allow myamiweb to connect to.

h2. Assign redux client to connect to redux server in myamiweb

* At myamiweb/config.php

<pre>

define('SERVER_HOST',"localhost")

define('SERVER_PORT',"55123");

</pre>

*The server port chosen should match the value found in redux.log when the redux server is started*

h2. Setup fftw to use wisdom (myami-3.0 only)

*This applies only if you see the messge "*** Using custom copy of fftw3"* in the previous redux test.

fftw runs much faster on odd image dimension if a wisdom is saved. It is best to create the wisdom ahead of time using the stand alone script pyami/fft/fftwsetup.py.  It will store the wisdom you create in your home directory with a name like 'fftw3-wisdom-hostname'.  If you only start reduxd as root and fftwsetup.py is run as root, this is enough.

* Redux needs write permission at its installation location to write fftw wisdom file.

* For developer only: you can copy the wisdom file to any other home directory that wants to use it, or copy it as root to a file called /etc/fftw/wisdom which any user can access.

h3. Using fftwsetup.py:

FIrst, you need to know the typical image dimension redux needs to process, especially the large ones and *ones that are not powers of 2 such as those produced by Gatan K2*.

<pre>

cd /YourMyamDownload/pyami/fft

./fftwsetup.py 1 number_of_rows number_of_colums

</pre>

For example, for K2 summit super-resolution image there are 7676 rows and 7420 columns, therefore, the command line is

<pre>

./fftwsetup.py 1 7676 7420

</pre>

This may take a few minutes.

Run this for as many dimensions you know will be used and move it for general use as instructed above if preferred.

h2. Using redux server with myamiweb (recommended)

# start reduxd server if not already running from the above test:<pre>reduxd</pre>

# click on "[test dataset]" on your main myamiweb home page, or go directly to the URL: myamiweb/viewerxml.php

# test by accessing your own images from Leginon in myamiweb/imageviewer.php

h2. starting reduxd at boot

<pre>

sudo cp -v myami/redux/init.d/reduxd /etc/init.d/

sudo service reduxd start

</pre>

h2. Alternative reduxd installation on file server rather than web server

This approach is less tested, but has been found necessary in the case of a very high load system (multiple microscopes acquiring data, multiple processing jobs, multiple web clients and servers, etc).  The problem has been that all of this demand for image I/O is occuring over NFS, and the NFS server is not coping with the high demand.  One solution we have been investigating is to run reduxd directly on the file server rather than the web server.  This means reduxd has direct access to the image files (not through NFS) and the web server now accesses reduxd over the network rather than locally.  This has two potential benefits:  1) less load on the NFS server, 2) only transferring JPEGs over the network, not MRCs.

How to do it:

# Install required myami components on the file server, at least pyami, sinedon, numextension, redux, leginon, modules, and any other 3rd part packages required by those.

# (optional) edit init.d/reduxd and use the optional high priority command line (see comment in that file)

# Configure redux.cfg on file server and start reduxd

# On web server, configure config.php:  turn off all caching options, set redux server host to be the file server

# skip starting reduxd on the web server

# skip imcache as described below, since this also uses redux locally and accesses images over NFS

{{include(leginon:Using imcache to cache mrc images as jpeg images of the default size on myamiweb)}}