<?xml version="1.0" encoding="iso-8859-1" ?>
<rss version="2.0">
  <channel>
    <title>PeakTrace Basecaller Forum</title>
    <link>http://www.nucleics.com/forum/list/21.html</link>
    <description><![CDATA[Forum for discussion and questions about the PeakTrace basecaller]]></description>
    <language>EN</language>
    <pubDate>Tue, 23 Oct 2007 22:27:48 -0400</pubDate>
    <lastBuildDate>Tue, 23 Oct 2007 22:27:48 -0400</lastBuildDate>
    <category>PeakTrace Basecaller Forum</category>
    <generator>Phorum 5.1.22</generator>
    <ttl>600</ttl>
    <item>
      <title>PeakTrace for MegaBACE recent developments</title>
      <link>http://www.nucleics.com/forum/read/21/365/365.html#msg-365</link>
      <author>nucleics</author>
      <description><![CDATA[We have started working on a version of PeakTrace designed for the MegaBACE sequencers. So far things are looking good and we have a version that will process traces generated with the ET terminators. If you are interested in trying this version please contact us.]]></description>
      <category>PeakTrace Basecaller Forum</category>
      <guid isPermaLink="true">http://www.nucleics.com/forum/read/21/365/365.html#msg-365</guid>
      <pubDate>Tue, 23 Oct 2007 22:27:48 -0400</pubDate>
    </item>
    <item>
      <title>PeakTrace v1.11</title>
      <link>http://www.nucleics.com/forum/read/21/363/363.html#msg-363</link>
      <author>nucleics</author>
      <description><![CDATA[Update to PeakTrace v1.11

A couple of updates to PeakTrace.

1. PeakTrace now handles traces with significant inter-channel signal intensity differences (ie traces where one or more channels were much stronger than the others). Previous these traces gave a spacing model error.

2. A new processing option has been introduced that allows either the original KB basecalling start point or the secondary start point to be selected for PeakTrace basecalling. This feature allows poor quality signal at the front of the trace to be clipped (eg removing problems caused by dye blobs).]]></description>
      <category>PeakTrace Basecaller Forum</category>
      <guid isPermaLink="true">http://www.nucleics.com/forum/read/21/363/363.html#msg-363</guid>
      <pubDate>Thu, 27 Sep 2007 07:42:50 -0400</pubDate>
    </item>
    <item>
      <title>Re: PeakTrace Upgrade v1.07</title>
      <link>http://www.nucleics.com/forum/read/21/329/334.html#msg-334</link>
      <author>nucleics</author>
      <description><![CDATA[Hi Ron

That would be great. I will email you directly about this as I really would like to add BigDye 1.1 support to PeakTrace.]]></description>
      <category>PeakTrace Basecaller Forum</category>
      <guid isPermaLink="true">http://www.nucleics.com/forum/read/21/329/334.html#msg-334</guid>
      <pubDate>Mon, 03 Sep 2007 03:18:04 -0400</pubDate>
    </item>
    <item>
      <title>PeakTrace v1.09</title>
      <link>http://www.nucleics.com/forum/read/21/333/333.html#msg-333</link>
      <author>nucleics</author>
      <description><![CDATA[New Features in PeakTrace 1.09:

* PeakTrace now outputs .phd.1 and .seq files in addition to .ab1 or .scf files.

* PeakTrace can now handle traces with .ab1 or .abi (ABI 377 traces) file extensions.

* Trace folders can be upload to PeakTrace FTP in either .zip or .7z format. We recommend using the 7zip (www.7zip.org) .7z format as the compression for .ab1 traces is about 60% greater than gzip or bzip2.

* Corrupt or invalid trace files are now moved to the user's &quot;out&quot; folder on the server. This prevents the user receiving more than one email informing them that their files are invalid.]]></description>
      <category>PeakTrace Basecaller Forum</category>
      <guid isPermaLink="true">http://www.nucleics.com/forum/read/21/333/333.html#msg-333</guid>
      <pubDate>Mon, 03 Sep 2007 03:12:58 -0400</pubDate>
    </item>
    <item>
      <title>Re: PeakTrace Upgrade v1.07</title>
      <link>http://www.nucleics.com/forum/read/21/329/332.html#msg-332</link>
      <author>Ron Burns</author>
      <description><![CDATA[Hi Daniel,

I just noticed this message. I have one customer who we have done a lot   of sequencing for who uses Big DYE V1.1. If you need data I could contact them and ask if they would be willing to let you use their data for testing. Let me know.


Thank you,

Ron Burns]]></description>
      <category>PeakTrace Basecaller Forum</category>
      <guid isPermaLink="true">http://www.nucleics.com/forum/read/21/329/332.html#msg-332</guid>
      <pubDate>Wed, 29 Aug 2007 12:26:51 -0400</pubDate>
    </item>
    <item>
      <title>PeakTrace Upgrade v1.07</title>
      <link>http://www.nucleics.com/forum/read/21/329/329.html#msg-329</link>
      <author>nucleics</author>
      <description><![CDATA[We have upgrade the PeakTrace basecalling of ABI 377 traces. The results are rather astounding (even for me) - we even have one 377 trace which gives over 1000 Q20+ bases!

At this stage support of ABI 377 traces is limited to the BigDyeV3.1 chemistry. If you are using BigDye v1.1 please contact us as the reason for our inability to support BigDyev1.1 is we do not have any example ABI 377 traces using this chemistry to train the software.]]></description>
      <category>PeakTrace Basecaller Forum</category>
      <guid isPermaLink="true">http://www.nucleics.com/forum/read/21/329/329.html#msg-329</guid>
      <pubDate>Fri, 10 Aug 2007 05:20:28 -0400</pubDate>
    </item>
    <item>
      <title>Welcome to the PeakTrace forum</title>
      <link>http://www.nucleics.com/forum/read/21/327/327.html#msg-327</link>
      <author>nucleics</author>
      <description><![CDATA[Welcome to the PeakTrace basecaller forum. This is the place to ask questions or discuss the PeakTrace basecaller. 

We will also be using this forum to make announcements about PeakTrace developments.]]></description>
      <category>PeakTrace Basecaller Forum</category>
      <guid isPermaLink="true">http://www.nucleics.com/forum/read/21/327/327.html#msg-327</guid>
      <pubDate>Wed, 08 Aug 2007 04:14:46 -0400</pubDate>
    </item>
  </channel>
</rss>
