Namespaces and fields#
In a Neptune object, such as a
run, fields and namespaces provide a folder-like structure for the metadata you log.
- A field represents a location for storing a piece of metadata.
- Fields can be organized under namespaces.
A field can be flat (stored at the root of the object) or nested (stored under one or more namespaces).
Field types and limitations#
Fields can contain values of various types: strings, dictionaries, floats, files, or artifacts. A field can also contain a series of values.
Namespaces (folders) can contain multiple fields of various types, but a field is always fixed to a type.
Good to know
When you assign some metadata to a new path in the Neptune object, that creates a field of a certain type.
If you reassign a value of the same type, it'll override the previous value stored in the field. Attempting to assign data of a different type to an existing field will result in an error.
In the above example, in order to upload a file, you'd need to change the
"parameters/momentum" path to something else. You could keep the "parameters" namespace, but at minimum, "momentum" should be changed to something different.
There are several options for storing metadata, such as simple assignment (
=) for single values,
upload() for uploading files, and
track_files() for tracking file metadata, to name a few. Each yields a different field type.
The most suitable logging method depends on:
- The data type of metadata you're logging.
The options you want for visualizing, storing, and interacting with the data in Neptune.
Example: For large files, you may want to simply track their metadata rather than upload them in full.