You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some inconsistency in the way different function accept/expect parallelization arguments. Some accept a dict called parallel, others accept divs and then look at the settings to see how many cores to uses, etc. Both are not great.
I am thinking parallel_kw and it takes a dict of keyword arguments and passes them on as needed.
The text was updated successfully, but these errors were encountered:
What if we just didn’t accept divs or any other parallelization-related kwargs? Since those are really part of global settings (which is why they’re stored in settings), they don’t belong in the function signature.
Then again, divs might be different since it helps avoid memory overflow on low-memory machines, so maybe we should keep it. But I still think the rest of the parallelization arguments don’t belong in the function signature.
We have some inconsistency in the way different function accept/expect parallelization arguments. Some accept a
dict
calledparallel
, others acceptdivs
and then look at thesettings
to see how many cores to uses, etc. Both are not great.I am thinking
parallel_kw
and it takes adict
of keyword arguments and passes them on as needed.The text was updated successfully, but these errors were encountered: