-
Notifications
You must be signed in to change notification settings - Fork 22
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
Custom databases #34
Comments
Hi, Thanks, |
I sent you a link to a tarball in google drive |
Hi again, and sorry for the late reply. My first guess is that this could have something to do with the igblast auxiliary file. It looks like you did not provide the auxiliary file when running bracer build (this is not required as of now, but since bracer has been more and more dependent on CDR3 detection this file and not custom scripts, it probably should be at least for species where such data is available. Sorry about that!). Could you please try to copy the auxiliary file from the bracer repository into the corresponding directory in your custom reference directory and let me know if this solves the problem? If so, I will make it more clear in the documentation that the --igblast_aux <igblast_auxiliary_file> argument is highly recommended to use. |
It helped with the kappas, but not the heavy chain (for this one test cell):
|
I'm trying to use bracer with a custom gene database (which is actually a superset of the standard IMGT database). After the documentation issues in #31, I did include a database and created a gapped alignment that conforms to the IMGT standard, which at least lets me run
bracer assemble
without a crash. However, my heavy chains are getting lost somewhere in the mix. I can detect them with the standard Human database. Moreover, when I look at the output from the individual steps, I can see roughly the same hits from the Bowtie alignment, Trinity assembly, and constant region BLAST. However, the heavy chains are failing to "pass" the IgBLAST step. It looks like it's having trouble detecting CDR3 and J, so maybe this is a problem with the way I built the combinatorial_recombinomes?The text was updated successfully, but these errors were encountered: