Should parallelization be handled upstream?

[arokem]

This is a suggestion to simplify this:

eddymotion/src/eddymotion/model/base.py

Line 160 in b1f70cc

with Parallel(n_jobs=n_jobs) as executor:

We are in the midst of some work to parallelize model fitting in DIPY itself: dipy/dipy#2593, which would benefit all downstream uses of these models, including here. I wonder whether we should aim to use these methods as implemented there (e.g., by passing through parallelization kwargs to DIPY's multi-voxel parallelization methods), instead of implementing that separately here.

[oesteban]

Yes :)

[arokem]

OK - well - let's keep this open if that's fine by you, so that we remember to refactor that code once the parallelization code is incorporated into DIPY (hopefully in the upcoming release).

[arokem]

Good news! dipy/dipy#2593 got merged 😄

[arokem]

Actually, reopening, because we still need to remove the parallelization code from here.