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
PR #140 introduced a feature for the MultiprocessingEvaluator to take a negative input for n_processes, which initialize the evaluator with the cpu_count minus that negative integer, leaving that number of cores free.
In 7dd1610 this code was refactored, introducing a bug that broke the negative-integer input functionality. When a negative integer is inputted, a AttributeError: 'MultiprocessingEvaluator' object has no attribute 'n_processes' was created.
The bug was caused by self.n_processes begin used instead of n_processes, where in earlier code self.n_processes was set equal to n_processes earlier in the process.
Unfortunately this bug landed in the EMAworkbench 2.2.0 release.
The text was updated successfully, but these errors were encountered:
all code for processes is now contained in the init and an extra check for windows is added were the max number of processes cannot be higher then 61 at the moment (is still true in python 3.10)
EwoutH
changed the title
Number of processes in the MultiprocessingEvaluator is broken.
Negative input values for n_processes in the MultiprocessingEvaluator result in fatal errors
Oct 5, 2022
PR #140 introduced a feature for the MultiprocessingEvaluator to take a negative input for
n_processes
, which initialize the evaluator with thecpu_count
minus that negative integer, leaving that number of cores free.In 7dd1610 this code was refactored, introducing a bug that broke the negative-integer input functionality. When a negative integer is inputted, a
AttributeError: 'MultiprocessingEvaluator' object has no attribute 'n_processes'
was created.The bug was caused by
self.n_processes
begin used instead ofn_processes
, where in earlier codeself.n_processes
was set equal ton_processes
earlier in the process.Unfortunately this bug landed in the EMAworkbench 2.2.0 release.
The text was updated successfully, but these errors were encountered: