schneebergerlab / syri

Synteny and Rearrangement Identifier
https://schneebergerlab.github.io/syri/
MIT License
323 stars 35 forks source link

chroder : No matching contigs for reference chromosome #114

Closed mnshgl0110 closed 2 years ago

mnshgl0110 commented 2 years ago

image image I tried to simulate pseudochromosomes using Chroder, but I couldn't find a match on any chromosome in the reference genome. At first, chromosome 1 didn't match, so I deleted chromosome 1 in the Coords file and ref.fas, but it kept dropping errors. Should I keep deleting chromosomes down?

Originally posted by @leyanKk in https://github.com/schneebergerlab/syri/issues/113#issuecomment-1001853966

mnshgl0110 commented 2 years ago

This is weird and is indeed unexpected behaviour. Could you please confirm that the two genomes are closely related, i.e. large parts of the genomes are indeed similar. For this, you can draw the mummerplot. If possible, can you share it as well?

leyanKk commented 2 years ago

They're not that far apart, but they belong to two different genera, mouse and zokor OUTFig I wonder if my mummer is running incorrectly

mnshgl0110 commented 2 years ago

Well, from this plot it is clear that the genomes, or at least the alignments, are not very similar. In case you are using nucmer4, then I would suggest that you try nucmer3 as in my experience that gives better results. You can also try minimap2 (version 2.17 works best for genome comparisons).

leyanKk commented 2 years ago

I use the nucmer3. I try minimap2

leyanKk commented 2 years ago

After using Minimap2, errors will still be reported, regardless of the Sam or BAM format image image

mnshgl0110 commented 2 years ago

It seems pysam is not installed correctly. Installing it should fix the issue.

leyanKk commented 2 years ago

image image Should my pysam be installed successfully before this

mnshgl0110 commented 2 years ago

Based on the discussion here: https://github.com/bactopia/bactopia/issues/12 upgrading pysam should fix it. Try upgrading to pysam v0.15.2

leyanKk commented 2 years ago

Pysam is upgraded to V0.15.2, or v0.15.3, depending on the upgrade method. The main reason is the Python version. The Syri Python version requires PYTHON 3.5 nohup.txt

mnshgl0110 commented 2 years ago

Have you tried installing v0.15.2? I have that installed with python 3.5.6, so I assume that it should work.

leyanKk commented 2 years ago

Installing this version also failed conda install -c conda-forge -c bioconda pysam=0.15.2 conda list |grep 'pysam' pysam 0.14.1 py35hae42fb6_1 bioconda nohup.txt

mnshgl0110 commented 2 years ago

My best probable guess is that there could be some issues with your working environment. I tried installing from fresh python3.5.6 and pysam0.15.2 and it worked.

conda create -n tpy3.5.6 python=3.5.6
conda activate tpy3.5.6
conda install -c bioconda pysam=0.15.2
(tpy3.5.6) 12:05 goel@pc-t7-130 goel:~$ conda list | grep python
python                    3.5.6                hc3d631a_0  
(tpy3.5.6) 12:06 goel@pc-t7-130 goel:~$ conda list | grep pysam
pysam                     0.15.2           py35h0380709_0    bioconda

The only thing I can suggest is to try with a new environment and maybe use the above commands.