Add MELODIC/AROMA figures to reports

[effigies]

Tabled in #539.

[chrisgorgo]

I made this on the plane last night:

What do you think @jdkent?

[chrisgorgo]

The assignments are random - just for the visualization purposes.

[jdkent]

This looks nice, the red/green classification makes it visually easy to distinguish noise and signal (if they were classified as such). Since this is such a large report, would it be given it's own page for visualization?

[chrisgorgo]

I would make it full scale to full width, but since the reports are HTML (not PDF) there are no "pages" per se.

[effigies]

Just as an aesthetic comment, I'd consider keeping the text in black, maybe coloring the "C". Definitely not a big deal, and I might be wrong, but I think that'd be a little easier to read.

[jdkent]

Sorry, I'm having trouble with words today. One issue I ran into when I was just trying to print the unaltered melodic report was the space allotted to the report was too small. fmriprep appeared to give each QC report the same amount of space, but the aroma report would need a variable amount of space depending on how many components were derived from melodic. I don't know if the space allotment is handled in reports.tpl or in reports.py, but that is separate issue from the aesthetic in the visualization.

[effigies]

I can try to find some time to look at how that works. If you want to start a quick feature branch that re-adds the reports, that would be a useful first step. I think what we may end up wanting to do is to generate an SVG that tiles the inputs, and then save that as a single reportlet to be included in the output.

[chrisgorgo]

I think we got it figured out in the mriqc reports. I'll try to get it working in FMRIPREP over the weekend.

…

On Jul 7, 2017 6:16 AM, "Chris Markiewicz" ***@***.***> wrote: I can try to find some time to look at how that works. If you want to start a quick feature branch that re-adds the reports, that would be a useful first step. I think what we may end up wanting to do is to generate an SVG that tiles the inputs, and then save that as a single reportlet to be included in the output. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#575 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOkpxqJKsKdCM4PH8q2C0lMfXfvZ-9zks5sLi-vgaJpZM4OIdg-> .

[oesteban]

We haven't talked much about ICA outputs in the testing plan. How are things in this front? Should we remove this issue from the 1.0.0-rc1?

[chrisgorgo]

I'm working on it. A PR should come in soon.

…

On Fri, Aug 4, 2017 at 10:28 AM, Oscar Esteban ***@***.***> wrote: We haven't talked much about ICA outputs in the testing plan. How are things in this front? Should we remove this issue from the 1.0.0-rc1? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#575 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOkp5MPq1_oV9J9FqTb-IK9hljuvbZLks5sU1TNgaJpZM4OIdg-> .