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

Unexpected output #45

Open
jjoets opened this issue Oct 21, 2022 · 1 comment
Open

Unexpected output #45

jjoets opened this issue Oct 21, 2022 · 1 comment

Comments

@jjoets
Copy link

jjoets commented Oct 21, 2022

Hi,

Thanks a lot for this huge tool. I had a very good experience with it a couple year ago (version 1). I now have other runs to do and I updated to the last version. I was a bit surprised by the outpout : instead of getting one lcb per genome for a unique block ID, I get several ones. To try to understand what was wrong, I ran again my previous analysis with the same setting but instead of getting on average one block coordinate by genome in the blocks_coords.gff I now get many.

Is this change expected between V1 and current version ? Is this linked to the -a option ? What would be you advices ?

Thanks a lot,

Johann

@iminkin
Copy link
Collaborator

iminkin commented Oct 27, 2022

Hi,

I am glad that you found SibeliaZ helpful. This is a bit tricky question. Representation of whole-genome alignment is inherently ambiguous. For example, a single alignment block can be chopped into multiple consecutive blocks and still represent an equivalent alignment. Also, the newer version could generate more blocks due to improvements in sensitivity, which would also result in fragmenting the blocks, which I suspect is the case. Does the coverage change of the block change significantly between the runs of different versions?

Regarding to -a option, it depends on how many genomes are there in the dataset, as well as their repeat content. What kind of genomes (and how many) are you trying to align?

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

2 participants