Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions about GimmeMotifs output #280

Open
paumarc opened this issue Oct 7, 2022 · 1 comment
Open

Questions about GimmeMotifs output #280

paumarc opened this issue Oct 7, 2022 · 1 comment

Comments

@paumarc
Copy link

paumarc commented Oct 7, 2022

I have been using gimmemotifs to analize data comming from chipseq experiment, it worked well, but now is hard for me to understand the outputs and i miss some information at the documentation. Let me explain myself:

at the results i have four html files : gimme.clustereds.html, gimme.denovo.html, gimme.motifs.html, gimme.motifs.redundant.html

that i think, but not for sure, that contains:

gimme.denovo.html : motives found that are not present at any datbase
gimme.motifs.redundant.html : All motives found at the sample, including denovo and known motif
gimme.clustereds.html here i think you try to "cluster" the motives
gimme.motifs.html : Final results with the most relevant information found

is that rigth?

the point here is that i don't find how to how to follow the the process, should I find the names from gimme.clustereds.html in gimme.motifs.redundant.html ?

how do you go from them redundant list to the motif list? and what should i take as a final result

thanks

@simonvh
Copy link
Member

simonvh commented Oct 14, 2022

Hi @paumarc, indeed, the documentation is not complete.
All in all, you are correct in your description of the files. The most important file is gimme.motifs.html. This provides an overview of the most important motifs, while trying to take care of motif redundancy. This includes (by default) both known as well as de novo motifs. However, this process of removing redundancy is not always perfect, so sometimes it's good to look at the gimme.motifs.redundant.html file to see if there's anything notable that's missing from the final output. In addition, if you want to compare between different runs, you have to use the gimme.motifs.redundant.html, as the grouping in gimme.motifs.html is run- and result-dependent.

The file gimme.denovo.html gives a more detailed overview of the quality of the de novo motifs. These motifs are clusered, as gimme runs a whole load of motif prediction tools with various settings. These are the ones that are present in gimme.clustereds.html. I pretty much never look at this output, as it contains many, many similar motifs.

Hope this helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants