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

Different output when the order of input genomes change #1

Open
areejalsheikh opened this issue Jun 7, 2017 · 0 comments
Open

Different output when the order of input genomes change #1

areejalsheikh opened this issue Jun 7, 2017 · 0 comments

Comments

@areejalsheikh
Copy link

areejalsheikh commented Jun 7, 2017

Hi Nabil,

I tried your tool here, great potential as there aren't any other tools out there to visualize and compare spacers between genomes. But I found a bug (I think).

In an attempt to identify spacers in a dataset, I had my input genomes ordered as they appear in the phylogeny (orderNum_strainName.fna). To do that, I had to sort the files being read by altering:

for name in sorted(files):
into
for name in sorted(files, key=lambda x: int(x.split('_')[0])):
It worked perfectly until I realised that the output before ordering is very different to after ordering. It could be an issue with the part of the script which parses pilercr report because I looked at the drawarray and found that for strain X, ordered vs. non-ordered has different number of spacers. It could also be an issue in the drawing code, because drawarray predicts for example 10 spacers for strain X, but the resulting svg shows only 2 spacers (in the case of ordered input).

Now I know this tool may not be supported anymore, but just a shot in the dark.

Thanks,
Areej

happykhan pushed a commit that referenced this issue Jun 20, 2017
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