-
Notifications
You must be signed in to change notification settings - Fork 3
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
about the test data #3
Comments
Hi, Hope it will help ! |
Thank you for your reply. It seems the
I was wondering is there any way to use one set of code to predict sequences less or longer than 200bp at the same time? Or i just need to separate them and run them twice. |
It seem that you are right, the code who subset a big sequence into smallers one should be responsible of this failure. For me, it's better to separate the two sets of sequences because it will not tell you the same thing. For sequences with less than 200bp, you want to know if you may have an active G4 or not. For big sequences, you want to "locate" or at least know if you will have a potential active G4 at some location, for insteance if you scan a full promoter region. |
Hi,
In the "promoters_seq_example.bed" file, what is the 4th and 5th column?
I assume 1st-3rd column is "chr", "start", "end" and the 6th is "strand"
I was trying to use my own bed file with only "chr, start, end, strand" to do the prediction but failed. Can you help me with this?
Thank you so much!!!
--KL
The text was updated successfully, but these errors were encountered: