How to get help
Last updated
Was this helpful?
Last updated
Was this helpful?
how to get support from inside or outside the lab; schedule of routine training for new members; things that bear repeating like "always ask questions!"; how to make mistakes productively
Don't be afraid to ask Simon questions, he would rather be bombarded with questions than you struggle on your own. That being said, it is good to independently come up with a couple of potential solutions to a problem and perhaps identify what you think is the best route forward and then run this past Simon. This independent thought followed by checking with the PI will help you learn how to trust your instincts and become a strong independent researcher. If you find Simon is struggling to understand the problem, try drawing pictures!
For basic coding challenges (how to I update plots, how to load CSV files etc) the best way to get help is by posting a code snippet in the coding channel on Slack. Please use code formatting to make this easy to read.
For larger challenges the best way to get help is to make sure others can run your code and reproduce the problem. Sending files through Slack or e-mail may seem helpful but often means lots of work has to be done before your code can be run. The best way to share an example of your problem is through the development github. Here is how to share an error you're struggling with:
Pull the latest version of the Mitchell Lab Dev repository.
- If in a new folder:
git clone
- if in an existing folder containing the repo:
git pull
Create a new folder in the repo for your exaxmple
mkdir debuggingForJohnDoe
Copy the individual files you need to recreate your example into the folder.
Do not include programatically generated files.
If you are using CSV2Julia do not copy the model files, only copy the CSV files and make sure your example notebook builds the model files and includes them.
Do not include any unneccessary files such as results from previous runs.
Make sure your folder contains a single .ipynb file that can be run in its entirety by pressing "run all cells". The notebook should either return the error or plot all inconsistent results in a single run.
Test run your notebook in your newly created folder and make sure you see the error.
If in doubt highlight the problem with some text in a markup cell. People might debug at a time when you're not around to explain the problem.
Add your folder, commit and push your new folder to the repo
git add debuggingForJohnDoe
git commit -m "added a debugging example so others can help me debug"
git push
Let everyone know in the coding channel that there is a working example ready to be debugged.
Simon should be your initial point of contact for most help. This includes scientific, work-life questions and anything else you might need to succeed. Below are some additional resources available to you:
The ECR page directs you to specific support for postdoc/early career researchers ()
The doctoral college for PhD students (Doctoral College - ).
BSMS mentoring scheme provides a one-on-one mentor, at a more senior career stage to help you meet your career ambitions. Contact Valerie Shilling - or od@sussex.ac.uk for information.