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

[Bug report] cocopp error with bbob-constrained data #2106

Closed
brockho opened this issue Apr 22, 2022 · 3 comments
Closed

[Bug report] cocopp error with bbob-constrained data #2106

brockho opened this issue Apr 22, 2022 · 3 comments
Assignees
Labels

Comments

@brockho
Copy link
Contributor

brockho commented Apr 22, 2022

Describe the bug
The postprocessing in current development branch does not work anymore with data sets from the bbob-constrained suite anymore (I used the one from here: #2094):

>> python -m cocopp rs.zip
Post-processing (1)
  Using 1 data set:
    rs.zip

Post-processing (1)
  loading data...
    archive extracted to folder .extracted_rs ...
Traceback (most recent call last):
  File "C:\Users\dimo\anaconda3\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\dimo\anaconda3\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\dimo\anaconda3\lib\site-packages\cocopp-2.6.1.11-py3.9.egg\cocopp\__main__.py", line 30, in <module>
    res = rungeneric.main(args)
  File "C:\Users\dimo\anaconda3\lib\site-packages\cocopp-2.6.1.11-py3.9.egg\cocopp\rungeneric.py", line 408, in main
    dsld = rungeneric1.main(alg, outputdir, genopts + ["-o", outputdir, alg])
  File "C:\Users\dimo\anaconda3\lib\site-packages\cocopp-2.6.1.11-py3.9.egg\cocopp\rungeneric1.py", line 72, in main
    dsList = DataSetList(alg)
  File "C:\Users\dimo\anaconda3\lib\site-packages\cocopp-2.6.1.11-py3.9.egg\cocopp\pproc.py", line 2149, in __init__
    self.processIndexFile(name, alg_name)
  File "C:\Users\dimo\anaconda3\lib\site-packages\cocopp-2.6.1.11-py3.9.egg\cocopp\pproc.py", line 2243, in processIndexFile
    self.append(ds)
  File "C:\Users\dimo\anaconda3\lib\site-packages\cocopp-2.6.1.11-py3.9.egg\cocopp\pproc.py", line 2293, in append
    i.computeERTfromEvals()
  File "C:\Users\dimo\anaconda3\lib\site-packages\cocopp-2.6.1.11-py3.9.egg\cocopp\pproc.py", line 1096, in computeERTfromEvals
    s += sum(self.maxevals[np.logical_not(succ)])
IndexError: boolean index did not match indexed array along dimension 0; dimension is 1 but corresponding boolean dimension is 2

@paulduf narrowed the error down to this commit 6294fda (everything works well before this), so it should be easy to fix?

It suggests that we, as soon as possible, add a test on some bbob-constrained data to the nightly build. [I will take care of that]

Your System (please complete the following information when it seems relevant):

  • Operating system: both on Windows and Linux
  • COCO version: latest development branch
  • Browser irrelevant
@brockho brockho added the bug label Apr 22, 2022
@brockho brockho changed the title [Bug report] please put your title here [Bug report] cocopp error with bbob-constrained data Apr 22, 2022
@nikohansen
Copy link
Contributor

First hunch: the attribute _lasttdatfilelines which is used to compute maxfgevals is only set after the above call of computeERTfromEvals.

@nikohansen nikohansen self-assigned this Apr 22, 2022
nikohansen added a commit that referenced this issue Apr 22, 2022
by postponing the call to computeERTfromEvals
@nikohansen
Copy link
Contributor

nikohansen commented Apr 22, 2022

I hope commit 6288ed3 fixes this, you maygit checkout this commit and test with data from the constrained testbed. Let me know whether it works for you.

nikohansen added a commit that referenced this issue Apr 22, 2022
by postponing the call to computeERTfromEvals
@brockho
Copy link
Contributor Author

brockho commented Apr 22, 2022

Yes, the commit works for me. Thanks!

Given that we now have a corresponding test in the nightly build (within the development branch), we should push this/these commit(s) there.

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

No branches or pull requests

2 participants