Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stopping criterion error #30

Open
miraSantos opened this issue Nov 1, 2024 · 0 comments
Open

stopping criterion error #30

miraSantos opened this issue Nov 1, 2024 · 0 comments

Comments

@miraSantos
Copy link

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'


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant