Difference between revisions of "Quantitative PCR"

From ImpVis Wiki
Jump to navigation Jump to search
(Created page with " ''This is a template which you can use to help get you started on the wiki submission. It is just intended as a guide and you may modify the structure to suit your project.'...")
 
Line 8: Line 8:
*''How was each person involved?''
*''How was each person involved?''
*''What rough dates did they contribute?''
*''What rough dates did they contribute?''
*Jaroslaw Ciba, Department of Physics.
*Thomas Travis, Department of Physics.
*Marcus Essam
*Jacky Zhu
*Anabel Varela Carver, Department of Surgery & Cancer. Staff partner from October 2021.
*Anabel Varela Carver, Department of Surgery & Cancer. Staff partner from October 2021.
*Joana Dos Santos, Department of Surgery & Cancer. Staff partner from October 2021.
*Joana Dos Santos, Department of Surgery & Cancer. Staff partner from October 2021.

Revision as of 17:00, 18 October 2021


This is a template which you can use to help get you started on the wiki submission. It is just intended as a guide and you may modify the structure to suit your project.

Contributors

  • Name and what department each person was in.
  • Student or staff partner?
  • How was each person involved?
  • What rough dates did they contribute?
  • Jaroslaw Ciba, Department of Physics.
  • Thomas Travis, Department of Physics.
  • Marcus Essam
  • Jacky Zhu
  • Anabel Varela Carver, Department of Surgery & Cancer. Staff partner from October 2021.
  • Joana Dos Santos, Department of Surgery & Cancer. Staff partner from October 2021.
  • Jon Krell, Department of Surgery & Cancer. Staff partner from October 2021.
  • Robert Kypta, Department of Surgery & Cancer. Staff partner from October 2021.

Aims & Learning Outcomes

  • Explain the motivation for your visualisation.
  • Introduce the subject of your visualisation.
  • Which module and year is it intended for and which setting (lecture or self study)?
  • List learning outcomes. E.g.: "After using this visualisation, students should be able to explain that..."

This visualisations is intended for self-study to support iBSc Cancer Frontiers Module 1 teaching (q-PCR principles, data analysis and application to an experiment involving cancer cells)

Intended Learning Outcome:

After using this visualisation, students should be able to explain how changes in Ct values from a q-PCR experiment relate to changes in the numbers of copies of a gene that a cell contains (for example, a cancer cell upon treatment with a drug).

Design Overview

  • What the final outcome was, how it looks, how it functions etc.
  • Include graphics.
  • Do not include justification or design progression, leave this for later sections.

Design Justification

Assessment Criteria

  • List your cohort's assessment criteria. You may want to number the assessment criteria so you can refer to them easily later.

Education Design

  • What Methods were considered to convey concepts?
  • Design progression, key choices with justifications.
  • How has feedback been incorporated.

Graphical Design

  • How were accessibility issues considered?
  • How was space used effectively?
  • Design progression, key choices with justifications.
  • How has feedback been incorporated.
  • How is the design intuitive?

Interaction Design

  • Choice of interactive element(s) that fit in organically with the visualisation [inspiration of choice might be from lecture/in-class activity or other sources] - Sliders/Buttons/Cursor (hover/click).
  • Keeping accessibility of interactive elements in mind during design phase.
  • Design progression, key choices with justifications.
  • How has feedback been incorporated.

Progress and Future Work

  • Is the design finalised?
  • Which pages have been uploaded to website?
  • Any ideas for future improvements.

Links

  • Link to GitHub repository for code in development:
  • Link to visualisation on ImpVis website (when uploaded):
  • Link to Collection on ImpVis website (when created):
  • Any other links to resources (Miro boards / notes pages / Google Docs etc):