|
|
| (33 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| | {{:Team:SUSTech_Shenzhen/removeStyles}} | | {{:Team:SUSTech_Shenzhen/removeStyles}} |
| | {{:Team:SUSTech_Shenzhen/themeCss}} | | {{:Team:SUSTech_Shenzhen/themeCss}} |
| − | {{:Team:SUSTech_Shenzhen/templates/nav}} | + | {{:Team:SUSTech Shenzhen/templates/page-header| |
| − | | + | url=wiki/images/1/1d/T--SUSTech_Shenzhen--Members.svg|size=100px|title=Countdown|subtitle=Run to fun!}} |
| − | {{:Team:SUSTech_Shenzhen/templates/page-header|
| + | |
| − | title=Project Overview|
| + | |
| − | subtitle=test page}}
| + | |
| − | | + | |
| − | {{:Team:SUSTech_Shenzhen/main-content-begin}}
| + | |
| − | | + | |
| − | = Abstract =
| + | |
| − | | + | |
| − | <!-- We are not satisfied to use the traditional ways to regulate gene expression, but to choose auodiogenetics and optogenetics to establish a high-efficiency regulation platform. Compared to the chemogenetics, sound and light are precise and nontoxic to our objects. Furthermore, the signals are easy to input into the system without delay.
We try to use a membrane mechanosensitive channel- transient receptor potential channel (TRPC5) to transform the audio wave energy as the input into cho-k1 cell. To select the cells which are sensitive to the specific wavelength, we mutate TRPC5 by molecular engineering and use calcium indicator(R-GECO) to quantify the intracellular calcium. Finally, we use the YFP as the downstream output signal to quantitatively analysis the regulatory ability of audiogenetics.
| + | |
| − | At the same time, we attempt to use opsin chrimson and coch-R expressed in C.elegans neurons, exploring a new way to study the neuronal response and learning process of worms. We choose a pair of sensor neurons AWA\AWB which are respectably and directly related to attractive and repulsive odorants. By using light-ray instead of chemicals, we can manufacture the alternative and consistent neuronal stimulus and observe its neuronal pathway in vivo.
| + | |
| − | | + | |
| − | Microfluidics is an important tool used in our experiments. Cells or C.elegans are seeded in the channels of microfluidics undergoing shear force controlled by microfluidics apparatus. We utilize shear stress as mechanical wave to impose pressure on cell membrane by changing the velocity of liquid flow in channels of microfluidics.
| + | |
| − | | + | |
| − | Another technology used is directed evolution. Here, we apply random PCR to acquire a large library of mutants of mechanosensitive channels which are then screened and selected based on the downstream pathways we design to meet our needs. -->
| + | |
| − | | + | |
| − | Audiogenetics is a useful tool for high-efficiency cell regulation. Compared to chemical genetics, it stimulates cells with better precision and less toxicity. Furthermore, signals are conveyed to target cells with little delay, leading to a shorter response time.
| + | |
| − | To achieve our goal of audiogenetics, membrane mechanosensitive channels (TRPC5 and Piezo) are chosen as receptors. Fluorescent calcium indicator (R-GECO) is employed to indicate cytoplasmic calcium level. Nuclear factor of activated T cells (NFAT) and YFP are used as downstream indicators to quantify the regulatory abilities.{{SUSTech_Image | filename=SUSTech_Shenzhen-ElementisLogo.jpg | caption=Elementis Logo}}
| + | |
| − | | + | |
| − | Microfluidic channels are also utilized in the pre-study in which shear stress, similar to sound waves, is applied on cell surface as signal input to explore the basic parameters. A sound generator is constructed to test whether sound can trigger the channels as expected. Additionally, we use directed evolution to improve channels' selectivity for specific sound frequency and their sensitivity to sound of lower intensity.
| + | |
| − | | + | |
| − | <!-- abstract 暂时 -->
| + | |
| − | | + | |
| − | | + | |
| − | = Welcome to iGEM 2016! = | + | |
| − | | + | |
| | <html> | | <html> |
| − | <a class="btn btn-success" href="javascript:(function()%7Bfunction readfiles(files) %7Bvar formData %3D new FormData()%3BformData.append('file'%2C files%5B0%5D)%3BformData.append('filename'%2C 'SUSTech_Shenzhen-'%2Bfiles%5B0%5D.name)%3BformData.append('format'%2C'json')%3BformData.append('token'%2Cmw.user.tokens.get( 'editToken' ))%3B%24.ajax(%7Burl%3A '%2Fwiki%2Fapi.php%3Faction%3Dupload'%2Ctype%3A 'POST'%2Cdata%3A formData%2Casync%3A true%2Csuccess%3A function (data) %7Bconsole.log(data)%3B%7D%2Ccache%3A false%2CcontentType%3A false%2CprocessData%3A false%7D)%3B%7Dvar dropzone %3D document.getElementById('wpTextbox1')%3Bdropzone.ondrop %3D function(e)%7Bconsole.log('drop')%3Be.preventDefault()%3Breadfiles(e.dataTransfer.files)%3Be.dataTransfer.setData('text%2Fplain'%2C e.dataTransfer.files%5B0%5D.name)%3Bvar %24txt %3D jQuery(dropzone)%3Bvar caretPos %3D %24txt%5B0%5D.selectionStart%3Bvar textAreaTxt %3D %24txt.val()%3Bvar txtToAdd %3D '%7B%7BSUSTech_Image %7C filename%3DSUSTech_Shenzhen-'%2Be.dataTransfer.files%5B0%5D.name%2B'%7D%7D'%3B%24txt.val(textAreaTxt.substring(0%2C caretPos) %2B txtToAdd %2B textAreaTxt.substring(caretPos) )%3B%7D%7D)()">Drag to bookmark bar</a> | + | <div class="team-content"> |
| − | </html>
| + | <div class="container"> |
| | | | |
| − | Your team has been approved and you are ready to start the iGEM season!
| + | <div class="row"><h1>Time to Wiki Freeze:</h1></div> |
| | + | <head> |
| | + | <link rel="stylesheet" href="/Team:SUSTech_Shenzhen/css/flip-clock-css?action=raw&ctype=text/css"> |
| | + | </head> |
| | | | |
| − | === Before you start === | + | <div class="clock"></div> |
| | | | |
| − | <html> | + | <script src="/Team:SUSTech_Shenzhen/js/flip-clock-js?action=raw&ctype=text/javascript"></script> |
| − | <a href="/Team:SUSTech_Shenzhen/Upload_Test" class="btn">Upload file using JS</a>
| + | <script type="text/javascript"> |
| − | <p> Please read the following pages:</p> | + | var clock = $('.clock').FlipClock((new Date("2016-10-20T12:00:00+08:00").getTime()-new Date().getTime())/1000, { |
| − | <ul>
| + | clockFace: 'DailyCounter', |
| − | <li> <a href="https://2016.igem.org/Requirements">Requirements page </a> </li>
| + | countdown: true |
| − | <li> <a href="https://2016.igem.org/Wiki_How-To">Wiki Requirements page</a></li>
| + | }); |
| − | <li> <a href="https://2016.igem.org/Resources/Template_Documentation"> Template Documentation </a></li>
| + | </script> |
| − | </ul> | + | </div> |
| | + | </div> |
| | </html> | | </html> |
| − |
| |
| − | === Styling your wiki ===
| |
| − |
| |
| − | You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project. {{SUSTech_Image | filename=SUSTech_Shenzhen-20160907,osmotic.png | caption=test}}
| |
| − |
| |
| − | While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.
| |
| − |
| |
| − |
| |
| − | === Wiki template information ===
| |
| − |
| |
| − | We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the <a href="https://2016.igem.org/Judging/Pages_for_Awards/Instructions">Pages for awards</a> link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!
| |
| − |
| |
| − | === Editing your wiki ===
| |
| − |
| |
| − | On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world!
| |
| − |
| |
| − | <p> <a href="https://2016.igem.org/wiki/index.php?title=Team:Example&action=edit"> </a>Use WikiTools - Edit in the black menu bar to edit this page</p>
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Tips ===
| |
| − |
| |
| − | <p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
| |
| − | <ul>
| |
| − | <li>State your accomplishments! Tell people what you have achieved from the start. </li>
| |
| − | <li>Be clear about what you are doing and how you plan to do this.</li>
| |
| − | <li>You have a global audience! Consider the different backgrounds that your users come from.</li>
| |
| − | <li>Make sure information is easy to find; nothing should be more than 3 clicks away. </li>
| |
| − | <li>Avoid using very small fonts and low contrast colors; information should be easy to read. </li>
| |
| − | <li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2016.igem.org/Calendar">iGEM 2016 calendar</a> </li>
| |
| − | <li>Have lots of fun! </li>
| |
| − | </ul>
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Inspiration ===
| |
| − |
| |
| − | <p> You can also view other team wikis for inspiration! Here are some examples:</p>
| |
| − | <ul>
| |
| − | <li> <a href="https://2014.igem.org/Team:SDU-Denmark/"> 2014 SDU Denmark </a> </li>
| |
| − | <li> <a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a> </li>
| |
| − | <li> <a href="https://2014.igem.org/Team:LMU-Munich">2014 LMU-Munich</a> </li>
| |
| − | <li> <a href="https://2014.igem.org/Team:Michigan"> 2014 Michigan</a></li>
| |
| − | <li> <a href="https://2014.igem.org/Team:ITESM-Guadalajara">2014 ITESM-Guadalajara </a></li>
| |
| − | <li> <a href="https://2014.igem.org/Team:SCU-China"> 2014 SCU-China </a></li>
| |
| − | </ul>
| |
| − |
| |
| − | === Uploading pictures and files ===
| |
| − | <p> You can upload your pictures and files to the iGEM 2016 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. <br />
| |
| − | When you upload, set the "Destination Filename" to <br><code>T--YourOfficialTeamName--NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
| |
| − |
| |
| − |
| |
| − | <div class="button_click" onClick=" parent.location= 'https://2016.igem.org/Special:Upload '">
| |
| − | UPLOAD FILES
| |
| − | </div>
| |
| − |
| |
| | | | |
| | | | |
| − | {{:Team:SUSTech_Shenzhen/main-content-end}}
| |
| | {{:Team:SUSTech_Shenzhen/wiki-footer}} | | {{:Team:SUSTech_Shenzhen/wiki-footer}} |
| | {{:Team:SUSTech_Shenzhen/themeJs}} | | {{:Team:SUSTech_Shenzhen/themeJs}} |
