First version of cut tuning with optuna #11
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
introduce various functionality, such as utils, I/O etc
the structure is not cast in stone of course, first attempt
wrap multiprocessing in one function
offer the user a user_config dictionary at each trial which can be
used to extract some (global) use case-specific configuration
allow 2 different signatures for objective
start making possible the usage of different samplers
cut tuning example
4 scripts provided to produce reference, optimisation, evaluation and
closure (see README in respective directory src/o2tuner_run)
NOTE The example is preliminary, might need improvements
Most functionality was added according to the needs of this example.
set max-line for flake8 to 150 (same as pylint)
add psutil and matplotlib as requirements
Overall, everything preliminary and up to discussion.