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

Can we specify file names of input assemblies? #155

Open
MostafaYA opened this issue Jan 10, 2023 · 1 comment
Open

Can we specify file names of input assemblies? #155

MostafaYA opened this issue Jan 10, 2023 · 1 comment
Assignees

Comments

@MostafaYA
Copy link

This is not really an issue, but may be a feature request. I see that chewbbaca allele call takes as input the directory containing the assemblies / file of paths to the assemblies.
Chewbbaca then predicts the names of the fasta files as a prefix before the first dot "." - in a few cases (such as different NCBI assembly versions) the names may contain dots.
I try to use chewbbaca as part of a pipeline, and this behavior leads to inconsistencies in the samples' name.

As a solution, instead of passing a file with paths, can we pass a file with two columns, column 1 for sample name and column 2 for the file's path?
e.g.
#Isolate_name path
Sample.1 /path/2/sample.1.fasta
Sample.2 /path/2/sample.2.fasta

Thanks

@rfm-targa rfm-targa self-assigned this Feb 28, 2023
@rfm-targa
Copy link
Contributor

Hello @MostafaYA,

Sorry for the delayed response. We can implement that for the AlleleCall module. I'll try to add it to one of the following versions (I don't know if it'll be possible in the next version, v3.2.0, but it should be included in the version after that).
Thanks for suggesting that feature. It'll help us improve chewBBACA.
I'll let you know when it's been implemented.

Rafael

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