Mark van der Wilk, April 2022
Please read these guidelines carefully. Keep in mind that I often supervise 10+ master's projects. Following these guidelines will make organisation a lot more efficient, and this will allow me to spend more time on what is actually important (and fun): supervising projects!
Your Individual Project is a significant undertaking where you develop your ability to perform independent work and research. Of course, you will be guided by myself and possibly a member of my research group.
Throughout the project, you will independently:
The main thing you can expect from your supervisors is a clear statement of what is to be investigated. This could include:
In addition, you can expect guidance from your supervisors throughout the project. Since the projects are all related to your supervisors' research, they are invested in ensuring that you get as far as possible, and are often enthusiastic to see the results you get. However, in principle, you should be able to make progress by yourself, and you may have to in periods where your supervisors are busy and cannot meet as regularly.
You can rely on roughly half an hour per week with your supervisor. This may be a bit more or less, depending on the needs of the project. If you have a PhD candidate co-supervisor, you may arrange additional meetings with them, if they have time.
You should treat your supervisor as a resource or a consultant on your project. The responsibility lies with you to make progress, but you should definitely consult your supervisor if you are stuck. Do keep in mind that you should use your meetings with your supervisor effectively. Time is limited and needs to be shared with many other master's students.
To use your meeting time optimally, follow the following tips:
Different courses have slightly different timetables, so it is your responsibility to decide when the project starts. Once you are ready to start, you should organise a first meeting with your supervisors.
For this first meeting, please prepare a Gantt chart that includes important dates like your final hand-in, and any intermediate deadlines. Include any ideas on tasks and milestones you need to do to make the project.
You should also be prepared to explain to your supervisors, what your current understanding of the project is. You should do this based on the project description, recommended papers, and perhaps by reading around key concepts that are mentioned. This is to ensure that everyone has a clear view on what should be done, and that your supervisors can steer you in the right direction if you do not have a clear view.
The most important outcome of the first meeting is that you leave with an understanding of what your project is supposed to achieve, and some initial suggestions for papers to read to solidify your understanding of the field.
It is really important to get a clear view of the goal of the project in the first few meetings. If you understand what your goal is, it will be much easier to for you to independently make progress.
It's a good idea to also do some of the recommended reading for the first meeting. Try to understand as much as you can, and come up with concrete questions to ask. It's normal to feel a bit lost at the start, but do try to understand as much as possible.
At a certain point in most projects, you will need compute resources. The Department of Computing provides quite a lot of useful resources. To fully see all that DoC offers, check out the CSG page. See our group's guide for more pointers.
Generally, it is a laborious process to get a good workflow for running machine learning experiments. You can help improve this by being proactive about asking questions, and improving our group's guide.