In Part I of this series we looked at how to limit the sharpness of the trace peaks from PeakTrace by using the no peak resolution setting. While this is…
- 9 Dec 2015In Depth: Extra Smoothing Part II
- 8 Dec 2015In Depth: Extra Smoothing Part I
An interesting concern we get from customers about the PeakTrace Basecaller™ is that the peaks are "too sharp" at the end of the trace. This has always puzzled us because…
- 1 Dec 2015In Depth: Extra Normalization
A common problem with Sanger DNA sequencing is a rapid falloff in peak signal strength - what is known colloquially as a “ski-slope” trace. This problem can often be difficult to…
- 30 Nov 2015In Depth: Automatic Bubble Spike Removal
One production problem that can occur with Sanger DNA sequencing is sharp spikes in the raw data channel. These spikes can appear anywhere in the raw channel, are…
- 27 Nov 2015PeakTrace 6.12 Linux x86_64 Released
We have released PeakTrace 6.12 for x86_64 Redhat/CentOS 6. This fixes a few minor bugs, but it does include one important improvement - bubble spike correction. Bubble spikes are sharp spikes…
- 26 Nov 2015Auto PeakTrace RP 6.12 Released
We have released Auto PeakTrace 6 RP 6.12. This is mostly a bug fix release, but it does contain one significant improvement - bubble spike correction. Bubble spikes are sharp…
- 24 Nov 2015In Depth: Clean Baseline
The clean baseline setting within the PeakTrace Basecaller™ is a cosmetic option that can be used to improve the appearance of trace files. While in an ideal world…
- 20 Nov 2015Why is the default Good Base Improvement −20?
A question we occasionally get asked is why is the default good base improvement set to −20? The reasons are complex, but it is basically due to the way…
- 19 Nov 2015Auto PeakTrace RP and the Good Base Improvement Setting
Just a quick update on how Auto PeakTrace RP charges for traces processed. Officially it has always been that if you set the good base improvement to value…
Page 15 of 27 · 237 posts Newer postsOlder posts