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

Issues with chewBBACA in Windows #74

Open
erikalmecdc opened this issue Dec 10, 2020 · 1 comment
Open

Issues with chewBBACA in Windows #74

erikalmecdc opened this issue Dec 10, 2020 · 1 comment

Comments

@erikalmecdc
Copy link

chewBBACA seems to have some incompatibilities with Windows 10/Windows server.

  1. The check for blastp fails, it works if --b flag is specified and 'blastp' is changed to 'blastp.exe' in the code. The makeblastdb commands does not use the --b path, so blast must also be on the path. This is a bit of an inconsistency with the --b flag in general.

  2. Blast db creation fails. This is a bug in BLAST that is mitigated with setting BLASTDB_LMDB_MAP_SIZE=1000000 in the Windows env, but could also be set in chewBBACA.

  3. Piping of sequences to BLAST fails in windows because windows echo does not work like linux echo. Can be mitigated with temporary files or by creating the stream to pipe without using system echo.

  4. When performing an A/B-test with Mirko Rossi, we got quite different results using the same schema and genome (Linux vs Windows), especially the number of paralogue loci. I can provide more details if needed. I have currently no explanation for this, probably some more incompatibility with windows that does not cause a direct crash but rather incorrect results.

@ramirma
Copy link
Member

ramirma commented Dec 11, 2020

@erikalmecdc to tell the truth we had not tested chewBBACA in Windows so thank you for the report.
@rfm-targa will look into this and we will certainly put working on a Windows compatible version in the roadmap. For now could you provide more information on each of the points:

  1. Could you provide more specific information on what you changed in the code for it to work?

  2. Same here.

  3. Do you have a traceback of the errors so that we could look in more detail at what could be happening?

  4. Having more information on this would be great. If you prefer to share the information through email you can use the address imm-bioinfo(at)medicina.ulisboa.pt

Thank you.

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

No branches or pull requests

3 participants