Skip to content

Commit 46d4760

Browse files
authored
Update 2.3.1_research_question.md
1 parent f275f18 commit 46d4760

File tree

1 file changed

+41
-27
lines changed

1 file changed

+41
-27
lines changed

_episodes/2.3.1_research_question.md

+41-27
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,9 @@ teaching:
55
exercises: 480
66
questions:
77
objectives:
8-
- "Choose a type of project"
9-
- "Write down research questions and discuss them"
8+
- "Get acquainted with the state of the art of phage research"
9+
- "Choose one or more papers for inspiration"
10+
- "Write down 1 or 2 research questions"
1011
- "Make a plan on how to tackle the questions"
1112
keypoints:
1213
---
@@ -26,51 +27,64 @@ Here are a few papers that caught our eye, maybe they inspire you (feel free to
2627
- [High viral abundance and low diversity are associated with increased CRISPR-Cas prevalence across microbial ecosystems](https://www.sciencedirect.com/science/article/pii/S0960982221014615), by Meaden *et al* (2022)
2728
- [Viruses interact with hosts that span distantly related microbial domains in dense hydrothermal mats](https://www.nature.com/articles/s41564-023-01347-5), by Hwang *et al* (2023)
2829

29-
# Choose a type of project
30+
# Choose one type of project
3031

31-
To start, choose one type of project that better fits your interests:
32+
Choose one type of project that better fits your interests:
3233

33-
- Go into detail into analyses
34-
- Build a broader research proposal
34+
1. Go into detail into analyses
35+
2. Build a broader research proposal
3536

36-
Independently of which type of project you choose, document it in your lab book and final presentation in a comprehensive way. Make sure your methods and results connect back to your hypothesis/what you wanted to achieve.
37+
{:start='1'}
38+
1. This type of project is more hands-on. You might write your own script(s), run your own analyses and produce your own plots. The idea here would be to focus on one of the methods/analyses we covered in the course and to go deeper into the analysis. In any case, the question you want to address should be clearly defined.
3739

38-
## Detailed analyses
40+
An example: "What are the differences between functional annotation done with Pharokka and Genomad?".
3941

40-
In this type of project, you should be more hands-on. Write your own script(s), run your own analysis, produce your own plots, etc. The focus is on the method rather than on the biological questions. In any case, whatever you want to achieve should be clear and straightforward. An example: "What are the differences between functional annotation done with Pharokka and Genomad?".
42+
Below are what should be included in your documentation/presentation for project type 1
4143

42-
The following points should be clear in your final presentation and in your lab book:
44+
- A brief background on the topic
45+
- A workflow for the steps you plan to take
46+
- A rationale for why you will take those steps
47+
- What will be the inputs and outputs?
48+
- Which programs will (do you plan to) use?
4349

44-
- What you want to achieve
45-
- Steps to take (consider drawing a workflow)
46-
- Why you take these steps
47-
- Which data to use
48-
- Which programs will/do you use
50+
- What are your expected results?
51+
-
4952

50-
Note that hypotheses do not need be proven. We want to see from you as results:
53+
{:start='2'}
54+
2. This type of project is more in the style of a research proposal with a broader scope. You should focus on the biological questions and how to address them using viromics.
5155

52-
- Output (a table or a figure)
53-
- Interpretation of the output: what does the data tell you?
54-
- Does it answer your question? It does not have to. In a negative case, can you say what you might do differently next time
56+
Your hypothesis and aims should be clear and backed-up by the literature.
5557

56-
## Research proposal
58+
Below are what should be included in your documentation/presentation for project type 2
5759

58-
In this type of project, you should focus on the biological questions and design it as if you were writing a research proposal. Your hypothesis and aims should be clear and backed-up by the literature.
60+
- A brief background on the topic
61+
- Formulate your research question or hypothesis to test
62+
- What informed the question?
63+
- How would you address this question or test the hypothesis? (make a detailed plan)
64+
- Estimate the complexity of the problem
5965

60-
The following points should be clear in your final presentation and in your lab book:
6166

62-
- What is the question
63-
- What is the state of the art (backed up by the literature)
64-
- What informed the question (cite your sources)
65-
- Is it testable? How?
67+
68+
- expected results
69+
- Hypotheses don't need be proven - can be null hypothesis
70+
- If you choose to do the detailed analyses:
71+
- Generate an output (a table or a figure)
72+
- Interpretation of the output: what does the data tell you?
73+
- Does it answer your question? (It doesn't have to, you can say what you might do differently next time)
74+
75+
Presentation
76+
77+
- comprehensive
78+
- has to connect back to hypothesis
6679

6780
# Exercise
6881

82+
6983
> ## Exercise
7084
> 1. Once you have an idea of a research question, take some time to talk about your idea with your fellow students.
7185
> Often your initial idea can be further refined based on discussions with others.
7286
> 2. Make sure you check the literature: are there any papers that do something related to your question?
73-
> For research proposal: find the three papers that are the most closely related to your project, and use them to refine your question.
87+
> Find the three papers that are the most closely related to your project, and use them to refine your question.
7488
> 3. Make a plan for tackling your question(s).
7589
> The more detail you can add, the better.
7690
> Think about data sources, bioinformatic methods, possible outcomes, expectations, backup/follow-up plans, hypotheses, and interpretation.

0 commit comments

Comments
 (0)