Dan Handwerker

Good point on the `betas` estimate. I think this makes me double-down on how aggressive vs non-aggressive can be confusing language. I'm also realizing we've sometimes used "aggressive"/"conservative" to describe...

I like your tabs because they explain a bit more clearly what each includes. I'd lean into your tab suggestions more and use more mathy terminology rather than "aggressive" "non-aggressive"....

This isn't quite right but hopefully it helps explain. Accepted components X includes fluctuations A, B, C Rejected components Y includes fluctuations C, D, E Aggressive denoising removes Y without...

Not yet. I'm working on another acquisition project now, but I should follow up on at least getting some EPITI data.

I may be optimistic, but, **IF** types are added to the BIDS outputs branch #691, then modularize metrics #591, and then decision tree modularization #592, we'll have covered a substantial...

This might be a naive question, but could you clarify what nptying adds over the the numpy typing that's native to Python 3.8 and can be backported to 3.6? https://numpy.org/devdocs/reference/typing.html...

I overlooked that `typing-extensions` isn't a native library & would need to be added. That said, IF this meets our needs, then we can mark it as a dependency only...

I've been thinking how to set this up, but it might be useful to sketch out a general structure. We already have a [modularization project](https://github.com/ME-ICA/tedana/projects/2) and I added the two...

I just created those impact, effort, & priority labels. It seems like we're under-using labels in general. I'm going to apply the new ones to active PRs & issues. Labeling...

Just to get some case examples started: - **Long task designs** Separating slow BOLD from non-BOLD baseline drifts using multi-echo fMRI 10.1016/j.neuroimage.2014.10.051 Can potentially distinguish slow drifts from scanner noise...