Why Diagnose Samples Before Association Analysis?
Variant-level filters assess whether individual structural-variant calls are credible. They do not establish that every sample was measured equally well. A sample with low callability may have many missing calls, while a sample processed in a different batch may show an unusual number of events or an atypical distribution of copy-number states. If these patterns align with phenotype or study group, downstream comparisons can reflect technical differences as well as biological variation.
Sample-level diagnostics are summaries for detecting patterns that merit investigation. They are not, by themselves, proof that a sample is erroneous or that an observed event is biological. The comparison must use an appropriate denominator, and interpretation should account for assay design, callable regions, ploidy, and batch composition.
Call Rate: The Denominator Matters
For a sample, call rate is the fraction of eligible sample–locus observations for which a call was successfully made. A locus belongs in the denominator only if it was intended to be assessed and was eligible for calling in that sample. Thus, the denominator should reflect the assay’s targets and the sample’s callable opportunities, rather than an arbitrary count of all possible genomic positions.
The definition of “locus” must match the analysis. It might refer to targeted intervals, a harmonized set of candidate regions, or another prespecified unit. If two samples have different target sets, dividing both by the same nominal number of loci can make their rates incomparable. Likewise, a locus that is not callable because of known assay limitations should not be treated as a failed call without stating that convention.
Call rate is a completeness measure, not an accuracy measure. A sample can have a high call rate and still have inaccurate calls. A low rate can reflect poor DNA quality, coverage, mapping difficulty, or an overly broad denominator. Inspect call rate alongside the technical records and the variant-level quality criteria already applied.
Worked Example: Comparing Sample Call Rates
Suppose a hypothetical analysis uses 50 eligible regions for each of two samples. Sample A has resolved calls in 48 regions, while Sample B has resolved calls in 42.
Sample A: \(48/50=0.960\), so its call rate is 96.0%.
Sample B: \(42/50=0.840\), so its call rate is 84.0%.
The absolute difference is \(0.960-0.840=0.120\), or 12.0 percentage points. Because the eligible-region denominator is the same, the rates are directly comparable under this setup. Sample B merits review for missingness and technical quality, but this calculation alone does not establish why its call rate is lower or whether it must be excluded.
Event Counts and Callable Opportunity
A total event count is the number of retained structural-variant events attributed to a sample under a specified event representation and filtering procedure. State exactly what is counted: for example, whether the count includes deletions and duplications, how multiallelic or overlapping calls are represented, and whether only calls passing the chosen variant-level filters are included. The count is useful for identifying unusually high or low values, but it is not automatically a measure of biological burden.
Observed event counts can differ because samples have different amounts of callable sequence or different detection sensitivity. When possible, compare samples assessed over the same regions and with comparable callability. If callable sequence differs, report it and consider an event rate per callable unit, such as events per callable megabase, only when the callable bases are defined consistently and the rate is scientifically interpretable.
An event-rate adjustment does not solve every comparability problem. If event detection sensitivity differs between samples, or if callable regions differ in their propensity to contain events, a simple rate may still be misleading. It is often preferable to restrict the comparison to a common callable region and inspect call rate and event count together.
Worked Example: Flagging an Unusually High Event Count
Consider eight hypothetical samples processed with the same event filters and each with 20 callable megabases. Their retained event counts are 0, 1, 1, 2, 2, 3, 3, and 8.
The median count is the average of the fourth and fifth sorted values: \((2+2)/2=2\) events. Using the median-of-halves convention, the lower half is 0, 1, 1, 2, so \(Q_1=(1+1)/2=1\). The upper half is 2, 3, 3, 8, so \(Q_3=(3+3)/2=3\). Thus, the interquartile range is \(IQR=Q_3-Q_1=3-1=2\).
The usual upper Tukey fence is \(Q_3+1.5(IQR)=3+1.5(2)=6\) events. The sample with 8 events lies above this descriptive fence and is flagged for review. Since each sample has 20 callable megabases, the corresponding rates are \(8/20=0.400\) events per megabase for that sample and \(2/20=0.100\) events per megabase at the cohort median count. This contrast is a diagnostic signal, not evidence by itself of either a technical artifact or a true excess of events.
Copy-Number Distributions Across Callable Regions
A sample’s copy-number distribution summarizes how often each copy-number state is observed across the regions assessed for that sample. Earlier material introduced copy-number states and dosage coding; here the purpose is quality review, not modeling an association. Summaries should be restricted to regions where a copy-number call was eligible and callable, and should respect the expected baseline ploidy. For example, interpreting a state relative to diploidy requires care for sex chromosomes or other regions where the expected baseline differs.
For sample \(i\), let \(n_{ic}\) be the number of callable regions assigned copy-number state \(c\), and let \(N_i\) be the total number of callable regions summarized. The within-sample proportion in state \(c\) is:
These proportions make samples with different numbers of callable regions easier to compare, provided the regions represent comparable opportunities. A copy-number histogram can reveal a sample with an unexpected concentration of apparent losses or gains, a distorted baseline peak, or an unusual fraction of unresolved states. Such a pattern can result from technical issues, but can also reflect real sample composition or region selection. Review the underlying calls and denominators before interpreting it.
Worked Example: Comparing Copy-Number Profiles by Batch
Suppose two hypothetical sequencing batches each contribute 1,000 callable region observations to a summary. Batch A has 20 observations in state 0, 180 in state 1, 780 in state 2, and 20 in state 3 or higher. Batch B has 60, 240, 650, and 50 observations in those same categories.
For Batch A, the proportions are \(20/1000=2.0\%\), \(180/1000=18.0\%\), \(780/1000=78.0\%\), and \(20/1000=2.0\%\), respectively. For Batch B, they are \(60/1000=6.0\%\), \(240/1000=24.0\%\), \(650/1000=65.0\%\), and \(50/1000=5.0\%\).
If states 0, 1, and 3 or higher are grouped as non-state-2 for this diagnostic, Batch A has \((20+180+20)/1000=0.220\), or 22.0%, in that group. Batch B has \((60+240+50)/1000=0.350\), or 35.0%. The 13.0-percentage-point difference is a reason to examine batch-specific call quality, region composition, and sample characteristics. It is not enough to conclude that Batch B has poorer calls: the batches must be compared over equivalent regions and with relevant ploidy and cohort composition considered.
Batch-Stratified Summaries
A cohort-wide summary can conceal technical heterogeneity. At minimum, inspect call rate, event count, and copy-number summaries by sequencing or calling batch, alongside the corresponding sample-level distributions. A batch summary may use a median and range or interquartile range for continuous diagnostics, and proportions for copy-number categories. Report the number of samples and the denominator behind each summary; otherwise, a difference can be difficult to assess.
Stratification helps distinguish an isolated sample outlier from a batch-wide shift. If many samples in one batch have lower call rates or higher event counts, a pipeline, reagent, sequencing, or target-design difference becomes a plausible explanation to investigate. If only one sample is unusual, sample-specific quality or biology may be more relevant. Neither pattern proves a cause.
Batch and phenotype can be associated by design or chance. If nearly all cases are in one batch and nearly all controls in another, a technical difference may be entangled with the group comparison. The diagnostic summaries can expose this risk, but they do not correct it. Preserve batch labels, document the imbalance, and resolve comparability before drawing association conclusions.
A Practical Diagnostic Sequence
Specify what counts as an event, which loci or intervals contribute to call rate, and how callable sequence is determined. Use the same definitions across samples wherever possible.
Calculate call rate, retained event count, and proportions of copy-number states among callable regions. Keep the denominators visible.
Use distributions and robust summaries, such as medians and interquartile ranges, to identify unusual samples without letting a few extreme values define the comparison.
Check technical records, region-level callability, and the underlying calls. Document any exclusions or corrections and consider whether the flagged pattern aligns with phenotype or study group.
Common Mistakes and Interpretation
- Using incomparable denominators. A call rate based on all nominal targets may unfairly penalize samples for regions that were not eligible or callable. Define the denominator and compare like with like.
- Treating a high event count as proof of poor quality. A high count can be biological, technical, or both. Check callability, filters, and batch patterns before deciding.
- Comparing raw copy-number counts across unequal numbers of regions. Use proportions among callable regions and confirm that the region sets are comparable.
- Assuming batch differences are harmless because calls passed variant-level filters. Variant-level filters do not guarantee equivalent sample-level sensitivity. Review sample and batch summaries as well.
- Automatically removing every flagged sample. A descriptive fence or unusual histogram is a prompt for investigation, not a universal exclusion threshold. Use prespecified criteria and retain an audit trail.
Check Your Understanding
Use the definitions and diagnostic logic above to answer the following.
- A sample has 90 resolved calls among 100 eligible regions. What is its call rate, and what does that rate measure?
- Why might two samples with the same underlying event count have different observed counts?
- What denominator should be used when comparing copy-number state proportions across samples?
- A batch has a shifted copy-number distribution. Give two non-exclusive explanations that should be investigated before attributing the shift to biology.
- Why is a sample above a Tukey fence flagged for review rather than automatically excluded?