You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: