-
Notifications
You must be signed in to change notification settings - Fork 97
Open
Description
I am getting the following error when I try to implement a custom stopping criterion. I used the stopping criterion code used in the documentation and I get the following error. Oddly, when I run this script locally, I do not get an error? I'm not sure why this issue is happening in the cluster.
Traceback (most recent call last):
File "/vortexfs1/apps/anaconda-5.1/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
self.run()
File "/vortexfs1/scratch/msantos/shift/scripts/comm-sync/lib/python3.6/site-packages/zoopt/algos/opt_algorithms/racos/asracos.py", line 158, in run
if stopping_criterion.check(self) is True:
File "scripts/zoopt_fn.py", line 24, in check
content_best_value = optcontent.get_best_solution().get_value()
AttributeError: 'Updater' object has no attribute 'get_best_solution'
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels