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
Is your feature request related to a problem? Please describe.
Following the refactoring recently introduced in #191, it is no longer possible to set the number of cpus used by DeseqDataSet when running the DefaultInference backend as DeseqDataSet keyword argument.
Currently, to set e.g. n_cpus=4 we must write something like
Adding n_cpus as an optional keyword argument in DeseqDataSet again, and potentially raise a warning if the inference method that is chosen cannot take n_cpus as an argument.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Following the refactoring recently introduced in #191, it is no longer possible to set the number of cpus used by
DeseqDataSet
when running theDefaultInference
backend asDeseqDataSet
keyword argument.Currently, to set e.g.
n_cpus=4
we must write something likeDescribe the solution you'd like
Adding
n_cpus
as an optional keyword argument inDeseqDataSet
again, and potentially raise a warning if the inference method that is chosen cannot taken_cpus
as an argument.The text was updated successfully, but these errors were encountered: