Get shared seq watch right

Start Shared Seq Watch with the constraint that matters most in real life: space, timing, budget, skill level, maintenance, or availability. That first constraint should shape the rest of the plan instead of appearing as an afterthought. Keep the first pass simple enough to verify. Compare the main options against the same criteria, remove choices that only work in ideal conditions, and save optional upgrades for later.

The simplest way to use this section is to write down the real constraint first, compare each option against it, and choose the path that still works outside ideal conditions.

Work through the steps

Shared Seq Watch works best as a clear sequence: define the constraint, compare the realistic options, test the tradeoff, and choose the path with the fewest hidden costs. That order keeps the advice usable instead of decorative. After each step, pause long enough to check whether the recommendation still fits the reader's actual situation. If it depends on perfect timing, unusual access, or a best-case budget, include a simpler fallback.

1
Define the constraint
Name the space, budget, timing, or skill limit that shapes the Shared Seq Watch decision.
2
Compare realistic options
Use the same criteria for each option so the tradeoff is visible.
3
Choose the practical path
Pick the option that still works after cost, maintenance, and fallback needs are included.

Common mistakes in shared sequencing workflows

Even with robust protocols, errors in library preparation or data handling can compromise the entire experiment. Because SHARE-seq links chromatin accessibility (ATAC-seq) and gene expression (RNA-seq) from the same cell, the margin for error is thinner than in single-modality assays. A mistake in one half of the assay often invalidates the other.

Skipping cell viability checks

Dead or damaged cells release free-floating DNA and RNA, creating "ambient RNA" and background noise that obscures true biological signals. If cell viability drops below 90% before loading into the droplet system, you will see high mitochondrial reads and low gene counts per cell. This makes it impossible to distinguish real low-expression genes from debris. Always check viability with a simple dye exclusion test before proceeding.

Overloading the microfluidics

SHARE-seq requires precise cell concentration. Overloading the GEM generation step causes "doublets"—two cells trapped in one droplet. While doublet detection algorithms exist, they are less effective in multi-omics data because the combined ATAC and RNA profiles can look like a single, noisy cell rather than two distinct ones. Follow the manufacturer’s recommended cell input strictly. If you must pool samples, normalize cell counts carefully to prevent one sample from dominating the droplet capacity.

Ignoring batch effects during library pooling

When sequencing multiple samples, differences in library preparation dates or reagent lots can introduce technical artifacts that mimic biological variation. This is especially dangerous in comparative studies. Always include spike-in controls or use a balanced experimental design where conditions are interlaced across batches. When analyzing the data, use tools like Seurat or Scanpy that explicitly model and remove batch effects before clustering.

Mixing up barcode indices

SHARE-seq uses unique dual indices (UDIs) to multiplex samples. Using the wrong index pair or reusing indices from a previous run with different sample multiplexing factors can lead to index hopping or cross-contamination. This results in cells being assigned to the wrong sample, ruining downstream analysis. Double-check your index plate layout against the sequencing run plan. Use unique dual indices exclusively to prevent this issue.

Shared seq watch: what to check next