Google Cloud Datalabeling V1beta1 Client - Class State (0.6.3)

Reference documentation and code samples for the Google Cloud Datalabeling V1beta1 Client class State.

State of the job.

Protobuf type google.cloud.datalabeling.v1beta1.EvaluationJob.State

  Value: 0 
 

Generated from protobuf enum STATE_UNSPECIFIED = 0;

  Value: 1 
 

The job is scheduled to run at the configured interval . You can pause or delete the job.

When the job is in this state, it samples prediction input and output from your model version into your BigQuery table as predictions occur.

Generated from protobuf enum SCHEDULED = 1;

  Value: 2 
 

The job is currently running. When the job runs, Data Labeling Service does several things:

1. If you have configured your job to use Data Labeling Service for ground truth labeling, the service creates a Dataset and a labeling task for all data sampled since the last time the job ran. Human labelers provide ground truth labels for your data. Human labeling may take hours, or even days, depending on how much data has been sampled. The job remains in the RUNNING state during this time, and it can even be running multiple times in parallel if it gets triggered again (for example 24 hours later) before the earlier run has completed. When human labelers have finished labeling the data, the next step occurs.

If you have configured your job to provide your own ground truth labels, Data Labeling Service still creates a Dataset for newly sampled data, but it expects that you have already added ground truth labels to the BigQuery table by this time. The next step occurs immediately.

1. Data Labeling Service creates an Evaluation by comparing your model version's predictions with the ground truth labels. If the job remains in this state for a long time, it continues to sample prediction data into your BigQuery table and will run again at the next interval, even if it causes the job to run multiple times in parallel.

Generated from protobuf enum RUNNING = 2;

  Value: 3 
 

The job is not sampling prediction input and output into your BigQuery table and it will not run according to its schedule. You can resume the job.

Generated from protobuf enum PAUSED = 3;

  Value: 4 
 

The job has this state right before it is deleted.

Generated from protobuf enum STOPPED = 4;