Inputs
Within the Inputs tab, you will find information to help you get a good overview of the inputs inside the request and their current status. Please see the section Key conceptsο»Ώ for some essential background information. We'll revise the main parts also below.
An input is a set of sensor data you want to have annotated in a request. It usually consists of at least one image/frame. It can also contain images from several cameras, a point cloud, a video, or a sequence of images. A request input goes through the annotation, and sometimes the review workflow before its annotation is Delivery Ready. On its way through the request, each input gets treated by Annotate, Correct, or Review Tasks.
At a given time, the input is part of a specific workflow stage within the request's workflow. You might be familiar with the stages from the Summaryο»Ώ page.
This table shows each input and high-level information about it. In the section below, we will describe its columns and their possible values in further detail.
The identifier given to the input by the user or process uploading the input. It's different from the Scene UUID.
Shows which stage of the annotation workflow the input currently is in. Sorting this column will sort according to the order stages order in the annotation workflow.
The workflow stages are:
Production
- Not started Inputs that are waiting to be annotated.
- Annotation: Annotate* Inputs that are being annotated using annotate tasks.
- Sampled QA: Quality Assurance* Annotated inputs waiting to be or currently are being quality assured as a part of the annotation phase CQC. It also includes inputs that are waiting for a quality decision based on the outcome of sampled quality assurance.
- Correction: Correct* Annotated inputs waiting to be or currently being quality assured using correction tasks.
- Review: Review Annotated inputs that are waiting to be or currently are being reviewed.
- Review: Correct Annotated inputs that got rejected in review and now either are waiting to be or currently are being corrected.
Delivery
- Delivery: Ready Annotated inputs that have gotten their final annotations and thus are ready for delivery.
*The stages Quality Assurance and Correction are only shown for organizations with the request role Producer. For organizations with other request roles, these stages are part of the stage In Annotation.
The unique identifier of the scene inside the Kognic platform.
You can conduct input actions for one input at a time or multiple inputs simultaneously. Where and how to do it will be described below.
Actions for individual inputs
Any actions available for a specific input can be found in its context menu. You open it by clicking the three dots (...) at the rightmost part of the inputs table row.
Batch actions
To select which inputs you want to conduct an action for, you can use either the selection box in the table header, the drop-down next to it, or the selection boxes on each row. When you select one or multiple inputs this way, you will see a toolbar at the bottom of your screen - where all the available actions for your selection are presented.
If your selection contains a variety of inputs, it might be that the available batch actions don't apply to every input in the selection. If so, you will be notified before completing the action.
ο»Ώ
By interacting with an input's context menu, you can open and view either the input's current task, its last completed task, or the empty input itself in the task view.
You can also copy view links to these tasks using the same menu.
This option is only available in requests with a workflow containing the review phase and where your organization has the request role Producer.
Rejecting an input's currently accepted annotation returns it to the Review flow and its Review Correction stage. To reject the input's currently accepted annotation, the input must be in the workflow stage Delivery Ready.
This action is available both as a single action and a batch action.
This option is only available in requests where your organization has the request role Producer.
Deleting an input from a request has the following consequences:
- We will delete all the inputs' created tasks and their annotations.
- If a Delivery-ready annotation exists for any of the inputs, we invalidate it.
- If the request uses the review phase, we delete any potential review statistics for the inputs and their tasks. Any potential feedback provided on the inputs and their annotations will no longer be available.
The above consequences only affect the inputs within the currently selected request. I.e., the inputs will remain in their input batch and will not be deleted from any other requests they are part of.
This action is available both as a single action and a batch action.
Deleting inputs from the request is a permanent action that can't be undone.
ο»Ώ
