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

Release 0.2.5rc #980

Merged
merged 303 commits into from
Aug 3, 2022
Merged

Release 0.2.5rc #980

merged 303 commits into from
Aug 3, 2022

Conversation

notoraptor
Copy link
Collaborator

@notoraptor notoraptor commented Aug 2, 2022

Description

Release v0.2.5

🏗 Enhancements

🐛 Bug Fixes

📜 Documentation

🧰 Maintenance

bouthilx and others added 30 commits June 20, 2022 15:20
[dashboard] Display trials for selected experiment in Database page
Why:

When upgrading the DB to support index of (trial.id, trial.experiment),
the DB will end up with a mixed format for the trial ids. The previous
ids (_id) where the hash of the trials. It will now rely on the DB to
generate the next _id. Thus, it will have string index mixed with
integer values. It is best to keep ids as they were to better support
backward compatibility (and Oríon version down-grade), so we should
support mixed indexes. The bug was confusing anyway.

How:

Only consider integer indexes when inferring next id to use.
…l_hash

Remove experiment from Trial hash
If the list of choices contains multiple types, numpy's RNG will cast
all values to the type of the first item.
Why:

When the trial has a parent, it means it should start from the same
working_dir state. We need to fetch the parent trial and copy its working
dir to the current trial's working dir.

How:

The runner now has a new argument, a callable that will be executed
before a trial is submitted to the executor. By default this callable
will take care of copying parent trial working_dir to child trial
working dir, or simply create the working dir if the trial has no
parent.

If the callable fails, the exception is caught and delayed to be caught
again during the executor's execution of the trial. This makes it
possible to handle these trials the same way as if they crashed during
trial execution rather than during trial preparation.
Delaunay and others added 26 commits July 28, 2022 12:38
Co-authored-by: Xavier Bouthillier <xavier.bouthillier@gmail.com>
It was previously removed in PR Epistimio#903 because the Consumer is not
supposed to create the directory anymore. Merging latest develop branch
reintroduced it.
Pass algo object instead so that random state can be updated at end of
with-clause.
Add configspace conversion

Co-authored-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Co-authored-by: Xavier Bouthillier <xavier.bouthillier@umontreal.ca>
Co-authored-by: Fabrice Normandin <fabrice.normandin@gmail.com>
Since release v0.6.0 of pymoo (https://github.com/anyoptimization/pymoo/releases/tag/0.6.0),
HEBO's acq_optimizers fail to import because of an ImportError during the module's own imports.
Fix PBT issues with working dir and promotion of max fidelity trials
@bouthilx bouthilx merged commit 38f2fed into Epistimio:master Aug 3, 2022
@notoraptor notoraptor deleted the release-0.2.5rc branch August 3, 2022 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants