Overview

Running on a cluster

The current implementation of the cache that GimmeMotifs uses does not play nice with concurrent access, for instance on a cluster. The result is that the cache will get corrupted and that GimmeMotifs will fail. Until this is fixed, there is a workaround. In your job submission script, use something like the following:

NEW_CACHE=$TMPDIR/cache
mkdir -p $NEW_CACHE
if [ -z $XDG_CACHE_HOME ]; then
    XDG_CACHE_HOME=$HOME/.cache
fi
cp -r $XDG_CACHE_HOME/gimmemotifs $NEW_CACHE/
export XDG_CACHE_HOME=$NEW_CACHE
echo 'Using $XDG_CACHE_HOME for cache'

This will use a local directory to store the cache.

Motif databases

By default GimmeMotifs uses a non-redundant, clustered database of known vertebrate motifs: gimme.vertebrate.v5.0. These motifs come from CIS-BP (http://cisbp.ccbr.utoronto.ca/) and other sources. Large-scale benchmarks using ChIP-seq peaks show that this database shows good performance and should be a good default choice.

In addition, many other motif databases come included with GimmeMotifs:

You can specify any of these motif databases by name in any GimmeMotifs tool. For instance:

$ gimme scan TAp73alpha.fa -p JASPAR2018_vertebrates -g hg38

or

$ gimme motifs TAp73alpha.fa TAp73alpha.motifs -p HOMER -g hg38 --known