sync() to ensure synchronous logging#
To ensure synchronous communication between multiple processes, you can make use of the
sync operations. These are available to any Neptune objects.
How they work#
The local representation is formed based on metadata tracking calls made with Neptune (such as
upload()). The Neptune server has the true representation based on all tracking calls.
sync()– synchronize the local representation with the server representation.
- In version control terms, it's like pulling changes from the remote. This is useful in cases when parallel processes are logging to the servers and you want to access a value logged by some other process.
wait()– wait for all tracking calls to reach Neptune before continuing execution.
- This ensures that all of the queued Neptune logging calls reach the servers before the script continues execution.
To combine the two operations, you can use
sync(wait=True) on a run or other Neptune object. It's equivalent to:
Fetching a value that is guaranteed to exist#
If you're fetching a value from a run that was logged earlier in the same process, or from another instance in a parallel setup, first run
sync(wait=True) so that the server and local object are in sync.
You can now fetch the parameter from the run:
- A variable logged by another process may not be immediately visible on the server.
If the script is not doing model training, you can initialize Neptune in the
syncconnection mode. This makes every method synchronous.
For details, see Using Neptune in different modes.
Copying parameters from a run to a model version#
Log the metadata and call
wait() on the run:
The server representation of the run now has the "parameters" dictionary assigned. The value of this field can be fetched and used elsewhere in your code:
Creating a version of a recently registered model#
Create a new model:
Wait for the model object to be created on the server:
Fetch the model ID and use it to create a model version: