Skip to content

Conversation

@renesass
Copy link
Collaborator

@renesass renesass commented Dec 7, 2022

This version contains primarily the new intensifier changes.

Documentation

https://automl.github.io/SMAC3/development/

Required for release candidate

  • Intensifier rework:
    • Support for multi-threating
    • Consider trials in runhistory
  • SH/HB
    • Easier implementation
    • Consider trials in runhistory
  • Fix multi-tasking on macs
  • Update changelog
  • Update docs
  • Specify some docstrings (inconsistent API in runhistory)
  • Reach 87% test coverage
  • Benchmarking

Intensifier

  • Decide which trial to suggest next if we are waiting for all busy workers (try new config instead of new instance, seed pair of already evaluated config)
  • Should directly operate on the RunHistory (no process_results method anymore)
  • When should the model be trained? static approach: after n evaluated configs
  • If user provided instances, seeds in the RunHistory: Those are preferred to be evaluated first
  • get_next_config: Generator, yields a config. Count how many configs yielded inside the generator.
  • Intensifier: Generator, yield trial.
  • Get rid off t_intensify (does not work in multi-processing) -- what was the idea behind it? Make sure that the computation time of the surrogate model and the intensifier are balanced?

@renesass renesass added this to the v2.0.0 milestone Dec 22, 2022
@renesass renesass added enhancement documentation Documentation is needed/added. feature test Tests are needed/added. example labels Dec 22, 2022
@renesass
Copy link
Collaborator Author

Okay guys, I just made my last pass and fixed some last minute issues. Please have a look and confirm ASAP.

@renesass renesass self-assigned this Dec 30, 2022
# targets = np.log(y)
# model = RandomForest(
# configspace=_get_cs(X.shape[1]),
# ratio_features=1.0,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commented out bc should be tested in the RF repo? (Same for GP?)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's because Boston is not supported anymore... changing the dataset means changing all of the values

@renesass renesass merged commit 0a1dff4 into main Jan 7, 2023
github-actions bot pushed a commit that referenced this pull request Jan 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation is needed/added. enhancement example feature test Tests are needed/added.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.