Difference between revisions of "Team:Tongji-Software/Attributions"

Line 8: Line 8:
 
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 
.judges-will-not-evaluate { border: 4px solid #e4dede; padding: 2% !important; width: 92%!important;}
 
.judges-will-not-evaluate { border: 4px solid #e4dede; padding: 2% !important; width: 92%!important;}
         .head1 .a{color:#c38d8f;font-size:48px}
+
         .head1 .a{color:#c38d8f;font-size:48px;text-align:center}
 
         body {font-family:}
 
         body {font-family:}
 
</style>
 
</style>
Line 21: Line 21:
 
     It’s more like a workflow. At first, everyone is engaged in previous biology research and decide to do a topic about pathway design. Secondly, biology group try to get access to different database and deliver data to programming group. Then data processing and main part programming are followed. At last, design group can figure out how to show our software reasonably and wiki design.</br>
 
     It’s more like a workflow. At first, everyone is engaged in previous biology research and decide to do a topic about pathway design. Secondly, biology group try to get access to different database and deliver data to programming group. Then data processing and main part programming are followed. At last, design group can figure out how to show our software reasonably and wiki design.</br>
 
     It’s more like a workflow. At first, everyone is engaged in previous biology research and decide to do a topic about pathway design. Secondly, biology group try to get access to different database and deliver data to programming group. Then data processing and main part programming are followed. At last, design group can figure out how to show our software reasonably and wiki design.</br>
 
     It’s more like a workflow. At first, everyone is engaged in previous biology research and decide to do a topic about pathway design. Secondly, biology group try to get access to different database and deliver data to programming group. Then data processing and main part programming are followed. At last, design group can figure out how to show our software reasonably and wiki design.</br>
 +
    <span class="a"> overview</span></br>
 
     <img src="https://static.igem.org/mediawiki/2018/f/fc/T--Tongji-Software--attribution-graph.png" width="600" height="450" />
 
     <img src="https://static.igem.org/mediawiki/2018/f/fc/T--Tongji-Software--attribution-graph.png" width="600" height="450" />
 +
</br>
 +
 
      
 
      
 
</span>
 
</span>

Revision as of 08:16, 2 October 2018


Attribution
What makes Alpha Ant meaningful and wonderful is those people’s great work.
Since we are from different majors, all things can be covered by everyone of us. More information about team members could be found in Team.Generally, we have three main sessions: biology logic thinking and investigation, programming and modeling, design.

It’s more like a workflow. At first, everyone is engaged in previous biology research and decide to do a topic about pathway design. Secondly, biology group try to get access to different database and deliver data to programming group. Then data processing and main part programming are followed. At last, design group can figure out how to show our software reasonably and wiki design.
It’s more like a workflow. At first, everyone is engaged in previous biology research and decide to do a topic about pathway design. Secondly, biology group try to get access to different database and deliver data to programming group. Then data processing and main part programming are followed. At last, design group can figure out how to show our software reasonably and wiki design.
overview