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

Remove backend options from the Everest configuration #9773

Closed
verveerpj opened this issue Jan 16, 2025 · 0 comments · Fixed by #9899
Closed

Remove backend options from the Everest configuration #9773

verveerpj opened this issue Jan 16, 2025 · 0 comments · Fixed by #9899

Comments

@verveerpj
Copy link
Contributor

verveerpj commented Jan 16, 2025

Is your feature request related to a problem? Please describe.
In the Everest configuration, both the optimization and samplers sections have a backend option. This is used to specify which plugin/backend should be used to look for algorithms/methods that user specifies with the algorithm or method keys. The backend is not strictly necessary anymore, since ropt will search through all its available backends to find an algorithm/method. Further, if desired, the backend can be specified by prefixing the algorithm/method keyword like this: scipy/slsqp. Therefore this keyword can be removed.

Describe the solution you'd like
The keyword should be deprecated and eventually removed. The documentation should clarify how algorithms/methods are found.

Describe alternatives you've considered
N/A

Additional context
Implementation should be straightforward, since ropt already uses this approach.

@verveerpj verveerpj moved this to Todo in SCOUT Jan 16, 2025
@verveerpj verveerpj added improvement Something nice to have, that will make life easier for developers or users or both. configuration and removed feature improvement Something nice to have, that will make life easier for developers or users or both. labels Jan 16, 2025
@yngve-sk yngve-sk self-assigned this Jan 29, 2025
@yngve-sk yngve-sk moved this from Todo to In Progress in SCOUT Jan 29, 2025
@yngve-sk yngve-sk moved this from In Progress to Ready for Review in SCOUT Jan 29, 2025
@verveerpj verveerpj moved this from Ready for Review to Reviewed in SCOUT Jan 29, 2025
@verveerpj verveerpj moved this from Reviewed to Ready for Review in SCOUT Jan 29, 2025
@github-project-automation github-project-automation bot moved this from Ready for Review to Done in SCOUT Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants