mpiblast
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| mpiblast [2010/01/19 11:10] – 172.26.0.166 | mpiblast [2010/01/29 09:39] – 172.26.0.166 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Parallel implementation of NCBI's BLAST algorithm. | Parallel implementation of NCBI's BLAST algorithm. | ||
| - | http:// | + | * http:// |
| - | OpenMPI FAQ: http:// | + | |
| < | < | ||
| Line 27: | Line 26: | ||
| The Data variable gives the location of the NCBI Data directory containing BLOSUM and PAM scoring matrices, among other things. The scoring matrix files are necessary for any type of protein BLAST search and should be accessible by all cluster nodes. The BLASTMAT variable also specifies the path to the scoring matrices, and will usually be identical to the Data variable. The BLASTDB variable tells standard NCBI blastall (not mpiBLAST) where to find BLAST databases. As previously mentioned, the Shared and Local variables give the shared and local database paths, respectively. By setting BLASTDB to the same path as Shared, it is possible for NCBI blastall to share the same databases that mpiBLAST uses. In such a configuration, | The Data variable gives the location of the NCBI Data directory containing BLOSUM and PAM scoring matrices, among other things. The scoring matrix files are necessary for any type of protein BLAST search and should be accessible by all cluster nodes. The BLASTMAT variable also specifies the path to the scoring matrices, and will usually be identical to the Data variable. The BLASTDB variable tells standard NCBI blastall (not mpiBLAST) where to find BLAST databases. As previously mentioned, the Shared and Local variables give the shared and local database paths, respectively. By setting BLASTDB to the same path as Shared, it is possible for NCBI blastall to share the same databases that mpiBLAST uses. In such a configuration, | ||
| - | |||
| - | ===== wwwblast ===== | ||
| - | http:// | ||
| Line 61: | Line 57: | ||
| < | < | ||
| Total Execution Time: 98.3068</ | Total Execution Time: 98.3068</ | ||
| + | |||
| + | < | ||
| + | |||
| + | real 3m6.163s | ||
| + | user 0m0.046s | ||
| + | sys | ||
| + | |||
| The number of processes for an MPI job should be +1 of the number of CPUs because one process is used as the master to control the other jobs. | The number of processes for an MPI job should be +1 of the number of CPUs because one process is used as the master to control the other jobs. | ||
| + | ===== Random Notes ===== | ||
| + | ==== Number of Jobs ==== | ||
| + | |||
| + | https:// | ||
| + | |||
| + | %%With formatdb, the number of nodes refers to compute node number. | ||
| + | With mpiBLAST, np refers to number of processes, which isn' | ||
| + | necessarily linked to compute node or processor number. You can run | ||
| + | 10 processes on 4 processors. But it's recommended to run a single | ||
| + | process per processor. But the minimum number of processes for | ||
| + | mpiBLAST is 3, no matter what your compute node number is.%% | ||
| + | ==== Number of Fragments ==== | ||
| + | Rule of thumb for large databases, one segment for every gigabyte (144 GB, 144 segments). | ||
| + | |||
| + | * http:// | ||
| + | * https:// | ||
| + | ==== Incorrect mpiBLAST Version ==== | ||
| + | < | ||
| + | mpiblast-1.5.0-pio | ||
| + | $ mpiblast --version | ||
| + | mpiblast version 1.4.0 | ||
| + | </ | ||
| + | You're not crazy, it's a known issue. 1.5.0 reports as 1.4.0: http:// | ||
| ===== Links ===== | ===== Links ===== | ||
| * Submitting MPI jobs using SGE: http:// | * Submitting MPI jobs using SGE: http:// | ||
| * mpiBLAST Guide: http:// | * mpiBLAST Guide: http:// | ||
| * Updating the BLAST databases: http:// | * Updating the BLAST databases: http:// | ||
| + | * Rocks documentation on mpiBLAST: http:// | ||
| + | * wwwblast: http:// | ||
| + | * OpenMPI FAQ: http:// | ||
| + | |||