Skip to content

Commit

Permalink
add links and tidy/restyle expectations
Browse files Browse the repository at this point in the history
  • Loading branch information
widdowquinn committed Sep 19, 2023
1 parent a5dc0f4 commit 6396857
Showing 1 changed file with 82 additions and 50 deletions.
132 changes: 82 additions & 50 deletions expectations.qmd
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Project Expectations"
description: |
General expectations of students and staff undertaking final year projects
General expectations of students and staff during final year projects
number-sections: true
about:
template: marquee
Expand All @@ -19,69 +19,101 @@ html:
anchor-sections: trueull
---

This may be your first time working on a scientific project, and/or your first time producing a scientific document (thesis). These guidelines are here to give you an idea of what to expect, and should be read in conjunction with the BM432 learning agreement [(MyPlace {{< bi link >}})]({{< var myplace.agreement >}}).
{
::: {.callout-important}
This may be your first time working on a scientific project, and maybe even your first time producing a scientific document (your project dissertation). The guide below is intended to help you understand what to expect, and should be read in conjunction with the BM432 learning agreement [(MyPlace {{< bi link >}})]({{< var myplace.agreement >}}).

::: {.callout-note}
Please read through these expectations and bring any questions or concerns that you would like to discuss with Dr. Pritchard to our first meeting.
:::

## Conducting Your Project

- Some [general advice about the group {{< bi link >}}](https://sipbs-compbiol.github.io/student/so_youre_a_project_student/)
- [How to avoid cognitive overload {{< bi link >}}](https://sipbs-compbiol.github.io/student/avoid-cognitive-overload/)


### Science:

- Maintain a lab notebook, either on paper or electronically. Human memory is fallible! Your notebook should be thorough and legible -- if you come back to it in a month's time, you should be able to reconstruct what you did.
- For each experiment, please write: Objective Background Methods, including deviations from established methods Results Conclusion
- Files should be saved with clear, concise file names and saved where you can find them again. **Back up your work frequently and in more than one place** -- you do not want to lose all of your data!
- At the end of the project, I expect you to provide me with the raw data files from your work: e.g. for a phylogenetic tree, I expect the .fasta file containing all of the sequences, the multiple sequence alignment of the sequences, and the .newick file for the tree. This is so that projects can be continued/expanded in future years.
- **Maintain a detailed record of your work (i.e. a lab notebook), either on paper or electronically.**
- All the projects run by our group are computational. You will probably find it easiest to maintain an electronic record.
- [Keeping a lab notebook to document your project {{< bi link >}}](https://sipbs-compbiol.github.io/BM432/notebooks/03-04-keeping_a_lab_notebook.html)

### Teamwork/collegiality:
::: {.callout-important}
- **Back up your work frequently and in more than one place** - you do not want to lose all of your data!
- If there are not three copies of your data/work (ideally in two physical locations), then it might as well not exist.
:::

- **At the end of the project, I expect you to provide me with the raw data files from your work.** For example:
- For a phylogenetic tree, I expect: the `.fasta` file containing the unaligned sequences; the multiple sequence alignment used to construct the tree (`.fasta`, `.msa`, etc.); and the `.newick` (or `.nex`) file for the tree. This is required so that projects can be continued and built upon in future years.
- You may find it most convenient to manage your project using standard computational biology tools, such as version control (e.g. `git` and GitHub). I would also find that convenient and strongly recommend it.

### Teamwork and collegiality:

- Science is a team effort and it benefits from people working together in groups -- we can accomplish more together than one person working alone can.
- Listen respectfully to each other, learn from each other, and contribute as you can.
- Be respectful of others' different life experiences, learn from them when appropriate, and contribute when appropriate. Do not insult or put down people who share their experiences. Harassment, sexism, racism, or exclusionary comments are not appropriate and prevent people from participating in science.
- Recognize that every person will bring strengths and weaknesses with them. Highlight each others strengths, and help each other overcome our weaknesses.
- If you find that you have made a mistake: listen, offer a genuine apology, and commit to learning and doing better.
- [Group Code of Conduct {{< bi link >}}](https://sipbs-compbiol.github.io/group/code_of_conduct)

- **I expect you to help each other**. In particular, some of you will have more experience than others in the group, when using computational and bioinformatics tools. You are all doing different projects, but you are using similar tools and techniques. I expect you to share knowledge and understanding kindly with one another.
- **Science is a team effort and it benefits from people working together in groups**. We can accomplish more together than one person working alone can.
- Listen respectfully to each other, learn from each other, and contribute as you can.
- Be respectful of others' different life experiences. Learn from them when appropriate, and contribute when appropriate. Do not insult or put down people who share their experiences.
- If you find that you have made a mistake: listen, offer a genuine apology, and commit to learning and doing better.

### Kindness:

- Be kind to yourself. Be mindful of your limits, and aware of the fact that you are still in the middle of a global pandemic -- give yourself credit for the hard work that you're doing every day.
- Be kind to others. Give them the benefit of the doubt when needed; remember that online communication often misses nuance or meaning. Remember that everyone is struggling right now and may not be able to be their best selves.
- Be patient. Science can be hard work -- things take longer to accomplish, particularly at first; you may need to repeat experiments or start over with a new dataset. This is all part of the process -- you are making progress, even though it may not be readily apparent.

### Communication:

- Clear, open, honest communication -- I cannot help if you don't let me know that there's a problem.
- Meetings at least once a week in person or via Zoom (individual and/or group meetings). Zoom etiquette: turning your camera, microphone on/off is completely up to you, no pressure either way.
- Between meetings, I'm available by e-mail to answer questions or you can schedule a drop-in Zoom (depending on our schedules).
- Don't be afraid to ask for help:
- Me (...this is literally my job!)
- Each other
- The Microbiology group
- Ask questions in your lectures/open office sessions
- Twitter (a great place to crowdsource science questions)
- **How to ask for help**: ... after Google, reading papers, looking at manuals and FAQs has proven unhelpful!
- Be detailed and specific! ("I tried it and it didn't work" is not a useful question).
- Explain what you were trying to do, exactly how you tried to do it, exactly what happened (e.g. what error message you got) -- include screenshots if they help to illustrate the problem. This will save a lot of time and back-and-forth e-mails
- Take ownership of your project: I am here to help and to guide you, but this is not my thesis (I have already done one!) Come prepared to meetings Think independently and critically Read broadly All of the above contributes to your project performance mark
- Don't be afraid to tell me that I'm wrong:
- Your data may well contradict my hypotheses or ideas
- You might find something in the literature that I wasn't aware of
- You may well have insights and clever thoughts that I won't have
- Doing science is about being able to challenge the accepted dogma and prove ideas wrong

## What you can expect from me:

- Kindness, team-work, and collegiality
- Advice and guidance on planning and carrying out your experiments
- Guidance on how to write a scientific document
- Feedback on drafts and practice presentation
- Good communication
- E-mail responses within 24h (I will do my absolute best)
- Feedback on project performance
- References
- **Be kind to yourself**. Be mindful of your limits, and aware of the fact that this is a world in crisis, with a myriad challenges.
- Give yourself credit for the hard work that you're doing every day.
- **Be kind to others**. Give them the benefit of the doubt when needed; remember that online communication often misses nuance or meaning.
- Remember that everyone is struggling right now and may not be able to be their best selves.
- **Be patient**. Science can be hard work. Things take longer to accomplish, particularly when you are first learning a technique. You may need to repeat experiments or start over with a new dataset. This is all part of the process.
- Be assured that you _are_ making progress, even though it may not feel that way at the time.

### Good Communication:

- [How to ask for feedback {{< bi link >}}](https://sipbs-compbiol.github.io/student/getting-good-feedback/)
- [How to ask good questions {{< bi link >}}](https://sipbs-compbiol.github.io/student/asking-good-questions/)
- **Be clear, open, and honest in your communication**

::: {.callout-caution}
I cannot help if you don't let me know that there's a problem.
:::

- We will meet at least once a week in person or via Zoom (individual and/or group meetings).
- Zoom etiquette: turning your camera, microphone on/off is completely up to you, no pressure either way.
- Between meetings, I'm available by email to answer questions or you can schedule a drop-in Zoom (depending on our schedules).
- **Don't be afraid to ask for help**. You have many resources to call on, including:
- Me (...this is literally my job!)
- Each other. **Please do talk to and help each other!** - we call this "_Peer Learning_" and it's deliberately part of the project. It's not cheating or plagiarism.
- Anyone else in the SIPBS CompBiol Group
- The Microbiology group
- Ask questions in your lectures/open office sessions
- [Stack Overflow](https://stackoverflow.com/), [Bioinformatics Stack Exchange](https://bioinformatics.stackexchange.com/) and other specialist sites
- Social Media (it can be a great place to crowdsource science questions, but it can also be a cesspool)
- **Take ownership of your project**. I am here to help and to guide you, but this is not my thesis (I have already done one!)
- Come to meetings prepared.
- Think independently and critically
- Read broadly

::: {.callout-note}
All of the above contributes to your project performance mark
:::

- **Don't be afraid to tell me that you think I'm wrong.** I'm a scientist. I'm probably wrong at least half the time.
- Your data may contradict my hypotheses or ideas. That's how science works.
- You will probably find something in the literature that I wasn't aware of. I'll be interested to hear about it.
- You may well have insights and clever thoughts that I won't have. You are closer to your project than I am, and that will generate insight.
- Doing science can involve challenges to accepted dogma, and the Scientific Method requires us to prove ideas (usually our own ideas!) wrong. Be bold.

## What you should expect from me:

- Kindness, team-work, and collegiality
- Advice and guidance on planning and carrying out your experiments
- Guidance on how to write a scientific document
- Feedback on drafts and practice presentation
- Good communication
- Email responses within a working day (I will do my absolute best)
- Feedback on project performance
- References

::: {.callout-note}
When naming me as a reference there's no need to ask for permission, but I do appreciate as much notice as possible. If you can send me your CV and a couple of points you'd like me to highlight, so much the better!
If you want to name me as a reference there's no need to ask for permission, but I do appreciate as much notice as possible. I want to encourage an employer to hire you/a course to take you on so, if you can send me your CV and a couple of points you'd like me to highlight, so much the better!
:::

::: {.callout-tip}
Expand Down

0 comments on commit 6396857

Please sign in to comment.