-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
π§βπ» Redesign boxplot setup #10
Comments
One thing I'm picturing is a single main "quick view" boxplot where outputs are included roughly in order of when they were produced. This would make it easier for the developers to eyeball where a variation between pipelines was introduced. This doesn't necessarily need to replace the existing boxplots which are sorted by data type and can just be an addition. Example of the outputs in this one figure:
Important: Depending on the pipeline configuration, some of these outputs may not be present, so the boxplot script should be able to be flexible regarding this, while also catching when any of these outputs are supposed to be present, but are missing (or if the filepath matching failed). |
It would also be nice to separate out the participant data that use distortion/susceptibility correction into their own three sets of boxplots (but still keep the total conglomerate ones also):
|
@birajstha - from earlier conversation, check out @e-kenneally 's issues with the template-space preprocessed BOLD time series correlations not completing/showing. This is a good focus for a unit test as well. |
This issue has been resolved, will resume the original task. |
@birajstha I did notice they're also missing in the |
Adding another potential feature idea - it would also be nice if there was an easy interface to grab the individual correlations of each output for each participant for each config. Without having to dig. Ex. "Can I see the correlation of the |
File paths matching were failing causing this missing plot. They have been resolved by adding replacements in the YML file. |
Planning
No response
User interface changes
No response
Project sub-parts and estimates
Timeline notes
No response
Timesink notes
No response
Frustration notes
No response
Design decisions and notes
The text was updated successfully, but these errors were encountered: