Summary

Most importantly, QMtools works on the group results of MRIQC to help compare intra-group and inter-group values. This can help you identify which datasets are appropriate for further analysis.

Less critically, QMtools is one of many evolving solutions to the problem of finding good quantitative and qualitative measures of quality, and making consistent and reasonable choices about what data to reject.

Caution!

● For your own data, the easiest choice is to use the qmtools-support directory.
● Put your input files in the expected directories (e.g., input for qmtraffic should be in the *inputs* subdirectory).
● Make calls to the scripts from the qmtools-support directory.
● Unique report names will be generated automatically. If you choose to create your own report name, don't use the same report name more than once (as you risk mixing old and new data).
● On the HPC, call the apptainer scripts instead of the Docker scripts (e.g., qmtraffic_hpc instead of qmtraffic).
● Because these scripts are not implemented internally as SLURM jobs, use an interactive session (an interactive desktop is probably best so you can see the resulting reports).

🟢 QA & QMtools 2: Pr