Dan Handwerker

Results 36 issues of Dan Handwerker

### Summary At the Nov 2022 dev call #897 we brought up the idea of adding instructions to our documentation on how to visually inspect components and consider reclassification.

documentation
effort: medium
impact: medium

### Summary @jsheunis made a great interactive interface for viewing parameter space options at: https://me-fmri-overview.herokuapp.com/ I think that's been down for a while. We should make sure that info is...

documentation
priority: medium
effort: medium
impact: medium

### Summary The documentation currently recommends running tedana before doing distortion correction or non-linear spatial alignments to a template and then has a note saying the other option is ok,...

documentation
priority: low
effort: low
impact: low

### Summary In the August 2023 dev call (#957) @BahmanTahayori commented that he had trouble tracking down a bug because it was not obvious that the ICA was re-run. The...

decomposition
priority: medium
effort: low
impact: low

### Summary In Decision Tree Modularization (#756), the functions in [`selection_nodes.py`](https://github.com/jbteves/tedana/blob/JT_DTM/tedana/selection/selection_nodes.py) were written so that it's possible to dry-run a tree and collect all metrics that would be needed to...

enhancement
priority: low
effort: medium
impact: medium

### Summary Current integration tests make sure consistent files are created and workflows run, but not the contents of the files. Additionally, there are a few parts of the `tedana`...

enhancement
testing
priority: medium
effort: high
impact: medium

### Summary As part of the review for #924, we noticed a divergence between the older MEICA decision tree and the one tedana has been using for years. There are...

priority: medium
effort: medium
impact: medium
breaking change

### Summary It is possible to use metrics in the component table that have n/a or None values for some components. With the added decision tree modularization #756, if a...

bug
priority: medium
effort: medium
impact: medium

### Summary After #756 is merged, some of the newly modularized functions could be better used in the `tedana.py` workflow. It should be possible to refactor that workflow to make...

enhancement
priority: low
refactoring
effort: high
impact: medium

### Summary Particularly with the addition of the modularization decision tree #756, there are places where similar things are given different names in various parts of the codebase. This might...

priority: low
refactoring
effort: medium
impact: low