This section will walk you through the steps necessary to install the motif analysis system. Once this installation is complete users will be able to define motif finding jobs, run them through the request queue, and then compare the output graphically with the motifCompare nodes. We have packaged the entire system, so that you only have to extract a tarball and change a couple of settings.
Prerequisites
Steps to follow for complete system installation
tar zxpvf motifAnalsyis_1.x.tar.gz
$db_url = 'mysql://username:password@localhost/databaseName';
. Update the username, password, and databaseName to reflect your setup.
In the file motifCron.php, you need to replace "YourWebRoot" with the appropriate URL that directs to your website.
mysql -u mysql_user -p mysql_database < motifAnalysis_1.x.sql.
It is important to note that this is a complete installation, so this should be done with an empty database.
These directories are used by the system: files, imgTmp and tmp. They must be writable by apache. The -p option used to untar the files previously, should preserve the permissions. The default permission states that the directories are writable by everyone, so Apache will be assured to write to these directories. This is rather insecure, so you might want to check with your system administrator to verify if this is ok to do.
motifPrograms/AlignAce
motifPrograms/bioprospector
motifPrograms/DME
motifPrograms/MDScan
motifPrograms/MEME
motifPrograms/MotifSampler
It is a good idea to ensure that these programs can be run on your server. If not, you need to recompile these programs, in which case please maintain the same file structure as above. These programs are all free for educational purposes, but you might need to obtain licenses to run them.
note: MEME is a directory containing all of the MEME files. It is not simply a binary, but depends on a number of things, so the entire directory should be in motifPrograms. Same is true for MotifSampler. You might want to look into the file sites/all/modules/motif/motifPrograms.inc to see how the paths to these programs are configured.
If you decide that you would rather change the references to the programs in the code, check out step 4 in the module install tutorial below.
That's it.
Install the modules using a current Drupal system (choose this installation only you are confident with configuring Drupal).
gzip -d motifAnalysis_1.x_module.tar.gz
tar -xvf motifAnalysis_1.x_module.tar
Files and Directories created:
_motifCron.php motifCron.php loading.gif MOTIFINSTALL.txt
weblogo/*
sites/all/modules/motifcompare/*
sites/all/modules/motif/*
cckExport/*
motifPrograms/*
imgTmp -- used to store the weblogo images
This directory must be writable by apache, as apache will be executing the programs
that create the weblogos.
** Note: If this directory is not in the Drupal web root, then a global variable must be changed
as described in step 4.
tmp -- used to store session files. Also must be writable by Apache.
motifPrograms/AlignAce
motifPrograms/bioprospector
motifPrograms/dme
motifPrograms/MDscan
motifPrograms/meme
motifPrograms/MotifSampler
If you cannot put the program files in motifPrograms, then some variables need to be changed within the code. The file 'sites/all/modules/motif/motifPrograms.inc' contains a block at the top where global variables are set.
The location of the motif finding programs as well as temporary storage directories and the directory for storage
of the weblogo images MUST be configured. The .inc file has more comments on the specifics.
CCK should be installed and directions on how to do that can be found here (http://drupal.org/project/cck).
FileField should be installed and directions on how to do that can be found here (http://drupal.org/project/filefield).
The content types can be imported by going to Administer->Content Types->Import. The content of each file in cckExport
should be copied and pasted, separately, into the textarea on the import screen.
This can be done through Administer->Modules
The instalation can be tested by defining jobs and running them via the request queue, then comparing them by creating motifcompare nodes.
If jobs are not in the request queue, verify that the motif_queue mysql table was created.
If jobs are showing up in the queue but are not executing, verify that motifCron.php has the correct path in the wget statement.
If jobs show error status, make sure that the paths set in 'sites/all/motif/motifPrograms.inc' correctly point to their respective programs.
If the jobs execute and the motifcompare nodes do not show any images, check your imgTmp directory to make sure they were generated.
The naming convention is 'weblogo_nodeId_*' where nodeId is the id of the node they should be created for and *
is a number from 0-M. M is the number of motifs minus 1. If the output from the programs is received correctly and stored in the database,
then there is a problem with the weblogo stuff. Make sure the path to the weblogo/createLogos.cgi program is configured in 'sites/all/motif/motifPrograms.inc'