-
Notifications
You must be signed in to change notification settings - Fork 1
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
Issue: build_database with prior #8
Comments
Hello @June3billion – I have pushed a fix for this issue. I had erroneously left in a hard-corded path during testing. Please pull the latest version, test, and let me know if this resolves the issue. |
Thank you for the kind response!
|
I think this issue has to do with a difference in how index columns are handled in newer versions of the pandas module. I have slightly modified the function that reads priors to hopefully address this. Could you once again pull the latest version and test? |
Thank you! The latest version worked well. but, I found the input MAF data (Indelible_db_10k.bed) was not reflected in the final output. The MAF column of the output file from the example data has 1. I assume that frequencies came from the input data itself... can I restrict the MAF information to the input database? |
Yes, I can see why one could want the MAF information from the priors. I see two use-cases here:
Let me see about adding an option flag to retain the MAF of the prior database. |
Thank you so much! I really appreciate it. |
I have pushed a new build which includes a flag (--old-maf) for the database / complete commands. Could you let me know if it works for you? Thanks! |
It worked! Thank you! |
Good to hear. I am going to close this issue. Please reopen if you encounter any other problems. |
Dear indelible guys.
I encountered the following error
with the following command
How can I use /NAS/data/etc/indelible/data/Indelible_db_10k.bed for MAF annotation?
The text was updated successfully, but these errors were encountered: