User Case
Last updated
Last updated
Once you have installed the sigopt.hyperopt
client and have configured your environment for SigOpt, you are ready to seamlessly track your Hyperopt executions as . The tracking is done using Hyperopt’s concept of . Shown below are three examples of how to do this.
This mode uploads all Trials to SigOpt in a single API request after the optimization loop completes. There are two main use cases:
When iterations are evaluated quickly and the time to complete API requests is non-negligible.
When evaluations must be done offline, and an API request cannot be made within the optimization loop. In this case the upload_trials
function will need to be called from a machine with the ability to execute HTTPS requests.
This mode uploads each trial immediately after the objective evaluation. SigOptTrials replaces the Hyperopt Trials object in this integration.
Limitations: Only trial status, numerical values in trial result, and parameters of trial are saved in SigOpt.
All Hyperopt algorithms can be parallelized using either or . Both alternatives to Hyperopt’s base Trials can be wrapped with the SigOptTrials object. Here is the example from Hyperopt’s documentation reworked to log results contained in MongoTrials to SigOpt.