Headed to AACR? Schedule time to connect with us at bd@ozette.com

Blog

Ozette Resolve: Why We Built It and Optimizing Use (Part 1)

Evan Greene, Chief Officer Applied Sciences

Are you regularly generating spectral cytometry data? If so, do you:

  • Worry about your data quality?
  • Look at gating plots and wonder if you’re seeing technical artifacts or biological signals?
  • Wonder whether it is appropriate to compensate your data after unmixing?
  • Try to cross compare results generated by different teams, instruments, or sites?
  • Spend more time than you’d like trying to answer these types of questions?


If you answered “yes” to any of the above, chances are you’ve had conversations with your colleagues that are similar to conversations we’ve had inside Ozette. In fact, these are the kinds of conversations that led us to build Ozette Resolve Spectral Unmixing, our instrument-agnostic solution for evaluating unmixing controls and performing adaptive unmixing of spectral cytometry datasets.

Time and again we found that errors introduced in the unmixing process were the root cause of complex issues we observed in downstream data analysis. The nature of the errors varied. Sometimes, a stain wasn’t behaving as expected. At other times, undetected cross-contamination of single-color controls compromised the estimated spectral signatures. In still other cases, fluors with highly similar spectra interacted with the specific mathematical unmixing model to produce strange artifacts.

Whatever the error, as an organization we decided that we needed a system to surface and correct these kinds of issues in data we analyzed. Our solution is called Ozette Resolve. We use it to reliably deliver high-quality unmixed outputs for all spectral datasets that we generate or analyze. Our customers also use the system to unmix their own data to achieve similarly high-quality outputs.

We’ve realized there is significant value in using Ozette Resolve to monitor the quality of unmixing controls over time: changes in experimental factors like disease states, reagents, buffering systems, stimulation conditions, and biological matrices can all affect unmixing outputs by altering the spectral signatures and autofluorescence of the samples. By monitoring the performance of controls through the Resolve workflow, we are able to identify issues in control files that would produce unmixing errors. And by remediating these issues before unmixing the raw data, we prevent errors that would confound downstream analysis from appearing in our unmixing outputs. This saves us substantial time and effort up front. We think your team can achieve similar efficiency savings and superior outputs by updating your workflows with Ozette Resolve.

To help you reach this goal, we’ll discuss our own set of best-practices for optimizing unmixing outputs through Ozette Resolve. Even if you’re not using Ozette Resolve today, you may still find it worth your while to read these discussions since many of these suggestions apply to cytometry in general. Our first topic is a critical, but often overlooked, component of any experiment: unstained controls.

Unstained Controls

Unstained controls are used to estimate the autofluorescent properties of materials measured on a cytometer. These controls are particularly valuable in Ozette Resolve, since it calculates event-specific autofluorescence estimates from these controls.

Many conventional approaches aim to account for autofluorescence by using an unstained control to estimate one or several autofluorescent profiles, either on the bulk cell population measured in a sample, or subdivided into different gated populations based on light scatter profiles (e.g. Lymphocytes, Monocytes, Granulocytes). These autofluorescent profiles are then often adjoined to a fixed unmixing matrix.

In Ozette Resolve, unstained controls are instead used to estimate event-specific autofluorescence contributions. The system therefore benefits when you use paired unstained controls for each sample you unmix, since generating paired controls provides the system with the best possible data to estimate autofluorescence contributions for the types of events actually measured in a given sample.

To see this, consider four unstained PBMC samples from four different subjects. We can immediately see differences in the scatter properties of the four assayed samples.

Some of these differences can be explained by differences in the number of events acquired (ranging from about 62,000 events in sample A to about 295,000 events in the largest sample C). By gating down to lymphocytes within these samples,

we can compare the median measured autofluorescence intensity within lymphocytes across the four subjects.

From this data we can see that there are subject-specific differences in median autofluorescence. The magnitude of the difference varies by detector, but the difference between the brightest and dimmest median signal summed across detectors represents about 9,100 fluorescence units. This is a difference caused by sample autofluorescence alone, and demonstrates that there are sample-specific autofluorescence effects. If we plot the 5% and 95% bands on the dimmest and brightest samples respectively, we can see that there is a lot of overlap between samples:

On the one hand, this overlap implies that many events can have their autofluorescence properties reasonably well-approximated by either sample, since both files contain events with similar autofluorescence signatures. On the other hand, despite this overlap, we can see that the dimmest events in the dimmest sample would be not be well-approximated using the brightest sample, and conversely the brightest events in the brightest sample would not be well-approximated by using the dimmest sample, since each sample lacks example events with those empirical autofluorescence characteristics.

While PBMCs stained to measure lymphocytes represent a somewhat simple use case, observing variable autofluorescence profiles between subjects and experimental runs have led us to develop the following recommendations for using unstained controls in Resolve:

  1. To optimize outputs, generate paired unstained controls alongside your experimental samples.
  2. If the material you are assaying does not admit sample pairing (e.g. you are assaying clinical samples and there is minimal left-over material per sample), we recommend pooling left-over material across a run and using a pooled unstained control for the entire run.
  3. If pairing or pooling is not possible, for each material type you intend to assay, associate the brightest unstained sample you have available with the panel you are running, and use that to estimate autofluorescence.

To be clear, we have achieved high-quality unmixing through Resolve under all three recommended scenarios. However, we have found it helpful to recommend this hierarchy of prioritization, as paired unstained controls are particularly valuable for calculating the recently developed positivity scores included in Resolve unmixing outputs. Positivity scores are a novel metric generated as supplementary parameters through Resolve. This metric can be used to inform objective gating and will be discussed in detail in a future post.

In our next article, we will discuss how to use Ozette Resolve to detect and remediate cross-contamination between single stain controls. In the meantime, if you’d like to try these recommendations with Resolve today, try our 30-day free demo at https://ozette.com/biological-insights/.

Ozette Resolve: Why We Built It and Optimizing Use (Part 1)

Unmixing spectral cytometry data is a complex process that combines both wet- and dry-lab workflows. Errors introduced in either part can propagate and compromise downstream analysis. Here we describe Ozette Resolve Spectral Unmixing, a solution that improves unmixing through quality evaluation of controls and adaptive, event-level unmixing, with guidance on optimizing results using appropriate unstained controls.

On complexity, decision making, and unintended consequences.

Scientific complexity can obscure simple errors, with potentially severe consequences. Flow cytometry, a powerful yet intricate tool, exemplifies how errors in data generation and analysis can propagate unnoticed, affecting critical outcomes in drug development and patient care. Ozette addresses these challenges by integrating validated computational methods, quality monitoring, and transparent data analysis, ensuring reliable insights that accelerate clinical research and improve decision-making.