Team:Vanderbilt Software/Future Work

From 2014.igem.org

(Difference between revisions)
(Created page with "{{CSS/Main}} <html> <style type="text/css"> body { position: relative; width: 850px //100%; margin: 0;...")
 
Line 62: Line 62:
   <td width="45%"  valign="top">
   <td width="45%"  valign="top">
     <h3>Future Work</h3>
     <h3>Future Work</h3>
 +
    <p>Future work mostly revolves around bringing darwin from a
 +
standalone diff-producing executable to an integrated system
 +
with a GUI usable by novices. The major challenge with that
 +
is parsing the plethora of different file types used to represent
 +
DNA although the implementation of other formats such as
 +
SBOL, ApE, etc., could be done easily by extracting the
 +
actual genetic sequence from the file.</p>
 +
<p>In addition, the current algorithms are unable to deal with
 +
introns of any sort in the input DNA sequence, and will
 +
attempt to split the file into ORFs regardless. The ability to
 +
correctly identify non-coding regions like this would create a
 +
far more valuable piece of software, able to deal with
 +
prokaryotes and eukaryotes alike.</p>
   </td>
   </td>
</tr>
</tr>

Latest revision as of 17:43, 18 January 2015


Home Program

Future Work

Future work mostly revolves around bringing darwin from a standalone diff-producing executable to an integrated system with a GUI usable by novices. The major challenge with that is parsing the plethora of different file types used to represent DNA although the implementation of other formats such as SBOL, ApE, etc., could be done easily by extracting the actual genetic sequence from the file.

In addition, the current algorithms are unable to deal with introns of any sort in the input DNA sequence, and will attempt to split the file into ORFs regardless. The ability to correctly identify non-coding regions like this would create a far more valuable piece of software, able to deal with prokaryotes and eukaryotes alike.