We only have access to a NovaSeq6000, does
anyone have experience using NovaSeq for the i5 vs i7 indexing
scheme?
I don't but I asked Illumina about it and they said they'd get back
to me very soon, so stay tuned. I imagine i5 indexing will require
the same workaround as on the MiSeq and NextSeq: just do the minimum
number of cycles in Index Read 1 (i7) so the software doesn't
complain (3 wasted cycles on MiSeq, 2 on NextSeq, waiting for answer
about NovaSeq).
Also, I'm not experienced with the NovaSeq myself, but I gather the
"Xp Workflow" allows you to run different library pools in each lane
(2 lanes on SP, S1, S2; 4 lanes on S4). So keep in mind that you can
run e.g. 192 or 384 libraries together using only 96 indexes, though
on the larger flow cells that might still be more reads per library
than you really need.
Has anyone, for simplicity/storage, used
combinatorial indexing rather than UDIs for Smart-3Seq?
This could certainly save some money on the PCR primers, however the
reason we stopped using i7 indexes altogether and switched to
96-plex i5-only indexing is because we seem to get a lot of poly(A)
artifacts in the i7 index read and not in the i5. So you might lose
some fraction of usable reads if you're depending even partly on the
i7 index.
It may be confusing and risk human error (including bad choices of
index combinations) if you manually combine a unique P5 and P7
primer in every sample at the time you do the experiment, rather
than premix all possible combinations so it's just one tube of
primer pair to one tube of sample, unless maybe you're doing a full
plate and going down the rows and columns with a multichannel pipet.
If you have to make 384 tubes of premixed primers anyway, then
combinatorial indexing doesn't really save so much trouble, just
cost.
Do you have available any index set that
would achieve this?
IDT (xGen) and PerkinElmer (NEXTFLEX) already sell UDIs up to
1536-plex (2 x 10 nt), so if you can track down their designs I
could put those into a list of designs for i5-only indexing. Or it's
possible you could just buy their PCR primer sets if they're
TruSeq-compatible. I'm not sure if anyone has 384-plex combinatorial
dual indexes; you could of course choose 16 x 24 of the UDIs, but
these indexes can be surprisingly fussy about cross-compatibility so
that's risky and needs empirical validation.
Any new recommendations on how to order from
IDT (e.g. purification method, ultramers vs not, etc)
On IDT's advice we've switched to Ultramer synthesis with no
purification, and only one phosphorothioate at the end. The Ultramer
synthesis is so efficient that it doesn't really need purification
to get mostly full-length oligos, and for PCR primers it's actually
not a big problem if some of them are slightly truncated anyway. So
skipping the purification greatly reduces the cost with little
downside. (Keep the RNase-free HPLC for the 1S and 2S primers,
though; those need it.)
I see IDT has a smaller 200 pmol scale for Ultramer oligos ordered
in plates (theoretically up to 40 libraries per index), so depending
on the size of your project that might be economical. It seems to be
the same price to order them "wet" (in TE) rather than lyophilized,
which saves a lot of time on that scale, though I still remeasure
every single tube on the Nanodrop because of a traumatic experience
years ago.
Whereas initially we used huge amounts of
PhiX (up to 40%!) to prevent errors from the GGG reads in cycles
6,7,8 under the legacy scheme (with 96 primer set), we have
consistently shown that 5% phiX works well, and plan to test even
lower.
Thanks very much for this information, which will definitely be
helpful to other users. On other platforms (MiSeq, NextSeq) it works
fine with no phiX at all, because it's only the GGG cycles that have
low diversity. I've heard the NovaSeq may be more sensitive to
losing focus in the dark GGG cycles, so it may still require a
little bit of phiX. But even if you find that it doesn't, I don't
recommend skipping phiX altogether, because it's a cheap insurance
policy in case of instrument failure - tech support's first response
is to blame the homemade libraries unless you can show them phiX
didn't work either.