Why aren 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 then PeakTrace basecalling will not be able improve the basecall as it is 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 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 trace 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. • Mixed signal caused by two or more templates. KB can give such traces high Q20+ read lengths even thought the resulting sequence data is total garbage. While PeakTrace could do the same with these trac
