finswimmer
finswimmer
:rocket: Can't wait for a new release :smiley:
Hello @DavidVujic, thanks a lot for your contribution and feature idea. In general I like the idea of "workspaces" and think it is a valuable thing. Currently we are working...
Hello @DavidVujic, I'm interested in the answers to @abn's questions as well. Especially why there are changes in `poetry-core` needed. Thanks a lot for your work. fin swimmer
We could ignore the `N818` error for now, to introduce `pep-naming` anyway.
Hello @nh13, unfortunately this doesn't work. The reads are trimmed to much. I guess the problem is: > Paired end reads that map to a given amplicon position are trimmed...
I was afraid that my description is confusing. So next try ;) I have paired end data. So `TrimPrimers` need to know where an amplicon starts and where it ends....
Which reference genome was used to create your initial vcf file? With this high number of ref mismatches I guess hg38/GRCh38 or NCBI36 was used and not hg19/GRCh37. fin swimmer
I'm not familiar with this. But could you show the header of the vcf file and the first 10 variants?
Hello again, these positions looks definitely wrong. Even it is possible to get the correct position ,based on the rs ids, I would recommend to find out what happens on...
Hello again, before choosing a dbSNP vcf file you must decide which reference genome you like to use. GRCh37 (hg19) or GRCh38 (hg38)? GRCh37 is outdated since Dec 2013. So...