-
Notifications
You must be signed in to change notification settings - Fork 11
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
using custom scheme no sequence type is assigned #95
Comments
Hi @stefcardinale thanks for using MentaLiST and reporting this issue. Which version of MentaLiST are you using? Could you post the commands that you used to build your db and call alleles? |
Hello, thanks for writing. I have installed Mentalist last week through manual installation following the instructions (installing Julia dependencies first). This created the following files: Then I used the command to call alleles: The process completes fine, but I always get ST=0, is it normal? I would expect the tool identifies the closest sequence type from the scheme profiles. Thanks! |
Could you post your |
Hi @stefcardinale , Mentalist will only assign an ST if it matches exactly the profile, it will not try to find the closest ST otherwise. Are you getting ST=0 for a genotype that matches the profile? |
Is there no way to make a call based on the closest allele match at some threshold? |
Hello, I have built a custom scheme based on a list of fasta files of loci using the 'build_db' function, I have also given the profile with Sequence Types and their allelic profiles using the -p option (file is a .txt file).
However, when I use the scheme for calling alleles on SRR Illumina reads, the process completes fine but no Sequence Type from the profile is assigned. How can I use the scheme profile information? is it lost somewhere? I noticed that the first function creates a xx.db.profile file with the appropriate information, but apparently it is not used? Thanks for the help!
The text was updated successfully, but these errors were encountered: