In this blog post, we will cover how to install Tator on a GCP VM. The main trick is updating the domain to the virtual machine's public IP address after running the install script. This is necessary because by default the install script will discover the internal IP address only, and use that IP address for the load balancer, Kubernetes API server, and domain name. For the most part we simply need to run the install script and make one change to the Helm config file, but we will also cover VM setup in the GCP console.

Upcoming versions of Tator, specifically 0.2.18, utilize a cutting edge browser feature known as the WebCodecs API. Based on browser security, features such as WebCodecs API are turned off in insecure origins.

Our next release of Tator, version 0.2.14, will include support for Argo 3.

CVision AI is proud to be a founding member and contributor to FathomNet. This post will cover how we used Tator to help our collaborators contribute to FathomNet.

One of our objectives with Tator is to enable you to explore, visualize, and edit your data efficiently.

As we close in on our first versioned release of Tator, we have made several improvements to the layout of the annotation view.