How much does Auto PeakTrace RP cost?
The Auto PeakTrace RP software is free to download for registered customers. Processing uses purchased RP units, which also work in PeakTrace Online Pro. See current unit bundles and prices and allow up to 12 hours for purchases to be credited.
At default settings, one RP unit is charged for each trace PeakTrace improves. Setting Minimum basecall improvement above -9 charges a unit for every processed trace.
How much does the PeakTrace:Box system cost?
PeakTrace:Box pricing depends on processing volume and lease arrangements. See the purchase page or email {This email is obscured. Your must have javascript enabled to see it} for a current quotation.
What do I need to do to use Auto PeakTrace RP?
You need a PeakTrace RP account, units, an internet connection and .ab1 or .abi traces containing raw data. The downloads page lists the current Windows desktop release and older releases (the legacy Mac installer is for macOS 10.12 and earlier). You can also run your RP account directly in any modern browser via PeakTrace Online Pro with no software installation (paid-account guide).
How is PeakTrace different to other basecallers like KB, phred or TraceTuner?
Other basecallers like phred or TraceTuner work by basecalling the processed peak data in each trace file. This means that their basecalling accuracy is limited to the quality of the processed peaks provided by the ABI data collection software. PeakTrace in the same way as the KB Basecaller™ works in that it works directly on the raw data contained within the .ab1 file. The PeakTrace Basecall reprocesses the raw data before basecalling. This means that PeakTrace is able to provide significantly better basecalls, with fewer errors and longer reads than any other Sanger sequencing basecaller.
One way to look at PeakTrace is that it is similar to ABI’s KB basecaller, but vastly superior in both data processing and basecalling accuracy.
Does PeakTrace come with a guarantee?
PeakTrace comes with a 60 day, full money back guarantee. If you find that the PeakTrace Basecaller does not meet your expectations for any reason you can return it within 60 days for a full refund – all we ask is that you tell us why you chose to cancel. This means you can trial PeakTrace in production without risk that it might not work with your workflows.
Why are some of my traces returned as .scf files and some as .ab1 files?
Output depends on the selected file format and the information available in the input trace. Some older ABI files lack fields needed for .ab1 output with base quality scores, so PeakTrace may return an .scf trace. Paid Online Pro accounts can select .ab1, .scf, or both under Output files. Input must still contain the original raw data; .scf files cannot be used as input.
What do I need to use the PeakTrace:Box system?
Other than the PeakTrace USB Key and the PeakTrace software, there are no external requirements. The traces can be PeakTrace basecalled at any time after they have been collected from the instrument. Since PeakTrace uses the raw data signal contained within each .ab1 trace file, it can not basecall .scf trace files as these only contain the processed peak data.
Can I try PeakTrace for free?
New users can register for the free PeakTrace Online Pro trial. The trial allows up to 3 traces per upload and 250 per day. Its password changes every Sunday, so register when you are ready to test. Paid RP accounts use their own units and do not need the trial password.
How do I use the free PeakTrace Online Pro service?
- Register for the free trial using your work or institution email address.
- Enter the emailed trial password on the Online Pro page.
- Select up to 3 traces, choose your settings and click Basecall traces.
- Download the processed traces from the results page.
Allow time for uploading and processing. The daily trial limit is 250 traces. The help guide explains each setting.
Can I use a paid PeakTrace RP account in my browser?
Yes. Sign in on PeakTrace Online Pro with your 10-character PeakTrace RP License Key to process up to 96 .ab1 or .abi traces per batch using your existing RP units (how it works). At default settings, one RP unit is charged for each trace PeakTrace improves (setting Minimum basecall improvement above -9 charges a unit for every processed trace). Each batch downloads as a single .zip containing your selected output files and a peaktrace.log file; downloads remain available for 3 days.
Can I trust the results from PeakTrace – they seem too good to be true?
This is not a simple question to answer as validation of trace processing and base calling software is very complex (for more information on basecalling validation see Ewing et al. (1998) Genome Research 8: 175 – 194). We have extensively validated PeakTrace using the approach of Ewing et al. on a variety of traces of known sequence generated by several large sequencing centers. We have found PeakTrace basecalling to be more reliable than that provided by ABI’s KB basecaller and phred on ABI 3730 data. This analysis is summarized on the PeakTrace validation page.
So to simply answer the question, if you are happy with the validity of the KB Basecaller then you will be more than happy with the validity of PeakTrace.
I only have .scf files – can I use PeakTrace?
No. The .scf file does not contain the raw data needed for the PeakTrace reprocessing. If you have a large sequencing project that you would like to reprocess using PeakTrace and only have the .scf files, we suggest you request the original .ab1 traces from the sequencing facility that generated the data. Most large sequencing centers archive their original .ab1 files. If they don’t, then suggest that they start doing so.
Can I buy the PeakTrace software to use on my own machine?
Auto PeakTrace RP runs as a Windows desktop client and sends traces to the processing server. For browser access on Windows, macOS or Linux, use PeakTrace Online Pro with your RP account. If traces must remain in your facility, ask about PeakTrace:Box.
So how does PeakTrace work?
The software underlying PeakTrace has involved more than 25 person years of work by our scientists and engineers here at Nucleics. The algorithms used are trade secrets, but in brief, PeakTrace works in a similar fashion to the KB basecaller™ by re-processing the raw ABI data contained within each .ab1 trace file. Better processing enables the PeakTrace basecaller to be more accurate, as well as providing better looking traces.
Why aren’t my traces improved by PeakTrace?
There are a number of reasons why PeakTrace can not improve a trace file. The major factors affecting PeakTrace basecalling are:
- Length of the read. If a read is shorter than what KB calls perfectly (i.e. less than 500 bases) then PeakTrace will not be able to improve the basecall as it is already as good as it can be.
- Strength of raw trace signal. If the raw signal is very weak (near to the signal noise level), then PeakTrace will not be able to improve the trace. The signal strength is particularly critical at the far ends of the trace. This is the most common cause we see for the non-improvement of traces. PeakTrace makes good traces better, not failed traces good!
- Failed sequencing reactions. Obviously if the sequencing reaction has failed, then PeakTrace will not be able to magically make the reaction work and produce a trace out of noise.
- Mixed signal caused by two or more templates. KB can give such traces high Q20+ read lengths, even though the resulting sequence data is total garbage. While PeakTrace could do the same with these traces, there is little point as the sequence is totally wrong and hence useless.
For advice on how to improve your DNA sequencing reactions, please visit the QualTrace III quality control software demonstration for a free automatic inspection of your traces, or the DNA sequencing troubleshooting advice pages.
Can I process ABI 377, ABI310 or ABI3700 traces?
Yes. The PeakTrace software supports all ABI instruments (including SeqStudio and SeqStudio Flex), although not all run conditions. If you have a run condition that is not supported, please contact us at {This email is obscured. Your must have javascript enabled to see it}.
How do I find out how many traces I have processed?
The Auto PeakTrace RP Options window and the signed-in Online Pro account bar show your remaining RP units. Online Pro also shows the units used by each batch. The peaktrace.log file records processing results for each trace.
Can I use the PeakTrace service with MegaBACE traces?
Yes. We support the MegaBACE sequencer. This support is still fairly limited, but it does work for the common run conditions. I suspect that there is no one left using the MegaBACE instruments anymore, but the support is still there.
What DNA sequencers and run conditions are supported?
ABI 3730, 3730xl, 3100 and 3130 Run Conditions
- POP7, BigDye3, 8.5kV, 50cm array traces
- POP7, BigDye1, 8.5kV, 50cm array traces
- POP7, BigDye3, 7kV, 50cm array traces
- POP7, BigDye1, 7kV, 50cm array traces
- POP7, BigDye3, 11kV, 50cm array traces
- POP7, BigDye1, 11kV, 50cm array traces
- POP7, BigDye3, 8.5kV, 36cm array traces
- POP7, BigDye1, 8.5kV, 36cm array traces
- POP7, BigDye3, 4.5kV (ultra long run), 50cm array traces
- POP7, BigDye3, 6.1kV (long run), 50cm array traces
- POP7, BigDye1, 6.1kV (long run), 50cm array traces
- POP7, BigDye3, >12kV (rapid run), 50cm array traces
- POP7, BigDye1, >12kV (rapid run), 50cm array traces
- POP7, BigDye3, >12kV (rapid run), 36cm array traces
- POP7, BigDye1, >12kV (rapid run), 36cm array traces
- POP7, ET Terminator, >12kV (rapid run), 50cm array traces
- POP7, ET Terminator, 8.5kV, 50cm array traces
- POP7, ET Terminator, 8.5kV, 36cm array traces
- POP7, BigDye3, 8.5kV, 80cm array traces
- POP7, BigDye1, 8.5kV, 80cm array traces
- POP6, BigDye3, 8.5kV, 50cm array traces
- POP6, BigDye1, 8.5kV, 50cm array traces
- POP6, BigDye3, 8.5kV, 36cm array traces
- POP6, BigDye1, 8.5kV, 36cm array traces
- POP6, ET Terminator, 8.5kV, 50cm array traces
- POP6, BigDye3, >12kV (rapid run), 50cm array traces
- POP6, BigDye1, >12kV (rapid run), 50cm array traces
- POP6, BigDye3, >12kV (rapid run), 36cm array traces
- POP6, BigDye1, >12kV (rapid run), 36cm array traces
- POP6, ET Terminator, >12kV (rapid run), 36cm array traces
- POP4, BigDye3, 8.5kV, 80cm array traces
- POP4, BigDye1, 8.5kV, 80cm array traces
- POP4, BigDye3, 8.5kV, 50cm array traces
- POP4, BigDye1, 8.5kV, 50cm array traces
- POP4, BigDye3, 8.5kV, 36cm array traces
- POP4, BigDye1, 8.5kV, 36cm array traces
- POP4, BigDye3, >12kV (rapid run), 36cm array traces
- POP4, BigDye1, >12kV (rapid run), 36cm array traces
ABI 3500 Run Conditions
- POP7, BigDye3, >18kV (ultra rapid run), 50cm array traces
- POP7, BigDye1, >18kV (ultra rapid run), 50cm array traces
- POP7, BigDye3, >13kV (rapid run), 50cm array traces
- POP7, BigDye1, >13kV (rapid run), 50cm array traces
- POP7, BigDye3, 8.5kV, 50cm array traces
- POP7, BigDye1, 8.5kV, 50cm array traces
- POP6, BigDye1, >18kV (ultra rapid run), 50cm array traces
ABI 3700 Run Conditions
- POP5, BigDye3, 50cm array traces
- POP5, BigDye1, 50cm array traces
- POP6, BigDye3, 50cm array traces
- POP6, BigDye1, 50cm array traces
ABI 310 Run Conditions
- POP6, BigDye3, >13kV (rapid run), 50cm array traces
- POP6, BigDye3, 50cm array traces
- POP6, BigDye1, 50cm array traces
- POP6, BigDye3, >13kV (rapid run), 36cm array traces
- POP7, BigDye1, >13kV (rapid run), 36cm array traces
- POP6, BigDye3, 36cm array traces
- POP6, BigDye1, 36cm array traces
- POP4, BigDye3, 36cm array traces
- POP6, BigDye3, >13kV (rapid run), 30cm array traces
- POP6, BigDye1, >13kV (rapid run), 30cm array traces
- POP6, BigDye3, 30cm array traces
- POP6, BigDye1, 30cm array traces
- POP4, BigDye1, >13kV (rapid run), 30cm array traces
- POP4, BigDye3, 30cm array traces
- POP4, BigDye1, 30cm array traces
ABI 377 Run Conditions
- BigDye3 traces
- BigDye1 traces
- ET Terminator traces
MegaBACE Run Conditions
- BigDye3 traces
- ET Terminator traces
- ET Primer traces
MJ Research BioStation Run Conditions
- Dye Rhodamine traces
If you don’t see your run condition or DNA sequencer on this list please contact us at {This email is obscured. Your must have javascript enabled to see it} as we should be able to add support for your run condition.
