Ryangguk Kim

Hi @kokyriakidis, OpenCRAVAT expects VCF-format input files to follow the VCF format standard which is that all variants are written from the + strand's viewpoint. With that said, do you...

Thanks for the information. Yes, at this moment, all variants in a VCF-format file should be based on the + strand. I can think of adding a "correction" feature to...

@kokyriakidis Yes. Thanks for letting us know about the database. We'll take a look and keep you updated. Regarding the VCF format issue, in that case, automatic conversion may be...

@ctokheim Thanks for letting us know Collin. It turns out that Gencode V33 itself has wrong UniProt mappings, which were directly transferred to OpenCRAVAT's mapper. As I check the latest...

Hi, sure we'll take a look and get back to you.

@kokyriakidis Hi, it seems that those jobs do not exist. Was the problem solved? If not, if an example file is available I can examine.

@kokyriakidis Thanks. The server should handle "C1-1" without a problem by now (vcf-converter 2.1.4 fixes the problem). Please let me know if you still encounter the issue.

@cariaso Sorry, I deleted my comments because I was afraid of possibly giving confusing information and wanted to write a clearer one again. I'll write below. OpenCRAVAT normalizes input variants...

There should be 2 entries in the variant table. The following is the test with which I saw two entries. The input and the tsv report file are attached. ```...

I see the following from an oc run with your two octopus VCF format variants: ``` 1 chr7 74053321 TG - 2 chr7 74053321 TGTG - ``` There are a...