Lab Course: Visualization and Medical Image Analysis
- Start: 26.04.2017, 15:30, I.80 VR-Lab (LBH)
- Dates: by arrangement
- Course number: MA-INF 2220 - Lab Visualization and Medical Image Analysis
- Curriculum: Master , B-IT Master Media Informatics
- Requirements: Knowledge from one of our classes is recommended.
In this lab, you will learn to implement state-of-the-art methods from the field of visualization or medical image analysis. Specific topics will be presented together with the Computer Graphics Seminar and Lab introduction on April 26, 2017 at 15h30 in LBH I.80. If you missed the introductory session but still want to do a lab, please contact Amin Abbasloo.
In this lab, you will learn to implement state-of-the-art methods from the field of visualization or medical image analysis. Specific topics will be presented together with the Computer Graphics Seminar and Lab introduction on April 26, 2017 at 15h30 in LBH I.80.
If you missed the introductory session but still want to do a lab, please contact Amin Abbasloo.
Guidelines for a strong lab
To successfully finish a lab in our group, you have to produce three main results:
A practical result. In most cases, this will be a software implementation of a method described in the scientific literature or by your advisor. You also need to conduct experiments to demonstrate the extent to which the implementation fulfills its purpose, and to investigate its limitations. Alternatively, in specific cases, the practical result might consist of getting one or several existing software packages to work, and performing a systematic evaluation. In any case, this is the most important part of the lab, and we will grade it based on how challenging it was to achieve the result, on its quality (correctness, efficiency, readability of your code), on how independently you worked and contributed your own ideas, as well as on how carefully you designed, conducted, and interpreted your experiments.
A written report. The report should describe the overall design of the software, provide the information that is required to use it, including dependencies (such as external libraries), and highlight the steps that took most of your time and effort. It should also present and interpret your experiments, and conclude with a clear statement what you achieved in the lab, and what might be left for potential future work. We recommend writing the report in LaTeX, since that is a useful skill for the MSc thesis; however, this will not affect your grade. Compared to a seminar report, the length is more flexible: Even though the typical range is 5-10 pages, this is not a strict requirement, and depends on your specific task and needs.
An oral presentation that should take 30 minutes, followed by answering questions about your lab. The presentation should contain an introduction that clearly explains what your topic is about and why it is important. Fellow students who have a similar background as you should be able to follow your presentation. A strong presentation makes use of the available time, but does not exceed it – in extreme cases, we have to cut you off. Your presentation should be supported by suitable media, such as projected slides. It is up to you how you create them (LaTeX, PowerPoint, other means). If it fits your topic, feel free to use other media also, such as the whiteboard or a live demo.
The practical result and written report have to be submitted before the presentation; we will tell you the exact dates well in advance. It is strongly recommended that you discuss your results and report with your direct advisor – who is usually one of our PhD students – and perform a practice presentation, at least one week in advance.
Write the report in your own words. In the “References” section, list all papers and resources that have helped you to complete the lab, and explain in the text what role they played. If you would like to use images, plots, or diagrams produced by others, or if you would like to cite one of your sources verbatim, you have to clearly mark which material has been copied, and from which source. The same applies to source code you might have used from open-source packages or other sources, including fellow students. If you copy source code, text, or any other material without clearly marking it, this will be considered as plagiarism and can lead to failing the module!
A lab amounts to around one third of the overall workload of a full-time semester, which means that you will not be able to complete a strong lab unless you work on it continuously throughout the semester – you cannot expect to do everything at the last minute. Finally, please keep in mind that a nice report and presentation will not make up for missing or poor results, but that a report that is extremely short or difficult to understand, or a chaotic presentation, can make it hard for us to fully appreciate the practical work that you have done.