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

ivariant filtering problem using 'tsv file' generated by 'ivar variant' command. #425

Closed
Moslemecoh opened this issue Apr 23, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@Moslemecoh
Copy link

Description of the bug

For the variant filter, the command is given as below:
ivar filtervariants -t 0.5 -p P.test.filtered P1_S1.tsv P2_S2.tsv P3_S3.tsv

But, unfortunately getting the following error message:
Header format of P1_S1.tsv did not match! Please use files generated using "ivar variants" command.
Header format of P2_S2.tsv did not match! Please use files generated using "ivar variants" command.
Header format of P3_S3.tsv did not match! Please use files generated using "ivar variants" command.

Even the header formats are unique among the files. txt files have also been used to filter but encountered the same error message. What could be the problem and solution to resolve it? Thanks in advance.

Command used and terminal output

No response

Relevant files

P1_S1.csv
P2_S2.csv
P3_S3.csv

System information

No response

@Moslemecoh Moslemecoh added the bug Something isn't working label Apr 23, 2024
@mgaucoin
Copy link

mgaucoin commented May 1, 2024

I have the exact same issue. I hope someone can help. I changed the tsv format to csv so that I could upload the files here (tsv is not a supported file type).

ivar filtervariants -p $1_variants $1_A_variants.tsv $1_B_variants.tsv
1_A_variants.csv
1_B_variants.csv

Header format of 1_A_variants.tsv did not match! Please use files generated using "ivar variants" command.
Header format of 1_B_variants.tsv did not match! Please use files generated using "ivar variants" command.

@Alex-Vasile
Copy link

See andersen-lab/ivar#178

@svarona
Copy link
Contributor

svarona commented May 9, 2024

@Alex-Vasile @mgaucoin @Moslemecoh can we close this issue as it seems to be an ivar issue and not a viralrecon issue?

@Alex-Vasile
Copy link

can we close this issue as it seems to be an ivar issue and not a viralrecon issue?

That depends on your philosophy of how to handle this. I could see this either being closed and wait for iVar to get fixed and let the users handle the problem. Or this package handed the problem and a workaround to be implemented into that pipeline until iVar gets fixed.

@svarona
Copy link
Contributor

svarona commented May 9, 2024

viralrecon generates the .vcf file of that .tsv that is correctly formatted. As viralrecon does not use ivar filtervariants, I think it is something that iVar should get fixed, and viralrecon users might find a way to do that filter with the .vcf using bcftools or something like that.

@Moslemecoh
Copy link
Author

@svarona thank you for your advice and apologies for posting on a different site. Please close this issue.

@svarona
Copy link
Contributor

svarona commented May 10, 2024

There is nothing to apology for! Hope this helps others to get to the problem! 😄

@svarona svarona closed this as completed May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants