From 6ac8d9bd4785c5d41a48a872b40b1e0347de80e7 Mon Sep 17 00:00:00 2001 From: Daniel Cameron Date: Wed, 28 Feb 2024 00:59:00 +1100 Subject: [PATCH] #699 Fix typos --- VCFv4.4.tex | 8 ++++---- VCFv4.5.draft.tex | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/VCFv4.4.tex b/VCFv4.4.tex index 5e62456bd..9aca34c9d 100644 --- a/VCFv4.4.tex +++ b/VCFv4.4.tex @@ -607,12 +607,12 @@ \subsubsection{Genotype fields} \end{tabular} \item PSO (List of integers): List of phase set ordinals. - For each phase-set name, defines the order in which variants are encountered when traversing a derivate chromosome. + For each phase-set name, defines the order in which variants are encountered when traversing a derivative chromosome. The missing value '$.$' should be used when the corresponding PSO value is missing. For each phase-set name, PSO should be defined if any allele with that phase-set name on any record is symbolic structural variant or in breakpoint notation. Variants in breakpoint notation must have the same PSL and PSO on both records. - Without explicitly specifying the derivate chromosome traversal order, multiple derivate chromosome reconstructions are possible. + Without explicitly specifying the derivative chromosome traversal order, multiple derivative chromosome reconstructions are possible. Take for example this tandem duplication in a triploid organism with SNVs (ID/QUAL/FILTER columns removed for clarity): \vspace{0.5em} @@ -829,7 +829,7 @@ \section{INFO keys used for structural variants} \item BFB - breakage fusion bridge \item DOUBLEMINUTE - Double minute \end{itemize} -The sematics of other $EVENTTYPE$ values is implementation-defined. +The semantics of other $EVENTTYPE$ values is implementation-defined. The use of $EVENT$ is not restricted to structural variation and can also be used to associate non-symbolic alleles. Such linking is useful for scenarios such as kataegis or when there is variant position ambiguity in segmentally duplicated regions. @@ -2555,7 +2555,7 @@ \subsection{Changes between VCFv4.4 and VCFv4.3} \item Added tandem repeat support ($<$CNV:TR$>$, RN, RUS, RUL, RB, CIRB, RUC, CIRUC, RUB) \item Redefined INFO CN as allele-specific copy number and FORMAT CN as total copy number. \item Redefined INFO and FORMAT CN to support non-integer copy numbers. -\item Added support for phasing and derivate chromosome reconstruction in the presence of SVs (PSL, PSO, PSQ) +\item Added support for phasing and derivative chromosome reconstruction in the presence of SVs (PSL, PSO, PSQ) \item Added SVCLAIM to disambiguate copy number based $<$DEL$>$ and $<$DUP$>$ variants from breakpoint based ones. \item Conceptually separated variant detection and interpretation. \item Added EVENTTYPE/EVENT to enable the multiple records encoding complex genomic rearrangements to be grouped together. diff --git a/VCFv4.5.draft.tex b/VCFv4.5.draft.tex index b70b33fa0..a4fd4c519 100644 --- a/VCFv4.5.draft.tex +++ b/VCFv4.5.draft.tex @@ -607,12 +607,12 @@ \subsubsection{Genotype fields} \end{tabular} \item PSO (List of integers): List of phase set ordinals. - For each phase-set name, defines the order in which variants are encountered when traversing a derivate chromosome. + For each phase-set name, defines the order in which variants are encountered when traversing a derivative chromosome. The missing value '$.$' should be used when the corresponding PSO value is missing. For each phase-set name, PSO should be defined if any allele with that phase-set name on any record is symbolic structural variant or in breakpoint notation. Variants in breakpoint notation must have the same PSL and PSO on both records. - Without explicitly specifying the derivate chromosome traversal order, multiple derivate chromosome reconstructions are possible. + Without explicitly specifying the derivative chromosome traversal order, multiple derivative chromosome reconstructions are possible. Take for example this tandem duplication in a triploid organism with SNVs (ID/QUAL/FILTER columns removed for clarity): \vspace{0.5em} @@ -829,7 +829,7 @@ \section{INFO keys used for structural variants} \item BFB - breakage fusion bridge \item DOUBLEMINUTE - Double minute \end{itemize} -The sematics of other $EVENTTYPE$ values is implementation-defined. +The semantics of other $EVENTTYPE$ values is implementation-defined. The use of $EVENT$ is not restricted to structural variation and can also be used to associate non-symbolic alleles. Such linking is useful for scenarios such as kataegis or when there is variant position ambiguity in segmentally duplicated regions. @@ -2560,7 +2560,7 @@ \subsection{Changes between VCFv4.4 and VCFv4.3} \item Added tandem repeat support ($<$CNV:TR$>$, RN, RUS, RUL, RB, CIRB, RUC, CIRUC, RUB) \item Redefined INFO CN as allele-specific copy number and FORMAT CN as total copy number. \item Redefined INFO and FORMAT CN to support non-integer copy numbers. -\item Added support for phasing and derivate chromosome reconstruction in the presence of SVs (PSL, PSO, PSQ) +\item Added support for phasing and derivative chromosome reconstruction in the presence of SVs (PSL, PSO, PSQ) \item Added SVCLAIM to disambiguate copy number based $<$DEL$>$ and $<$DUP$>$ variants from breakpoint based ones. \item Conceptually separated variant detection and interpretation. \item Added EVENTTYPE/EVENT to enable the multiple records encoding complex genomic rearrangements to be grouped together.