Skip to content
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

Why do I still get misassembles thought salsa didn't find any? #156

Open
zmz1988 opened this issue Jan 17, 2022 · 1 comment
Open

Why do I still get misassembles thought salsa didn't find any? #156

zmz1988 opened this issue Jan 17, 2022 · 1 comment

Comments

@zmz1988
Copy link

zmz1988 commented Jan 17, 2022

Dear developers,

Thanks a lot for writing this super easy-to-use tool!

I'm new in doing scaffolding with Hi-C data and also in using SALSA. I recently ran salsa with our Omni-C data for scaffolding. Our assembly is already quite good (NG50>15 MB), and we are hoping to confirm/solve some of the centromere and telomere part of the genome by using Hi-C data.

After I ran SALSA with python /miniconda3/envs/salsa/bin/run_pipeline.py -a Sample.fasta -l Sample.fasta.fai -b Sample_mapped.PT.alignment.bed -e DNASE -o scaffolds -m yes, I got empty misaim_2.DONE, misaim_3.DONE and misasm_3.log. So I think no misassembles were found in our assembly? Do I interpret it correctly?

However, in the contact map generated I saw many misassembled signals (mostly in centromere and telomere regions), and also some contigs that could be joined into the chromosomes.

So I would like to know whether I had done something wrong in running SALSA that resulted in unsolved misassembled regions? If not, how can I improve my results?

Thanks a lot in advance!

@zmz1988
Copy link
Author

zmz1988 commented Jan 17, 2022

Contact map here
Screenshot 2022-01-17 at 10 37 17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant