created by KateN
on 2015-10-21
Default modules:
-list command.Each table has a few columns of data that will be the same across multiple evaluation modules. To avoid listing them multiple times, they will be specified here
Example Output *
eval for that row. By default, this is dbsnp, but you can specify additional comparison files using -comp, and name them using :. E.g. -comp:name \path\to\file.vcf where name is the name you wish to specify for the CompRod column and \path\to\file.vcf is your comparison file. If left unnamed, these additional comparison files will default to "comp" in the CompRod column.eval files. They can be named using the : notation as above. When unnamed, they will default to "eval" in the EvalRod column.-knownName with the new comparison file you have passed in.*Output from a rare variant association study with >1500 whole genome sequenced samples
Example Output *
eval fileeval considered to be novel in comparison to dbsnp (same as novel row of nEvalVariants column)eval that match the location of a variant in the comparison file (same as known row of nEvalVariants)eval that exactly match the genotype present in the comparison file*Output from a rare variant association study with >1500 whole genome sequenced samples
Example Output *
eval fileeval that matched the reference fileeval that did not match the reference file*Output from a rare variant association study with >1500 whole genome sequenced samples
Example Output *
-gold parameter)*Output from a rare variant association study with >1500 whole genome sequenced samples
Example Output *
eval (A↔G or T↔C)eval (A↔T or G↔C or A↔C or G↔T)*Output from a rare variant association study with >1500 whole genome sequenced samples
Example Output *
eval was found in the known comparison file (applies only to multiallelic sites)eval were also found in the known comparison file (applies only to multiallelic sites)*Output from a rare variant association study with >1500 whole genome sequenced samples
Updated on 2017-09-30
From auraf on 2017-09-25
Hi, does the nTv metric calculated by the TiTvVariantEvaluator consider also N of transversions A/C and G/T?
From Sheila on 2017-09-28
@auraf
HI,
I don’t think it does, but let me check with the team and get back to you.
-Sheila
From Geraldine_VdAuwera on 2017-09-30
It certainly should — looks like an error in the doc, sorry about that. (fixed it)
