Difference between revisions of "Team:Chalmers Gothenburg/Experiments/Flowcharts"
| Line 12: | Line 12: | ||
</head> | </head> | ||
| − | <body class="notebook"> | + | <body><div class="notebook"> |
<div id="header_navbar_wrapper"> | <div id="header_navbar_wrapper"> | ||
| Line 28: | Line 28: | ||
<div class="wrap-content-no-side-nav"> | <div class="wrap-content-no-side-nav"> | ||
| − | < | + | <h3>Flowcharts for laboratory work</h3> |
<p class="text">Flowcharts is a good way to visualize a whole process or an entire project. From the extraction of genome to transformation of the assembled construct. In the lab it sometimes is hard to keep track of what you are doing is going to be used for, especially when you are several people working in shifts on the same tasks. The flowchart allows for the whole lab to quickly see were in the process the specific task fits in and adapt the protocol after that. Having flowcharts also makes troubleshooting easier since you can overview an entire process and thus identify problems that might occur. Furthermore, this overview makes it a lot easier to research protocols and procedures and foresee potential bottlenecks.</p> | <p class="text">Flowcharts is a good way to visualize a whole process or an entire project. From the extraction of genome to transformation of the assembled construct. In the lab it sometimes is hard to keep track of what you are doing is going to be used for, especially when you are several people working in shifts on the same tasks. The flowchart allows for the whole lab to quickly see were in the process the specific task fits in and adapt the protocol after that. Having flowcharts also makes troubleshooting easier since you can overview an entire process and thus identify problems that might occur. Furthermore, this overview makes it a lot easier to research protocols and procedures and foresee potential bottlenecks.</p> | ||
| − | < | + | <h3>How to make them?</h3> |
<p class="text">Designing a flowchart is not an especially complicated process. The main question is what level of detail the flowchart should contain. This in turn depends on what purpose the flowchart has and what information the user might need. A more experienced person understands what intermediate steps that are excluded and thus won’t need such a level of detail as a beginner need. In turn the flowchart can contain a larger portion of the project. </p> | <p class="text">Designing a flowchart is not an especially complicated process. The main question is what level of detail the flowchart should contain. This in turn depends on what purpose the flowchart has and what information the user might need. A more experienced person understands what intermediate steps that are excluded and thus won’t need such a level of detail as a beginner need. In turn the flowchart can contain a larger portion of the project. </p> | ||
| − | < | + | <h2>Examples</h2> |
<a href="https://static.igem.org/mediawiki/2016/f/f8/T--Chalmers_Gothenburg--Biobricksubmissionflowchartpdf.pdf"><img src="https://static.igem.org/mediawiki/2016/a/ac/T--Chalmers_Gothenburg--Biobricksubmissionflowchart.jpg" width="250px"></a> | <a href="https://static.igem.org/mediawiki/2016/f/f8/T--Chalmers_Gothenburg--Biobricksubmissionflowchartpdf.pdf"><img src="https://static.igem.org/mediawiki/2016/a/ac/T--Chalmers_Gothenburg--Biobricksubmissionflowchart.jpg" width="250px"></a> | ||
<a href="https://static.igem.org/mediawiki/2016/b/ba/T--Chalmers_Gothenburg--Cloningflowchartpdf.pdf"><img src="https://static.igem.org/mediawiki/2016/b/bc/T--Chalmers_Gothenburg--Cloningflowchart.jpg" width="250px"></a> | <a href="https://static.igem.org/mediawiki/2016/b/ba/T--Chalmers_Gothenburg--Cloningflowchartpdf.pdf"><img src="https://static.igem.org/mediawiki/2016/b/bc/T--Chalmers_Gothenburg--Cloningflowchart.jpg" width="250px"></a> | ||
| Line 41: | Line 41: | ||
</html>{{:Team:Chalmers_Gothenburg/footer}}<html> | </html>{{:Team:Chalmers_Gothenburg/footer}}<html> | ||
</div> | </div> | ||
| − | </body> | + | </div></body> |
Revision as of 16:57, 15 October 2016
Flowcharts for laboratory work
Flowcharts is a good way to visualize a whole process or an entire project. From the extraction of genome to transformation of the assembled construct. In the lab it sometimes is hard to keep track of what you are doing is going to be used for, especially when you are several people working in shifts on the same tasks. The flowchart allows for the whole lab to quickly see were in the process the specific task fits in and adapt the protocol after that. Having flowcharts also makes troubleshooting easier since you can overview an entire process and thus identify problems that might occur. Furthermore, this overview makes it a lot easier to research protocols and procedures and foresee potential bottlenecks.
How to make them?
Designing a flowchart is not an especially complicated process. The main question is what level of detail the flowchart should contain. This in turn depends on what purpose the flowchart has and what information the user might need. A more experienced person understands what intermediate steps that are excluded and thus won’t need such a level of detail as a beginner need. In turn the flowchart can contain a larger portion of the project.
Examples
