Currently, clusterPWMs accepts only motifs from a file and requires an output file name (outfile argument).
What about extending clusterPWMs to:
- have multiple methods (along the line of
findMotifHits), e.g. one for motifs in a file, and another for motifs as a PFMatrixList
- set the default for
outfile = NULL and in that case, captures the homer output in a temporary file that will be deleted after parsing. Providing a value for outfile will still work as it does currently
- make use of the
-cpu flag to speed up computations
Finally, what about:
- porting
compareMotifs.pl to R (maybe C++) so that it will run fast enough to make it a default when creating a SummarizedExperiment - the information seems very useful and might be worth to have always available
Currently,
clusterPWMsaccepts only motifs from a file and requires an output file name (outfileargument).What about extending
clusterPWMsto:findMotifHits), e.g. one for motifs in a file, and another for motifs as aPFMatrixListoutfile = NULLand in that case, captures the homer output in a temporary file that will be deleted after parsing. Providing a value foroutfilewill still work as it does currently-cpuflag to speed up computationsFinally, what about:
compareMotifs.plto R (maybe C++) so that it will run fast enough to make it a default when creating aSummarizedExperiment- the information seems very useful and might be worth to have always available