Introduction
TomTom is a tool for comparing motifs to a known set of motifs. It
takes as input a set of motifs and a database of known motifs to return
a ranked list of the significance of the match between the input and
known motifs. TomTom can be run using the runTomTom()
function.
Accepted database formats
runTomTom() can accept a variety of inputs to use as the
“known” motif database. The formats are as follows: - a path to a .meme
format file (eg "fly_factor_survey.meme") - a list of
universalmotifs - the output object from runDreme() - a
list() of all the above. If entries are named,
runTomTom() will use those names as the database
identifier
Setting a default database
memes can be configured to use a default .meme format file as the
query database, which it will use if the user does not provide a value
to database when calling runTomTom(). The
following locations will be searched in order:
- The
meme_dboption, defined usingoptions(meme_db = "path/to/database.meme")
- The
meme_dboption can also be set to an R object, like a universalmotif list.
- The
MEME_DBenvironment variable defined in.Renviron
- The
MEME_DBvariable will only accept a path to a .meme file
NOTE: if an invalid location is found at one option,
runTomTom() will fall back to the next location if valid
(eg if the meme_db option is set to an invalid file, but
the MEME_DB environment variable is a valid file, the
MEME_DB path will be used.
Input types
To use TomTom on existing motifs, runTomTom() will
accept any motifs in universalmotif format. The
universalmotif package provides several utilities for
importing data from various sources.
runTomTom() can also take the output of
runDreme as input. This allows users to easily discover
denovo motifs, then match them to as set of known motifs. When run on
the output of runDreme, all runTomTom() output
columns will be appended to the runDreme() output
data.frame, so no information will be lost.
Output data
# This is a pre-build dataset packaged with memes
# that mirrors running:
# options(meme_db = system.file("inst/extdata/db/fly_factor_survey_id.meme", package = "memes"))
# example_motif <- create_motif("CCRAAAW")
# example_tomtom <- runTomTom(example_motif)
data("example_tomtom")When run using a universalmotif object as input,
runTomTom returns the following columns:
names(example_tomtom)
#> [1] "motif" "name" "altname"
#> [4] "family" "organism" "consensus"
#> [7] "alphabet" "strand" "icscore"
#> [10] "nsites" "bkgsites" "pval"
#> [13] "qval" "eval" "type"
#> [16] "bkg" "best_match_name" "best_match_altname"
#> [19] "best_db_name" "best_match_offset" "best_match_pval"
#> [22] "best_match_eval" "best_match_qval" "best_match_strand"
#> [25] "best_match_motif" "tomtom"Columns preappended with best_ indicate the data
corresponding to the best match to the motif listed in
name.
The tomtom column is a special column which contains a
nested data.frame of the rank-order list of TomTom hits for
the motif listed in name.
names(example_tomtom$tomtom[[1]])
#> [1] "match_name" "match_altname" "match_motif" "db_name"
#> [5] "match_offset" "match_pval" "match_eval" "match_qval"
#> [9] "match_strand"The best_match_motif column contains the universalmotif
representation of the best match motif.
The match_motif column of tomtom contains
the universalmotif format motif from the database corresponding to each
match in descending order.
The drop_best_match() function drops all the
best_match_* columns from the runTomTom()
output.
example_tomtom %>%
drop_best_match() %>%
names
#> [1] "motif" "name" "altname" "family" "organism" "consensus"
#> [7] "alphabet" "strand" "icscore" "nsites" "bkgsites" "pval"
#> [13] "qval" "eval" "type" "bkg" "tomtom"To unnest the tomtom data.frame column, use
tidyr::unnest(). The drop_best_match()
function can be useful when doing this to clean up the unnested
data.frame.
unnested <- example_tomtom %>%
drop_best_match() %>%
tidyr::unnest(tomtom)
names(unnested)
#> [1] "motif" "name" "altname" "family"
#> [5] "organism" "consensus" "alphabet" "strand"
#> [9] "icscore" "nsites" "bkgsites" "pval"
#> [13] "qval" "eval" "type" "bkg"
#> [17] "match_name" "match_altname" "match_motif" "db_name"
#> [21] "match_offset" "match_pval" "match_eval" "match_qval"
#> [25] "match_strand"To re-nest the tomtom results, use nest_tomtom() (Note:
that best_match_ columns will be automatically updated
based on the rank-order of the tomtom data.frame)
unnested %>%
nest_tomtom() %>%
names
#> [1] "name" "altname" "family"
#> [4] "organism" "consensus" "alphabet"
#> [7] "strand" "icscore" "nsites"
#> [10] "bkgsites" "pval" "qval"
#> [13] "eval" "type" "bkg"
#> [16] "best_match_name" "best_match_altname" "best_match_motif"
#> [19] "best_db_name" "best_match_offset" "best_match_pval"
#> [22] "best_match_eval" "best_match_qval" "best_match_strand"
#> [25] "motif" "tomtom"Manipulating the assigned best match
While TomTom can be useful for limiting the search-space for potential true motif matches, often times the default “best match” is not the correct assignment. Users should use their domain-specific knowledge in conjunction with the data returned by TomTom to make this judgement (see below for more details). memes provides a few convenience functions for reassigning these values.
First, the update_best_match() function will update the
values of the best_match* columns to reflect the values
stored in the first row of the tomtom data.frame entry.
This means that the rank of the tomtom data is
meaningful, and users should only manipulate it if intending to
create side-effects.
If the user can force motifs to contain a certain motif as their best
match using the force_best_match() function.
force_best_match() takes a named vector as input, where the
name corresponds to the input motif name, and the value
corresponds to a match_name found in the
tomtom list data (NOTE: this means that
users cannot force the best match to be a motif that TomTom did not
return as a potential match).
For example, below the example motif could match either “Eip93F_SANGER_10”, or “Lag1_Cell”.
example_tomtom$tomtom[[1]] %>% head(3)
#> match_name match_altname match_motif db_name
#> 1 Eip93F_SANGER_10 Eip93F <mot:Eip9..> flyFactorSurvey_cleaned
#> 2 Lag1_Cell schlank <mot:Lag1..> flyFactorSurvey_cleaned
#> 3 pho_SOLEXA_5 pho <mot:pho_..> flyFactorSurvey_cleaned
#> match_offset match_pval match_eval match_qval match_strand
#> 1 4 8.26e-07 0.000459 0.000919 +
#> 2 3 1.85e-03 1.030000 0.781000 +
#> 3 1 2.54e-03 1.410000 0.781000 +The current best match is listed as “Eip93F_SANGER_10”.
example_tomtom %>%
dplyr::select(name, best_match_name)
#> name best_match_name
#> 1 example_motif Eip93F_SANGER_10
#>
#> [Note: incomplete universalmotif_df object.]To force “example_motif” to have the best match as “Lag1_Cell”, do the following:
new_tomtom <- example_tomtom %>%
# multiple motifs can be updated at a time by passing additional name-value pairs.
force_best_match(c("example_motif" = "Lag1_Cell"))The best_match_* columns will be updated to reflect the
modifications.
Visualize data
view_tomtom_hits() can be used to compare the hits from
tomtom to each input motif. Hits are shown in descending order by rank.
By default, all hits are shown, or the user can pass an integer to
top_n to view the top number of motifs. This can be a
useful plot for determining which of the matches appear to be the “best”
hit.
For example, it appears that indeed “Eip93F_SANGER_10” is the best of the top 3 hits, as most of the matching sequences in the “Lag1_Cell” and “pho_SOLEXA_5” motifs correspond to low information-content regions of the matched motifs.
Importing previous data
importTomTomXML() can be used to import a
tomtom.xml file from a previous run on the MEME server or
on the commandline. Details for how to save data from the TomTom
webserver are below.
Saving data from TomTom Web Server
To download XML data from the MEME Server, right-click the TomTom XML
output link and “Save Target As” or “Save Link As” (see example image
below), and save as <filename>.xml. This file can be
read using importTomTomXML()
