<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://amos.sourceforge.net/wiki/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://amos.sourceforge.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Amos2ace</id>
		<title>Amos2ace - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://amos.sourceforge.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Amos2ace"/>
		<link rel="alternate" type="text/html" href="http://amos.sourceforge.net/wiki/index.php?title=Amos2ace&amp;action=history"/>
		<updated>2026-06-15T01:22:48Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.23.5</generator>

	<entry>
		<id>http://amos.sourceforge.net/wiki/index.php?title=Amos2ace&amp;diff=96&amp;oldid=prev</id>
		<title>Mcschatz: New page: == Overview ==  Amos2ace can be used to convert assembler output in the AMOS message format to the .ACE format (readable by consed).    == Synopsis ==   amos2ace [options] &lt;infile1&gt; &lt;infil...</title>
		<link rel="alternate" type="text/html" href="http://amos.sourceforge.net/wiki/index.php?title=Amos2ace&amp;diff=96&amp;oldid=prev"/>
				<updated>2009-07-08T18:43:07Z</updated>
		
		<summary type="html">&lt;p&gt;New page: == Overview ==  Amos2ace can be used to convert assembler output in the AMOS message format to the .ACE format (readable by consed).    == Synopsis ==   amos2ace [options] &amp;lt;infile1&amp;gt; &amp;lt;infil...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Amos2ace can be used to convert assembler output in the AMOS message format to the .ACE format (readable by consed).&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Synopsis ==&lt;br /&gt;
&lt;br /&gt;
 amos2ace [options] &amp;lt;infile1&amp;gt; &amp;lt;infile2&amp;gt; ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Amos2ace reads one or more AMOS message files specified on the command line and produces a .ACE file. The message files must be provided in a &amp;quot;reasonable&amp;quot; order: the file defining a specific object must occur before a file using it. The output file name is generated from the first file on the command line unless specifically set through option -o (see below).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Options ==&lt;br /&gt;
&lt;br /&gt;
* -o &amp;lt;outfile&amp;gt; - place output in &amp;lt;outfile&amp;gt;&lt;br /&gt;
* -c &amp;lt;chromat_dir&amp;gt; - the chromatograms can be found in directory &amp;lt;chromat_dir&amp;gt;&lt;br /&gt;
* -p &amp;lt;phd_dir&amp;gt; - the PHD files can be found in directory &amp;lt;phd_dir&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: the chromat_dir and phd_dir parameters are only used to provide consed with the necessary information used to display chromatograms. These options are only relevant if the assembler inputs were generated using the phred pipeline.&lt;/div&gt;</summary>
		<author><name>Mcschatz</name></author>	</entry>

	</feed>