-
Notifications
You must be signed in to change notification settings - Fork 27
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
Do not prefix chromosome names with "chr" per default #17
Comments
Thanks for the quick fix. I too use a reference genome that lacks 'chr' for chromosomes (GRCh37). |
Thanks for this as well. We will test this before merging. |
Hi @rbonneville, this is just a quick workaround for the problem, I do not think this should be merged. But it would certainly be a good idea to check for matching contig names for bam files, reference and bed file. |
Not sure what has changed in the meantime, but the most recent version does not crash anymore. Probably the @rbonneville should we close this? |
Hi, thanks for developing MANTIS. This problem still seems to exist. MANTIS prepends "chr" to the locus file. However, the reference FASTA file (used to produce the microsates) does not contain "chr" thus, it errors out:
|
Hi,
I am trying to run MANTIS and I think forcing chromosome names to start with "chr" is not a good idea.
My reference fasta, my bam files and the bed file I generated with RepeatFinder do not have them, so adding them crashes MANTIS.
Quick workaround if anybody has got the same problem
The text was updated successfully, but these errors were encountered: