Difference between revisions of "Template:SYSU-Software/statics/html/Human Practice/Silver.html"

(Created page with "<div class="page-container"> <div class="header1"> Human Practice </div> <div class="header2"> Silver </div> <div class="content">...")
 
Line 1: Line 1:
 
<div class="page-container">
 
<div class="page-container">
 +
    <div class="last-page-identify" data-value="16"></div>
 
     <div class="header1">
 
     <div class="header1">
 
         Human Practice
 
         Human Practice
Line 5: Line 6:
 
     <div class="header2">
 
     <div class="header2">
 
         Silver
 
         Silver
 +
    </div>
 +
    <div class="header3">
 +
        Survey on needs.
 
     </div>
 
     </div>
 
     <div class="content">
 
     <div class="content">
−
         We first conducted a survey to understand the basic condition that the iGEM teams and professional researchers
+
         Our goal is to build a software that fits the needs of synthetic biologists, and is efficient and easy to use.
−
         are facing. Then we held meetings with several iGEM teams as SCUT-China, XMU-China, and SYSU-China to exchange
+
         To determine the specific functionalities we need to implement, we conducted a survey on researchers and other
−
        opinions about our projects and try to find a way to build a software that fits the users’demand and will be
+
        iGEM teams, including SCUT-China, Xiamen-China, and SYSU-Chin, and held a meeting with them to find out the
−
         used regularly.
+
         problems they face on a daily basis.
−
 
+
 
     </div>
 
     </div>
  
−
     <div class="header3">
+
     <div class="content">
−
         Meeting with other iGEM team
+
         For more information, please turn to <a href="javascript:void(0)" goto="XMU"> Collaboration pages </a>.
 
     </div>
 
     </div>
  
−
    We held a meeting with several iGEM teams as SCUT-China, Xiamen-China, and SYSU-China to exchange opinions about
+
     <div class="header3">Biolosafety and ethics
−
    our projects and try to find a way to build a software that fits the users’ demand and will be used regularly.
+
−
    For more information, please turn to <a href="javascript:void(0)" goto="XMU"> Collaboration pages. </a>
+
−
     <div class="header3">
+
−
        Biolosafety and Ethics
+
 
     </div>
 
     </div>
 
     <div class="header4">
 
     <div class="header4">
−
         Presentation and discussion inside our group
+
         Regular presentation and discussion
 
     </div>
 
     </div>
 
     <div class="content">
 
     <div class="content">
−
         We carried out inside activity and outside counselling to ensure the biosafety of our project. Intrinsically we
+
         We took steps to ensure the biosafety of our project. Presentations and discussions about biosafety knowledge
−
        had a group member giving a presentation about biosafety knowledge and hold a discussion about what action can
+
         were regularly held during the developing period.
−
         we take to ensure that our software is safe for the environment and society.
+
 
     </div>
 
     </div>
−
   
+
 
−
     <img src="TODO:">
+
     （figure1：暂无）
−
    <div class="caption">Figure 1:</div>
+
 
 
     <div class="content">
 
     <div class="content">
−
         During the discussion, we talked about how to let the users of our software use the registered parts and
+
         We discussed about validation and safety of registered parts and existing circuit data. Several ideas were
−
        existing circuit data responsibly. Our team members raised several ideas such as giving alert in the software
+
        raised, such as giving alert to inform the user about the potential risks and limit the unregistered users to
−
        to inform the user about the potential risks and limit the unregistered users to invoke the risky part. Other
+
        invoke the risky part. Members from other teams suggest that we rid the dangerous parts and circuits of the
−
        team members suggest that we wipe off the dangerous parts and circuits from our database. Given the Safety
+
         database.
−
         first principles , we adopted all these ideas.
+
 
     </div>
 
     </div>
−
     <img src="TODO:" />
+
     （figure2：暂无）
−
    <div class="caption">Figure 2:</div>
+
 
−
   
+
 
     <div class="header4">
 
     <div class="header4">
 
         Consulting Prof.LEE about dry lab and wet lab biosafety
 
         Consulting Prof.LEE about dry lab and wet lab biosafety
 
     </div>
 
     </div>
 
     <div class="content">
 
     <div class="content">
−
         Extrinsically, we got in touch with the university biosafety committee member Prof.LEE for safety information.
+
         We consulted Prof.LEE in the university biosafety committee about safety information. We introduced our
−
        We introduced our validating experiment and showed him the materials（parts and chassis microbes） and methods we
+
        validating experiment and showed him the materials（parts and chassis microbes）and methods we used. He stated
−
        used. He thinks that our experiment is almost risk free because all the parts we use are standardized and
+
        highly that our experiment is almost free of risk for all parts we had used were standardized and
−
         well-researched for potential danger. Previous experiment have proved the safety of such experiment. For dry
+
         well-researched, proved to be out of potential danger. For dry lab biosafety, he suggested that we could
−
        lab biosafety, he suggests that we could do something about the database and the authorization of using such
+
        enhance the constraints on using dangerous part in circuit design.
−
        parts.
+
−
 
+
 
     </div>
 
     </div>
−
     <img src="https://static.igem.org/mediawiki/2018/9/9e/T--SYSU-Software--Consulting.png" />
+
    ​​
−
     <div class="caption">Figure 3：Consulting  Prof.LEE for biosafety</div>
+
     <img src="https://static.igem.org/mediawiki/2018/9/9e/T--SYSU-Software--Consulting.png">
 +
     <div class="caption">
 +
        Figure 3: Consulting Prof.LEE for biosafety
 +
    </div>
 +
 
 
     <div class="header4">
 
     <div class="header4">
 
         Inspiration
 
         Inspiration
Line 67: Line 65:
 
         some circuits and parts from former iGEM teams, we also took biosafety into consideration, in other words, the
 
         some circuits and parts from former iGEM teams, we also took biosafety into consideration, in other words, the
 
         circuits and parts our software uses conform to the standard of biosafety.
 
         circuits and parts our software uses conform to the standard of biosafety.
−
          
+
         Our software ensures the safety of parts and circuits used in biological experiments by only including
 +
        standardized and well-researched parts and circuits in our database, meaning that we check for biosafety
 +
        whenever we add parts or circuits from former iGEM teams into our database. We have also put necessary
 +
        authorization constraints on our software to protect the database from being tampered with. In addition, We
 +
        give appropriate warning information whenever a part or circuit is requested by the user.
 
     </div>
 
     </div>
 +
 
     <div class="next-page-identify" data-value="18"></div> <!-- 这个是跳页标记 -->
 
     <div class="next-page-identify" data-value="18"></div> <!-- 这个是跳页标记 -->
−
   
+
 
 
</div>
 
</div>

Revision as of 16:41, 17 October 2018

       Human Practice

       Silver

       Survey on needs.

       Our goal is to build a software that fits the needs of synthetic biologists, and is efficient and easy to use.
       To determine the specific functionalities we need to implement, we conducted a survey on researchers and other
       iGEM teams, including SCUT-China, Xiamen-China, and SYSU-Chin, and held a meeting with them to find out the
       problems they face on a daily basis.

       For more information, please turn to <a href="javascript:void(0)" goto="XMU"> Collaboration pages </a>.
Biolosafety and ethics 
       Regular presentation and discussion

       We took steps to ensure the biosafety of our project. Presentations and discussions about biosafety knowledge
       were regularly held during the developing period.

   （figure1：暂无）

       We discussed about validation and safety of registered parts and existing circuit data. Several ideas were
       raised, such as giving alert to inform the user about the potential risks and limit the unregistered users to
       invoke the risky part. Members from other teams suggest that we rid the dangerous parts and circuits of the
       database.

   （figure2：暂无）

       Consulting Prof.LEE about dry lab and wet lab biosafety

       We consulted Prof.LEE in the university biosafety committee about safety information. We introduced our
       validating experiment and showed him the materials（parts and chassis microbes）and methods we used. He stated
       highly that our experiment is almost free of risk for all parts we had used were standardized and
       well-researched, proved to be out of potential danger. For dry lab biosafety, he suggested that we could
       enhance the constraints on using dangerous part in circuit design.

   ​​
   <img src="T--SYSU-Software--Consulting.png">

       Figure 3: Consulting Prof.LEE for biosafety

       Inspiration

       As a platform on which many biologists participate to solve problems together, we have the responsibility to
       guarantee the circuits our software recommends and parts the users search are safe, therefore, when we gained
       some circuits and parts from former iGEM teams, we also took biosafety into consideration, in other words, the
       circuits and parts our software uses conform to the standard of biosafety.
       Our software ensures the safety of parts and circuits used in biological experiments by only including
       standardized and well-researched parts and circuits in our database, meaning that we check for biosafety
       whenever we add parts or circuits from former iGEM teams into our database. We have also put necessary
       authorization constraints on our software to protect the database from being tampered with. In addition, We
       give appropriate warning information whenever a part or circuit is requested by the user.