-
Notifications
You must be signed in to change notification settings - Fork 32
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
different TFs are discovered from different cistarget databases #526
Comments
Hi @gilgolan73 This is expected. The precomputed database uses ENCODE SCREEN regions. These regulatory regions are based on data from a variety of cell lines. These cell lines might not be too similar to your data. For this reason I would trust the results from the custom database more. Best, Seppe |
Hello @SeppeDeWinter , Thank you, |
Hi @SeppeDeWinter , An additional question- when I look at the TF_names.txt file, I can see that some TFs are missing (in both analyses). Is it because their motif does not appear in the database? If so, can I add their motif somehow? Thank you, |
Hi @gilgolan73
Yes, this in theory possible. This would involve generating a new database containing the union of SCREEN regions (https://screen.encodeproject.org/) and you consensus peak set.
This file is generated based on your motif enrichment results. If the TF does not appear it means that no motif for your TF of interest is enriched. It is of course possible that our collection does not contain any motif for your TF of interest. For this, please check wether your TF of interest occurs on the motif-to-TF annotation table: https://resources.aertslab.org/cistarget/motif2tf/ I hope I could help with this? Best, S |
Hi,
Thanks, |
Describe the bug
Hi, I am using scenicplus to find eRegulons in my sc-multiomic data (mouse).
I ran scenicplus twice, each time using a different cistarget databases:
When I looked at the results, I noticed that a lot of the TFs that were found using the custom databases, are missing in the precomputed databases-based analysis (and vice-versa). For example, for the custom-based databases , I found 100 TFs with regulons (among these, 51 were not found in the precomputed-based analysis). For the precomputed-based analysis, I found 94 TFs with regulons (among these, 46 were not found in the custom-based analysis).
These different sets of found TFs results in very different results (in terms of the eRegulons found, and the ability to perform in-silico perturbation assays for the TFs). Why do I get such different results? Is there a way to include more TFs in the custom-based analysis (which I guess is more accurate?) ?
Thank you,
Gil Golan
The text was updated successfully, but these errors were encountered: