-
Notifications
You must be signed in to change notification settings - Fork 106
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
Motif presence at genomic location #28
Comments
Yea this has been on my radar for awhile. I suppose I've hesitated because tomtom is so often unable to identify what proteins are most relevant to the motif. I'll post here if I code up a solution. |
Yeah, but I can definitely say that this is something that is absolutely crucial for this to catch real traction, need to connect to previous people's stuff. I started working on this and it should just be feeding the model the seqeunce of a specific location right? |
Just to make sure that we're on the same page- you want to annotate the motifs that pop up with loss scores in the saturated mutagenesis heat maps, right? For example, the sequence in Figure 5 in the paper would be annotated as CTCF. That's how I've been thinking about it. Obviously, there are already tools for annotating sequences with motifs, like Tomtom. Basset can help suggest which motifs are actually relevant. So maybe the easiest approach would be to add an option to basset_sat.py to query the sequence for significant motifs with Tomtom, but filter the list for only those that overlap a nucleotide with a loss score above some threshold. |
Yeah that's exactly right (CTCF in figure 5). |
In my use case of Basset i've bumped into something that would be super useful. This may already be doable (but i'm not sure how): a method to take in a genomic region, a target cell type and output what motifs are associated with that region in that cell type using Tomtom. I know that right now you can feed the entire model and sequences but i'm not sure how to hook all that together.
The text was updated successfully, but these errors were encountered: