SMAC3
SMAC3 copied to clipboard
Remove Scenario
- [ ] 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?
Placeholder: List how old variables are called
What's the issue here with ConfigSpace?