HealthBioscienceIDEAS / demon-imaging-harmonisation

A Binder-ready GitHub repo to show the effects of using different scanners
1 stars 2 forks source link

DEMON ECR lecture "Harmonisation strategies for multi-centre imaging studies"

Binder

Overview

This lecture will cover various techniques for how to handle variability in imaging data arising from multi-site and multi-scaner acquisition. Differences in hardware, software and acquisition parameters between scanners can lead to diferences in the resulting image data. This lecture was developed as part of the Health and Bioscience IDEAS training programme, funded by UKRI Innovation Scholars (MR/V03863X/1) These differences include:

These differences between scanners can ultimately lead to differences in the outcome measures, so if an individual was scanned at site A and then again the next day at site B, there would be potential differences in the measurement. While of course some of these differences would simply be measurement error, there are also systematic differences between the sites that would lead to bias and/or differences in variability (heteroskedasticity). Methods that reduce or remove these sources of systematic error arising from multiple scanners/sites while leaving the biologically-relevant changes intact are often referred to as data harmonisation. There are many opportunities for harmonisation, from prospecitvely tuning the acquisition parameters from the different sites to ensure that the resulting images have properties that are as similar as possible to each other, to adaptive processing pipelines that harmoinse the images before analysis to adjusting for these differences between sites/scanners through statsitical models. Each approach has its place, with potential benefits and drawbacks, but they can also be used in a combined harmonisation strategy.

In the Jupyter notebook lectures included in this repository, we will:

Setup

This lecture is intended to be a Binder-ready repository (add links to Binder). This means that the repository with the Jupyter notebook will created as a Docker container and then accessible via the web. Thus it should not require any more requirements than a network connection and web browser.

If you are intereste in running this on your local environment, please investigate the local ennvironment page. The dependencies will be:

Thanks to the team behind the Software Carpentries courses on Introduction to Working with MRI Data in Python and other great courses on neuro MRI for their inspiration on how to setup teaching material in this manner.