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.

Sign up for GitHub

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

Jump to bottom

Remove Scenario #860

Closed
3 tasks
renesass opened this issue Jun 30, 2022 · 2 comments · Fixed by #875
Closed
3 tasks

Remove Scenario #860

renesass opened this issue Jun 30, 2022 · 2 comments · Fixed by #875
Labels
enhancement
Milestone
v2.0.0

Comments

@renesass
Copy link
Collaborator

renesass commented Jun 30, 2022 •
edited
Loading

  • Eventually rename scenario to config (defining objectives, determinstic behaviour, limitations, how many runs should be executed, etc.)
  • Fix multiple names/variables with the same meaning
  • Remove/replace scenario from/in the main code (scenario was written for CLI mainly)

Important: Scenario was designed for reproducability in mind. We should keep that.
Question: How to deal with configspace? Put it in scenario?
@renesass renesass added this to the v2.0.0 milestone Jun 30, 2022
@renesass renesass changed the title Removing Scenario Remove Scenario Jun 30, 2022
@renesass
Copy link
Collaborator Author

Placeholder: List how old variables are called

@renesass renesass mentioned this issue Jun 30, 2022
Closed
@eddiebergman
Copy link
Contributor

What's the issue here with ConfigSpace?

@renesass renesass linked a pull request Aug 5, 2022 that will close this issue
Version 2.0.0a1 #875
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
SMAC board
Status: Done
Milestone
v2.0.0
Development

Successfully merging a pull request may close this issue.

Version 2.0.0a1 automl/SMAC3
2 participants
@renesass @eddiebergman