Archive for the ‘Uncategorized’ Category.

Olink

This post previously appeared on substack.

Olink is developing a novel sequencing based proteomics platform.

Their 2020 revenue was $54.1 million, 16.7% growth on 2019. This year growth looks set to be higher (in the 50% range). Interestingly the majority of their business seems to be service related (rather than kits). Margins seem to be ~60%.

Olink have a number of offerings, including a new instrument, the Olink Signature Q100. This appears to be an integrated qPCR platform. This doesn’t interest to me so much. I find their NGS based PEA approach more exciting as it lets you assay >1000 (different) proteins. The qPCR approach is limited to ~96 to 314.

In this post, I briefly review the approach and my initial thoughts.

The PEA approach

I’ve summarized the PEA (Proximity Extension Assay) approach in figure below.

Essentially Olink have designed pairs of antibodies with oligo nucleotide tags. Each antibody pair binds to a single protein (type). The antibody pairs are designed with a complementary region. These regions hybridize. The hybridized region is used as the primer for extension by a polymerase resulting in a longer fragment which embeds the complementary region:

So, in the ideal scenario, you only get extension products when both antibodies bind to the target protein. This should help reduce the false positive rate, as you need two concurrent binding events to get a signal.

As it goes that sounds great, but there are a number of potential failure modes:

In particular, we could imagine that there will be some background signal just from antibodies free in solution. They will stochastically encounter each other, the tags will hybridize, and be extended.

The second point is that antibodies are pretty big compared to target proteins. Schematics generally show them as tiny things, but they are likely several times larger than the target protein. This means that antibody pairs probably need to be carefully selected such that both antibodies can bind at the same time.

Finally, hybridization isn’t 100% specific. So lets say we have an unpaired antibody that shows weak binding, the oligo tags while not perfectly complementary, hybridize. Extension occurs and a signal is produced. Many approaches that use hybridization are problematic for this reason. But here it seems like less of an issue. The sequencing readout should provide enough information to filter out these sequences. Non-complementary region may also be providing information about the antibody and can be used to filter non-matching pairs.

However overall it’s clear that antibodies and oligos must be carefully selected to avoid issues. I imagine the development of these antibody libraries must have been a significant effort for Olink. Which makes the development of a library of 1000s of antibodies all the more impressive.

It’s important to note that we’re only identifying protein types, and likely don’t have a route to detecting single amino acid changes. For this reason it doesn’t make sense to directly compare Olink to next-gen protein sequencing approaches.

However Olink’s approach does seem like it would compete against a platform like Nautilus’ at protein fingerprints rather than full sequences.

It also competes against proposed protein sequencing platforms like QuantumSi, if we assume that they never reach their goal of producing full protein sequences, and in reality also only really generate fingerprints. 

PEA-NGS (Olink Explore)

It’s fairly easy to see how the above scheme would work both with qPCR and sequencing. In the qPCR approach I assume the extension products have primer sites for amplification. In the sequencing approach, you just need to sequence through the extension product.

The sequencing approach (Olink Explore) seems to be a little less well developed than the qPCR platform. But there are several interesting recent papers on the approach. In particular, I’ve been looking at a recent Nature Communications article.

Correlation between NGS and qPCR for selected proteins looks pretty good:

It would be interesting to look at raw data across all proteins, particularly low abundance proteins to see where things break. However, raw data isn’t available “due to patient consent and confidentiality agreements”. On their website Olink state that“some proteins have a low correlation. Proteins with lower correlations tended to have limited spread in at least one platform and/or were typically close to the limit of detection”. But I don’t see a raw dataset anywhere.

Olink Explore seems to be available as a kit to use with your own sequencer now. This could mean that raw reads from this platform will start appearing. This would be interesting, as it should be possible to diagnose the various failure modes present in the raw data.

But the fact that qPCR and NGS correlate well is encouraging. 

Other studies, have looked at how well the PEA/Olink approach is correlated with other approaches (below Mass Spec DIA and DDA):

They seem to correlate well in at least some cases, but the data I’ve found it quite limited. One of the issues with these kinds of validation studies is the lack of dynamic range in existing approaches, limits your ability to accurately assess a new platform.

Conclusion

Overall the Olink PEA approach is a neat idea. The data suggests that it works, and the financials suggest that there’s a market for the approach. I suspect that the potential failure modes ultimately limit the platforms accuracy. However, it’s not clear if this is fundamentally better or worse than other approaches.

Ultimately, coming from sequencing, I’d love to see a to see a high throughput single amino acid resolution sequencing platform. Olink certainly isn’t this. But it’s not clear that such a platform will be available in the medium term (say 10 years).

Perhaps Olink-type solutions are the best we can except in the short term.

DU530 CFL Spectra – Again

In my previous post hacking around with the DU530 I showed a spectra from a CFL which matched published spectra. However I was still having a number of issues, particularly with the stepper driver. In particular I was having issues with the stepper skipping steps.

I’ve been using an EasyDriver (clone) and found that if I disabled microstepping everything was working correctly, but when microstepping was enabled steps would be skipped.

I installed a shunt resistor and took a look at the current output on a scope (over the shunt). I used a couple of 0.22Ohm resistors as this is what I had to hand…

The current trace looked like this:

So for some reason it was hitting it’s maximum current output and then just sitting there. I don’t fully understand why, but reducing the current (via the current adjust pot on the board) and increasing the supply voltage (I pushed it to 24, which seems like it’s more than should be required, but still drawing only ~300mA) resolved the issue. I don’t fully understand why the current adjust should have this effect and should probably investigate further. But the traces look fine and I don’t see any missed steps:

With these changes I was again able to resolve the CFL spectra but now I have more freedom with speed/acquisition time…

Acquiring on the scope at a lower speed seems to result in more noise (likely from vibration), but at least a still visible spectra:

This means I can probably move on to acquiring the photodiode output on a microcontroller… a picture of the EasyDriver/shunt is below for reference:

Nanodrop Notes

I recently wrote about various UV-Vis spectrophotometers on the substack. As part of this I discussed the Nanodrop and how its architecture differs from other instruments and the advantages this gives.

The CCD is quite possibly a Sony ILX511 this sensor was a popular CCD in a number of spectrometers, I’ve previously designed a small interface for this sensor.

The layout seems pretty simple, the light from the fiber comes in, hits a mirror then is reflected off a diffraction grating and heads to the CCD:

The auction contains a number of other photos, which includes a fiber cable. I assume this fiber (and all the other components) must be UV compatible which will increase the cost. But overall, its a very simple optical system.

Thermo documentation suggests that older Nanodrops use Xenon Flash lamps. These give a relatively broad output. It doesn’t seem like the Nanodrop has any kind of sensor on the output of the lamp (unlike more traditional UV-Vis instruments) this will make taking a blank measurement all the more important. The blank will be compensating for both emission differences across wavelength in the lamp and the absorbance of the buffer.

Newer Nanodrops appear to use LEDs, I assume this must be a combination of UV and visible LEDs to cover the entire spectrum.

Other references show the Nanodrop setup, and suggest that fused silica (quartz) is used:

The Nanodrop patents are pretty informative, and make it reasonably clear that the fiber optical “pedestals” are just the ends of a couple of SMA connectors “typically the end of an industry standard SMA fiber optic connector 10, FIG. 3(found as connectors on the ends of optical patch cords like p/n P-400-2-UV-VIS from Ocean Optics inc. of Dunedin, Fla.)… For most SMA connectors the approximate 2 mm end diameter can be effectively covered with 2 microliters of water or a water-based solutions.”

A few other pictures from the auction are below, while the auction is listed as Nanodrop monochromator. I suspect this may however be mislabeled, and am continuing to search for Nanodrop teardown images…

Beckman DU530 Spectrophotometer CFL Spectra

I’ve continued to do some work with the DU530 (see previously blog posts).

I decided to see if I could drive the grating motor and register the spectra from a CFL light through the grating.

As shown above I used an EasyDriver and Arduino to drive the stepper. This showed some slipping (using a 200ms square wave generated from the Arduino to drive the step input). The CFL bulb was just jammed into the lamp box. You can fairly easily see the spectra coming out the grating:

I then registered the output of the far side photodiode using a 10M gain transimpedance amplifier. I continuously ran the stepper and monitored the output on a scope:

Spectra recorded on my scope

This matches the spectra published online extremely well, though the resolution is limited in the scope recording:

Obvious next step would be to record the output with an ADC/microcontroller, this would let me do slower scans. I’m also concerned that the motor is occasionally slipping, which suggests I might want to review the stepper driver…