From 2010.igem.org
(Difference between revisions)
|
|
| (63 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| - | == Chain Sorting and Weighting Scheme == | + | {{Team:USTC_Software/Header}} |
| - | Chains in our Chain-Node Model should not have any order since there are no natural ways to sort them. One chain is not
| + | <html> |
| - | preferred to another, since in a complex of multiple chains, which are connected via binding interaction of binding bites on their own, all chains are equivalent. However, a chain-sorting program is a prerequisite for implementations of many other functions, such as comparison of two Chain-Node structures, or pattern matching of template species to those with definite structure.
| + | <head> |
| | + | <style type="text/css"> |
| | + | p.normal {font-variant: normal} |
| | + | p.small {font-variant: small-caps} |
| | + | </style> |
| | + | </head> |
| | | | |
| | + | <body> |
| | + | <p class="normal">This is a paragraph</p> |
| | + | <p class="small">This is a paragraph</p> |
| | + | </body> |
| | | | |
| - | Sorting is always performed under some rules. Since there are no natural options, we design one to generate the unique order for a list of chains. The rule we developed is something like that for comparing two strings: comparing first the database '''id''' and part type of the first part of two chains in alphabet order and if equal, then comparing the next until there are differences or to the end of either chain. For convenience, we generate a unique code (a string) for each chain by putting their database '''id''' and part type one by one, for example,
| + | </html> |
| - |
| + | |
| - | [placI185:ForwardDNA][RBS147:forwardDNA][lacI153:ForwardDNA][TE145:ForwardDNA]...
| + | |
Latest revision as of 08:22, 21 October 2010
This is a paragraph
This is a paragraph
"
