iGEM 2020 — Team UMaryland

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UMaryland/Notebook

# Notebook

Document the dates you worked on your project. This should be a detailed account of the work done each day for your project.

### What should this page have?

* Chronological notes of what your team is doing.
* Brief descriptions of daily important events.
* Pictures of your progress.
* Mention who participated in what task.

### Inspiration

You can see what others teams have done to organize their notes:

* [2018 Munich](https://2018.igem.org/Team%3AMunich/Notebook)
* [2014 ATOMS-Turkiye](https://2014.igem.org/Team%3AATOMS-Turkiye/Notebook)
* [2014 Tec Monterrey](https://2014.igem.org/Team%3ATec-Monterrey/ITESM14_project.html#tab_notebook)
* [2014 Kyoto](https://2014.igem.org/Team%3AKyoto/Notebook/Magnetosome_Formation#title)
* [2014 Cornell](https://2014.igem.org/Team%3ACornell/notebook)

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UMaryland/Engineering

# Engineering Success

This year, due to the pandemic we were unable to get into a lab. We wanted to follow the engineering design process very closely as a result of this and aimed to create a very solid design which we could hopefully test out in a lab next year. A summary of the engineering design steps we undertook are below:

Research → Imagine → Design → Build → Test → Learn → Improve → Research...

Research: We used the Book BioBuilder (ISBN: 978-1491904299) as well as researched many past projects to come up with several wide ranging ideas for our project, we ultimately chose Covid-19 although we had a host of other ideas.

Imagine: We imagined a system where we could test detect the virus *in vivo* . However, after designing such a system we realized that there were just too many complications in getting any eukaryotic cell to engulf a protein such that it could be detected.

Design: We went back to the drawing board and decided on an *in vitro* test, but we wanted to make sure it could overcome some of the shortcomings of the current testing crisis that was gripping the country. We decided on a split protein, dCas system.

Build: We used modeling (pyMOL) to get a good understanding of the final design and we used other calculations to get a grasp on our reaction and how it would work. For example, we used enzyme kinetic calculations to decide between using a split luciferase system vs a split Beta-Lactamase system. pyMol was used to decide which dCas13 ortholog to use, as we considered where the linker protein sequence would go. We also used the protein modeling to inform us on where to split the Beta-Lac enzyme for optimal enzyme activity.

When we get into a lab, we hope to actually test our plasmid design and actual test. Based on the results of these tests, such as whether we can successfully transform bacteria (Blue/White Screening), whether the dCas13 is binding to synthetic mRNA (binding Assay), and measuring the background activity of the enzyme, we would learn and improve our design further.

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UMaryland/Experiments

# Experiments

Describe the research, experiments, and protocols you used in your iGEM project. These should be detailed enough for another team to repeat your experiments.

If you made Parts this year, please remember to put all information, characterization, and measurement data on the Part's Main Page on the [Registry](http://parts.igem.org/Main_Page).

### What should this page contain?

* Protocols
* Experiments

### Inspiration

* [2014 Colombia](https://2014.igem.org/Team%3AColombia/Protocols)
* [2014 Imperial](https://2014.igem.org/Team%3AImperial/Protocols)
* [2014 Caltech](https://2014.igem.org/Team%3ACaltech/Project/Experiments)

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UMaryland/Results

# Results

You can describe the results of your project and your future plans here.

### What should this page contain?

* Clearly and objectively describe the results of your work.
* Future plans for the project.
* Considerations for replicating the experiments.

### Describe what your results mean

* Interpretation of the results obtained during your project. Don't just show a plot/figure/graph/other, tell us what you think the data means. This is an important part of your project that the judges will look for.
* Show data, but remember **all measurement and characterization data must also be on the Part's Main Page on the [Registry](http://parts.igem.org/Main_Page).** Otherwise these data will not be in consideration for any medals or part awards!
* Consider including an analysis summary section to discuss what your results mean. Judges like to read what you think your data means, beyond all the data you have acquired during your project.

### Project Achievements

You can also include a list of bullet points (and links) of the successes and failures you have had over your summer. It is a quick reference page for the judges to see what you achieved during your summer.

* A list of linked bullet points of the successful results during your project
* A list of linked bullet points of the unsuccessful results during your project. This is about being scientifically honest. If you worked on an area for a long time with no success, tell us so we know where you put your effort.

### Inspiration

See how other teams presented their results.

* [2014 TU Darmstadt](https://2014.igem.org/Team%3ATU_Darmstadt/Results/Pathway)
* [2014 Imperial](https://2014.igem.org/Team%3AImperial/Results)
* [2014 Paris Bettencourt](https://2014.igem.org/Team%3AParis_Bettencourt/Results)