Use metadata to store information alongside SigOpt objects. For example, training/evaluation time, IP addresses, and tags. Metadata is a collection of user-provided key-value pairs that SigOpt stores on your behalf under the metadata field. Think of metadata as your annotation for a SigOpt object. You can include metadata when you create an object:
The Analysis page in the Experiment Dashboard allows you to plot metadata values of observations as axes in the Experiment History visualizations. This feature enables visualizing the relationship between metadata values and the metric value, as well as metadata values and other parameter values.
Specs
Metadata is a series of up to 100 key/value pairs. Keys can have a maximum length of 100 characters. Values must be non-null and can be numbers or strings, and string values can have a maximum length of 500 characters.
If the value of a Metadata item is None, SigOpt will ignore this item in the metadata. For example: {"ip": None} will be treated as an empty dictionary.
Metadata is extremely flexible and there are many different ways to use it.
Track information such as error codes and hostnames, which can be helpful in diagnosing issues within distributed systems.
Store IP information for suggestions while completing parallel evaluations of a model. Examining open suggestions will tell you at a glance which machines are currently tuning models, and can give a rough time estimate for how long a set of assignments has currently run for.
Tag experiments that are all tuning the same type of model.
Annotate observations with timing data. Use the Analysis page to see how long each model took to evaluate versus the value of the metric.
Example: Tracking Suggestions and Observations Using Metadata
When running SigOpt in parallel, one may be interested in tracking which worker (e.g., an EC2 instance on AWS) a Suggestion or Observation is running on. This can be useful, for instance, when a failed observation appears and you want to identify the corresponding failed worker.
Including metadata at Suggestion creation can be done via
Information stored in metadata will be displayed on the SigOpt Experiment webpage. If instance_id is passed in, the Suggestion tab in each Suggestion entry will include the associated instance_id. Likewise, under the History tab, the user can see all metadata passed in with any Observation. In particular if the user clicks on entries with failed Observations, they can see which instance_id is associated with that result(see example below).
To find the instance_id of an EC2 instance, the UNIX command is
If an instance crashes during a Suggestion computation, the user can reconnect to that instance and run the following commands to restart the open Suggestion(s) associated with that instance:
When generating plots on the SigOpt webpage, the user can choose fields from metadata as coordinates for plots. In particular, Experiment History, Full Experiment History, and Parallel Coordinates plots all include fields from metadata as possible choices for coordinates. The user can select and combine them with other coordinates to generate custom visualizations.