Closed dimitri-rusin closed 7 months ago
This pull request DOES NOT use code from the following repo: https://github.com/ewarchul/cec
Although, it probably should. This is an idea for improvement. That code looks very nice and ordered. And probably contains fewer mistakes than the code committed via this pull request. Although, that code is C code, rather than proper C++ code.
But the code from https://github.com/ewarchul/cec actually does not contain CEC 2022 functions, only functions from CEC 2014, 2015, 2017, 2019, 2021.
They also have R code: https://github.com/ewarchul/cecs
This pull request DOES NOT use code from the following repo: https://github.com/ewarchul/cec
Although, it probably should. This is an idea for improvement. That code looks very nice and ordered. And probably contains fewer mistakes than the code committed via this pull request. Although, that code is C code, rather than proper C++ code.
But the code from https://github.com/ewarchul/cec actually does not contain CEC 2022 functions, only functions from CEC 2014, 2015, 2017, 2019, 2021.
They also have R code: https://github.com/ewarchul/cecs
https://github.com/yangyongkang2000/SEvoBench/blob/main/include/SEvoBench/cec2022.hpp
We are integrating functions from the CEC 2022 conference.
This is the paper:
Kumar, Abhishek; Price, Kenneth V.; Mohamed, Ali Wagdy; Hadi, Anas A.; Suganthan, P. N. "Problem Definitions and Evaluation Criteria for the CEC 2022 Special Session and Competition on Single Objective Bound Constrained Numerical Optimization." Technical Report, December 2021.
This repo has some code and the paper's PDF: https://github.com/P-N-Suganthan/2022-SO-BO
We have:
Let me know, if workflow scripts or something else should be removed or added.
Thank you!