Taylor Salo

I'll move forward with issues in fMRIPrep once interested folks over there are able to respond (so far there haven't been many replies to my comments). The idea of applying...

The relevant issues are https://github.com/poldracklab/fmriprep/issues/1784 and https://github.com/poldracklab/fmriprep/issues/1010.

Alternatively, what if we removed the t2smap workflow altogether and just added a `--no-denoise` argument to the tedana workflow that, if set, would stop after writing out the optimally combined...

Once I started working on the first approach I realized that there would still be a lot of unnecessary duplication and opportunities for one method to end up outdated compared...

If we move the core of t2smap into a separate function that is called by both the t2smap CLI and tedana workflow, then that function will likely include the following...

Earlier this week `numpy` didn't have a 3.10-compatible release, and it looked like it might be up to a month before they make it.

I still need to change which maps are required for the reports, but are we happy with the output changes overall?

The `black` configuration info should all be in `pyproject.toml`. https://github.com/ME-ICA/tedana/blob/4d5c6456d66c6badea7aa3730130756db286a52d/pyproject.toml#L1-L5 However, we also have our [`flake8` settings set up to be compatible with `black`](https://black.readthedocs.io/en/stable/guides/using_black_with_other_tools.html#flake8), so that might also come into...

In NiMARE trying out Python 3.10 failed. I don't even know what's happening here... Why would it freeze like that?

It looks like [v1.21.4](https://github.com/numpy/numpy/releases/tag/v1.21.4) supports 3.10.