-
Notifications
You must be signed in to change notification settings - Fork 38
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
empty output of chroder #182
Comments
Hi. Could you please share the chromosome IDs in the reference and the chroder_qry genome? If the number of chromosomes are same then this error should not happen. Also, please run syri with Additionally, if there is a chromosome level reference genome available, then you can also try using ragtag as that generates better pseudo-chromosomes then chroder. |
Thanks for your help. I made a denovo assembly for human genome chr6. The output from chroder output.qry.fasta includes
And the reference includes
the log file for syri I'll try ragtag! |
Does your reference has only |
Thanks for your help. The reference only includes chr6. My code is like below. GRCh38_chr6.fa includes only "chr6".
the output of chroder output.ref.fasta is empty. Confirmed input of syri has same chromosome.
Then run syri.
I also tried ragtag but it does not solve the situation. |
If I understand correctly, in the following command: |
Oh thank you! Is it usual to get empty output of reference fasta ("output.ref.fasta") from chroder if I use the chromosome level assembly as an reference? |
Hi, thank you for developing cool tool.
I know that there are several posts about this but I cannot solve my problem.
I am trying to use denovo assembly with scaffold level and reference genome, using pseudo genome assembly,
It runs but the output of the chroder "out_ref.fasta" was an empty file.
"output.qry.fasta" seems to be good including the same number of Chromosome as the reference genome.
Tried syri with "out_ref.fasta" or the reference fasta, it got the error "Chromosomes IDs do not match."
Thanks for your help.
The text was updated successfully, but these errors were encountered: