"
Team:SYSU-Software/Safety
From 2012.igem.org
(Difference between revisions)
Nie1234567 (Talk | contribs) |
Nie1234567 (Talk | contribs) |
||
| (5 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
{{:Team:SYSU-Software/menu}} | {{:Team:SYSU-Software/menu}} | ||
| - | <html xmlns="http://www.w3.org/1999/xhtml"> | + | <html xmlns="http://www.w3.org/1999/xhtml" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office"> |
<head> | <head> | ||
| Line 20: | Line 20: | ||
<div id="header" class="clear" style="background-color: #545454"> | <div id="header" class="clear" style="background-color: #545454"> | ||
<div class="wrapper"> | <div class="wrapper"> | ||
| - | <a href="/" class="sysu-title"></a> | + | <a href="https://2012.igem.org/Team:SYSU-Software" class="sysu-title"></a> |
<!--end navigation--> | <!--end navigation--> | ||
| Line 48: | Line 48: | ||
</li> | </li> | ||
| - | + | ||
| - | + | ||
| - | + | ||
| Line 56: | Line 54: | ||
<li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Notebook">Notebook</a></li> | <li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Notebook">Notebook</a></li> | ||
| + | <li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Practice"> | ||
| + | Tips</a><!--input an em tag as a space,IE is gread need--> | ||
| + | </li> | ||
</ul> | </ul> | ||
| Line 84: | Line 85: | ||
</table> | </table> | ||
<div id="doc-contents"> | <div id="doc-contents"> | ||
| - | <h2 id="r0">Q1:Would any of your project ideas raise safety issues in terms of: | + | <h2 id="r0" style="line-height: 1em;">Q1:Would any of your project ideas raise safety issues in terms of: |
researcher safety, public safety, or environmental safety?</h2> | researcher safety, public safety, or environmental safety?</h2> | ||
<div> | <div> | ||
| Line 94: | Line 95: | ||
<p> </p> | <p> </p> | ||
</p></div> | </p></div> | ||
| - | <h2 id="r1">Q2:Do any of the new BioBrick parts (or devices) that you made this | + | <h2 id="r1" style="line-height: 1em;">Q2:Do any of the new BioBrick parts (or devices) that you made this |
year raise any safety issues? If yes, did you document these issues in the | year raise any safety issues? If yes, did you document these issues in the | ||
Registry? how did you manage to handle the safety issue? How could other teams | Registry? how did you manage to handle the safety issue? How could other teams | ||
| Line 100: | Line 101: | ||
<div> | <div> | ||
<p> As a software team, we didn't make any | <p> As a software team, we didn't make any | ||
| - | BioBrick. and no safety issues happened from this.</p> | + | BioBrick. and no safety issues happened from this. For a software, the most |
| + | important safety concern is network safety. Our software can be used offline, so | ||
| + | it's safer in some way. Other software team should pay attention on the network | ||
| + | safety of their software.</p> | ||
</p></div> | </p></div> | ||
| - | <h2 id="r2">Q3:Is there a local biosafety group, committee, or review board at your institution? | + | <h2 id="r2" style="line-height: 1em;">Q3:Is there a local biosafety group, committee, or review board at your institution? |
If yes, what does your local biosafety group think about your project? | If yes, what does your local biosafety group think about your project? | ||
| Line 117: | Line 121: | ||
harmful substance or destroy anything. The Regulator Designer focus on the | harmful substance or destroy anything. The Regulator Designer focus on the | ||
design of regulatory elements of metabolic networks, It's also safety.<br> | design of regulatory elements of metabolic networks, It's also safety.<br> | ||
| - | |||
</p> | </p> | ||
</div> | </div> | ||
| - | <h2 id="r3">Q4:Do you have any other ideas how to deal with safety issues that | + | <h2 id="r3" style="line-height: 1em;">Q4:Do you have any other ideas how to deal with safety issues that |
could be useful for future iGEM competitions? How could parts, devices and | could be useful for future iGEM competitions? How could parts, devices and | ||
systems be made even safer through biosafety engineering?</h2> | systems be made even safer through biosafety engineering?</h2> | ||
| Line 146: | Line 149: | ||
</li> | </li> | ||
<li> | <li> | ||
| - | <a href="/ | + | <a href="https://2012.igem.org/Team:SYSU-Software/SecondEdition">Second Edition</a> |
| + | </li> | ||
| + | <li> | ||
| + | <a href="https://2012.igem.org/Team:SYSU-Software/Accomplishment">Accomplishment</a> | ||
</li> | </li> | ||
| Line 158: | Line 164: | ||
<ul> | <ul> | ||
<li> | <li> | ||
| - | <a href="/ | + | <a href="https://2012.igem.org/Team:SYSU-Software/Download">Source Code</a> |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
</li> | </li> | ||
<li> | <li> | ||
| Line 172: | Line 174: | ||
<li> | <li> | ||
| - | <a href="/ | + | <a href="https://2012.igem.org/Team:SYSU-Software/Contact">Email</a> |
</li> | </li> | ||
| Line 185: | Line 187: | ||
<ul> | <ul> | ||
<li> | <li> | ||
| - | <a href="">Questions</a> | + | <a href="https://2012.igem.org/Team:SYSU-Software/Faq">Questions</a> |
</li> | </li> | ||
<li> | <li> | ||
| - | <a href="">Troubleshooting</a> | + | <a href="https://2012.igem.org/Team:SYSU-Software/Faq">Troubleshooting</a> |
</li> | </li> | ||
<li> | <li> | ||
| - | <a href="">Uninstalling</a> | + | <a href="https://2012.igem.org/Team:SYSU-Software/Uninstalling">Uninstalling</a> |
</li> | </li> | ||
<li> | <li> | ||
<a href="">Contact Us</a> | <a href="">Contact Us</a> | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
</li> | </li> | ||
</ul> | </ul> | ||
| Line 251: | Line 239: | ||
<div class="wrapper clear"> | <div class="wrapper clear"> | ||
<div id="footer-about" class="footer-column"> | <div id="footer-about" class="footer-column"> | ||
| - | <h2>About</h2> | + | <h2> About</h2> |
<ul> | <ul> | ||
<li> | <li> | ||
| - | <a href="/ | + | <a href="https://2012.igem.org/Team:SYSU-Software/Team">Developers</a> |
</li> | </li> | ||
<li> | <li> | ||
| - | <a href="/ | + | <a href="https://2012.igem.org/Team:SYSU-Software/Contact">Contact Us</a> |
</li> | </li> | ||
</ul> | </ul> | ||
</div> | </div> | ||
<div id="footer-flickr" class="footer-column"> | <div id="footer-flickr" class="footer-column"> | ||
| - | <h2>Links</h2> | + | <h2> Links</h2> |
<ul> | <ul> | ||
<li><a href="http://www.sysu.edu.cn">SUN YAT-SEN University</a></li> | <li><a href="http://www.sysu.edu.cn">SUN YAT-SEN University</a></li> | ||
| - | <li><a href="http://lifescience.sysu.edu.cn/main/default/index.aspx">SYSU | + | <li><a href="http://lifescience.sysu.edu.cn/main/default/index.aspx">SYSU LifeScience</a></li> |
</ul> | </ul> | ||
</div> | </div> | ||
<div id="footer-search" class="footer-column"> | <div id="footer-search" class="footer-column"> | ||
| - | <h2>Facebook</h2> | + | <h2> Facebook</h2> |
</div> | </div> | ||
Latest revision as of 11:49, 26 September 2012
Safety
Contents |
Q1:Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?
No, just like other office software, it isn't involved with harmful material or attack. It only can be used to assisting viewing and analyzing biological data and designing regulatory elements of metabolic networks, which will scarcely cause any public or environmental problem. The software itself will not do harm to researcher either.
Q2:Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues? If yes, did you document these issues in the Registry? how did you manage to handle the safety issue? How could other teams learn from your experience?
As a software team, we didn't make any BioBrick. and no safety issues happened from this. For a software, the most important safety concern is network safety. Our software can be used offline, so it's safer in some way. Other software team should pay attention on the network safety of their software.
Q3:Is there a local biosafety group, committee, or review board at your institution? If yes, what does your local biosafety group think about your project? If no, which specific biosafety rules or guidelines do you have to consider in your country?
Yes, there are biosafety committee in our school, and Center for Disease Control and Prevention in our city. We consulted them, and they think our project is safety, the reasons are as follows:
There four part in the software. Among them,
Genome Browser,Network Illustrator and Simulator are all tools assisting
scientists to view or analyze biological data, which will not produce and
harmful substance or destroy anything. The Regulator Designer focus on the
design of regulatory elements of metabolic networks, It's also safety.
Q4:Do you have any other ideas how to deal with safety issues that could be useful for future iGEM competitions? How could parts, devices and systems be made even safer through biosafety engineering?
Set a risk evaluating system, give each BioBrick a safety mark, not by estimating by man, but by a calculating equation.
