SLiMSuite is designed to be a suite of programs that enable you to navigate your way through most of the main motif discovery tasks. Well, I say designed but it would probably be more accurate to say evolved. All the programs within SLiMSuite arose from research needs within the lab. As a result, they are heavily biased to the kind of data that we analyse and data sources that we use. However, it should be fairly easy to get data from other formats and sources into SLiMSuite.
From a computer science perspective, input and output for SLiMSuite is just plain ASCII text. This makes it easy to plug SLiMSuite into existing scripts and pipelines - and manually view/edit any input or output files if required. However, “plain text” is not very informative, and SLiMSuite actually deals with a lot of different formats of plain text (from a “human formatting” rather than “file type” point of view). The documentation is currently in the process of being updated to better reflect these formats but some commandline options will still simply list
FILELIST as input parameters: see the accompanying descriptions to see what format these should be. Ask if it’s not clear! (File format documentation will also be added to the SLiMSuite blog, so check there.)
Within SLiMSuite, each file type has a distinct “file extension” that denotes the file type. Note that these are not enforced for input, although some programs may not always recognise the right format if a different extension is used. If you get odd input behaviour/errors that you do not understand, see if changing the file extensions helps. If you want a common file extension to be auto-recognised, let me know and I might be able to add it. SLiMSuite file extensions will not necessarily be recognised by other programs. NOTE: Operating systems will sometimes hide file extensions by default. If you are getting very confused, or have problems of extra
*.txt extensions on everything, try changing the system settings. (And/or becoming familiar with command-line file manipulation.)
The main file types used by SLiMSuite are:
MOTIFS= A list of SLiM motif patterns. SLiMSuite has its own motif format but a number of other formats will also work when given as input. This includes a plain list of regex patterns, and results tables from other SLiMSuite programs. [
ACCLIST= A list of Uniprot accession numbers. [
SEQFILE= A file containing biological sequences - usually protein sequences. (Some of the non-SLiM programs will use nucleotides sequences.) These can either be in fasta format (see
FASFILE) or Uniprot plain text format (see DATFILE). [
FASFILE= A fasta file of (unaligned) protein sequences. [
DATFILE= Uniprot plain text format [
ALNFILE= Aligned fasta file [
DSVFILE= Delimiter separated value text file. The delimiter will be auto-recognised if possible as a tab [
*.tsv], comma [
*.csv] or whitespace [
*.txt], or can be set with
delimit=Xif not recognised. Note:
delimit=Xinput may not work with every program, so it is safest to use a consistent files name. The
delimit=Xparameter is more commonly used to control output format.
TDTFILE= Tab delimited text file [
CSVFILE= Comma separated text file [
PPIFILE= Delimited text file with
Spoke(gene symbol) fields and preferably also
GENELIST= Plain text list of gene symbols.
XREFDATA= Delimited text file that links gene symbols to identifiers from other databases.
The main input formats for SLiM discovery are:
- A source of protein sequence data. This could be a protein FASTA file, a Uniprot plain text file, or a list of Uniprot accession numbers to download. For some tools, a single Uniprot accession number will work.
- A source of motif (regular expression) definitions. This is only required if looking for known (or other pre-defined) motifs and/or wanting to compare a set of de novo predictions with known motifs. A number of different formats are accepted for motif input, including SLiMFinder (summary) results and ELM downloads. The simplest/easiest is a plain text file of regular expressions. For more on motif regular expression formats, please see Edwards and Palopoli 2015.
The main output formats are delimited text files.