• Skip to main content
  • Skip to primary sidebar

Nucleics

  • PeakTrace
    • About PeakTrace
    • PeakTrace Online
    • PeakTrace Online Pro
    • PeakTrace 6
    • PeakTrace:Box
    • PeakTrace RP
    • PeakTrace for Chromas
    • Buy PeakTrace
    • Why use PeakTrace?
    • Validation of PeakTrace
    • PeakTrace FAQ
    • PeakTrace In Depth
  • DNA Sequencing Products
    • PeakTrace Basecaller
    • PeakTrace:Box
    • PeakTrace RP
    • PeakTrace for Chromas
    • QualTrace
    • LongTrace
    • CounterTrace
    • dLUTE SEQ
    • UniSeq
    • ASIN
  • Support & Services
    • PeakTrace Online Pro Registration
    • QualTrace III Online
    • DNA Sequencing Troubleshooting Guide
    • PeakTrace RP Downloads
    • PeakTrace:Box Downloads
    • Trace Viewers
    • User Manuals
    • Help Guides
      • How to Install Auto PeakTrace 6
      • How to Upgrade to Auto PeakTrace 6
      • How to Update the PeakTrace License on Linux
      • How to Generate a cmDust File
      • Online Activation of Auto PeakTrace 6
      • Auto PeakTrace 6 Online Activation Guide
      • DNA Sequencing Protocols
        • DNA Sequencing Protocol Tips
        • Exonuclease I – Shrimp Alkaline Phosphatase Clean Up of PCR Products
        • Tris EDTA DNA Sequencing Resuspension Buffer
        • DNA Sequencing Reaction Clean-up using Phenol & Butanol
    • DNA Sequencing Service Reviews
    • Software Downloads
    • MSDS
    • Services
      • Genomics Sequencing
      • Bioinformatics
  • Forum
    • Register
    • Login
    • PeakTrace Basecaller Forum
    • PeakTrace:Box Forum
    • Auto PeakTrace RP Forum
    • QualTrace Forum
    • DNA Sequencing Forum
    • DNA Sequencing Software
    • PCR Forum
    • DNA Isolation Forum
    • LongTrace Forum
    • dLUTE SEQ Forum
  • About
    • Contact
    • News
    • Jobs
    • Nucleics Privacy Policy
Buy PeakTrace

force processing

In Depth: Force Processing

July 4, 2018 By Samuel

Auto PeakTrace 6 with force processing off, reporting TestTrace1.ab1 as a failed trace and TestTrace2.ab1 as a weak trace

One of the more commonly misunderstood settings within PeakTrace™ is the force processing option. This option will allow you to force PeakTrace basecalling of files that would normally be rejected by PeakTrace for poor quality under normal circumstances (Figures 1 & 2).

Auto PeakTrace 6 reporting code 16, Failed trace, for Failure.ab1
Figure 1. An example low quality trace that PeakTrace fails under default conditions.

 

Auto PeakTrace 6 reporting Success for Failure.ab1 with force processing on
Figure 2: Successful PeakTrace basecalling of the same trace after force processing has been toggled on.

Advantages

  • Force processing may be useful when you wish to proceed with processing poor quality traces that are not able to be basecalled by PeakTrace under standard basecalling settings.
  • Forced processing may allow PeakTrace to rescue some usable data from an otherwise unusable trace (Figures 2 & 3).

 

Original failed trace above the force-processed trace, which has basecalls from about base 30
Figure 3. A side by side comparison of the original trace, and the force processed trace. The original trace failed to be basecalled by KB, and was also rejected by PeakTrace under the default settings due to poor quality. Force processing has allowed the PeakTrace basecalling and trace processing to proceed.

 

BLAST result showing 97% identity over 365 bases to Homo sapiens BAC clone CH17-270A2 from chromosome 1
Figure 4: Blast alignment of the extracted data reveals a sequence match. Force processing has allowed useful data to be obtained.

Potential Pitfalls

While force processing can be useful to rescue some traces, there are risks with using it on all traces.

  • Force processing may produce nonsensical or corrupted trace files. It is advised that you use this feature only as a last resort, and that you do so with additional caution.
  • Force processing is not magic. It can not create a high quality trace from a failed reaction. In most cases, a poor quality trace indicates that the sample will need to be sequenced again under improved sequencing conditions.
  • Force processing may result in PeakTrace crashing. While PeakTrace can automatically recover from a crash and restart, you may notice the program closing and restarting.

It is advised that force processing is only used if needed and not by default on all traces.

Filed Under: In Depth, PeakTrace, PeakTrace RP Tagged With: force processing, in depth, low quality trace

Primary Sidebar

DNA Sequencing Help

We have added a guide on troubleshooting automated DNA sequencing problems.

DNA Sequencing Service Facilities Reviews

Please see our review of 325 DNA sequencing core facilities and commercial services for more information on selecting the right sequencing service for your needs.

QualTrace III Online

Try the free online version of the QualTrace DNA sequencing QC software and see how real time quality control tracking can improve your read lengths and lower sequencing failure rates.

Contact Details

email. information@nucleics.com
phone. +61 3 9016 9373
  • home
  • peaktrace
  • software & reagents
  • forum
  • tools
  • services
  • support
  • about

Nucleics

Sanger Seqencing Software

©Nucleics 1999 - 2026