-
Notifications
You must be signed in to change notification settings - Fork 151
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
6 Motif analysis does not work (bug) #40
Comments
I modified the script 'find_motifs.py', and now it runs without error. See below. I also edited the example dev.tsv file so the header is tab-seperated not space-seperated. However, no motifs are output for the provided example data/commands.
|
FYI - After editing the script as per above,the motif finding procedure worked on our data and identified motifs. GREAT! Thank you very much for the awesome tool! However, if I set the --max_seq_length to 56 instead of 64 during the (4) prediction and (5) visualization steps, then the following eror is thrown:
|
Hi, After I modified it according to your code. pos_seqs: 9674; neg_seqs: 9709 |
@lhy0322 For me, there were also no files saved when using the provided example data. When I used my own data, motif files were saved. |
If you receive the error: AttributeError: Not an Aho-Corasick automaton yet: call add_word to add some keys and call make_automaton to convert the trie to an automaton. I think it means: "No Motifs found , no high-attention regions" for your data. |
Hi @Joseph-Vineland and @lhy0322, Sorry about the bugs and delay in my response and thank you very much for reporting. We have uploaded new test data and performed general bug fixes on different modules of this framework. Please try again with the updated code and let me know if any bug still happens. Thanks, |
Going to close this one for now. Feel free to reopen if there's any additional questions. |
Hello, Step 6 Motif finding does not work, even with the provided example data and commands.
Motif analyis converts patterns detected by DNABERT to actionable biological insights. I really hope this bug can be fixed, becasue DNABERT is working out great so far, I don’t want to be stopped at the crucial last step. @Zhihan1996
The problem has also been identified as a bug here: #2
(Fixing the issue with the header lines only results in other error messages, and fixing those errors causes even more confusing error messages.)
The text was updated successfully, but these errors were encountered: