28 Apr 2005 mcxdeblast 1.005, 05-118
mcxdeblast - parse BLAST files and write mcxassemble input.
mcxassemble will in turn create input suitable for mcl.
mcxdeblast [--score=<b|e|r> (bit scores|e-values|normalize bit score)] [--sort=<a|o> (alphabetic|occurrence sorting)] [--m9 (expect BLAST column format)] [--abc (expect ID1 ID2 score format)] [--xi-dat=<suf> (strip <suf> from file-name)] [--xo-dat=<suf> (add <suf> to base name)] [--bcut=<val> (bit score cutoff)] [--ecut=<val> (E-value cutoff)] [--tab=<fname> (tab file)] <file-name>
If the input file is named iput, mcxdeblast will by default create files iput.hdr, iput.raw, iput.tab, iput.map, and iput.err. The hdr file contains information about the number of nodes found. It will be read by mcxassemble. The raw file contains the co-occurrence scores between different nodes (peptides), also to be read by mcxassemble. The co-occurrence scores are in terms of mcl indentiers, which are subjected to rearranging by mcxassemble in order to correctly align them with the tab file. The tab file contains bindings between mcl identifiers (after rearranging as specified in the map file) and the BLAST labels (peptide identifiers). Refer to the manual of mcxassemble for the syntax of a tab file. The err file contains a list of any errors encountered.
If the --tab=fname option is used mcxdeblast changes its behaviour. It will read the file fname, and use the bindings found therein. It will no longer output any of the hdr, map, or tab files. The hdr file should be provided by the same application that generated the specified tab file, and the map file should no longer be necessary (it might be convenient though and perhaps the future will bring a new --map option).
The --tab=fname option can be convenient e.g. if you split a BLAST job over multiple machines and want to apply mcxdeblast to each of the subresults. You do this by generating a single central tab file in advance. Then provide each instance of mcxdeblast with this tab file. Each instance will generate a raw file. The respective raw files can simply be concatenated and fed to mcxassemble using its -raw option. Additionally, a hdr file has to be specified for mcxassemble using its -hdr option. The syntax of hdr files is described in the mcxassemble manual. Currently there is usually only one variable in the hdr file, which is the number of bindings listed in the tab file. This number, in turn, should equal the total number of different peptides encountered in the BLAST input.