1. Taskflow Details

Users must fill in the taskflow details on the left (highlighted red area). The user has to define the taskflow order and function on the right.

Taskflow Basic Details

Annotation Tool Selection

• By default, the same tool is selected at the time of creating recipe i.e. iMerit LiDAR (Multisensor).

  

---

Select Taskflow Template

On tool selection, the options to select a Workflow Template will appear right below. Selecting a template will define the number of nodes the task will pass through in the labeling process. Learn how to select a template (below).

---

Additional Information

Give a Name and Description to the Taskflow.

---

Advanced Feature

Timeout

The tool by default tracks an individual's time on each frame. However, this feature waits for x mins of idle time before the time tracker in the annotation tool comes to a stop till any activity is detected on the tool.

Audit Errors

This UI helps manage the visibility of Issue Types for Auditors in the Audit tool. The Solution Owner can navigate to the UI and configure the Issue Types.

+ New

+ New enables a user to create a new template.

1. Category: Errors are to be grouped so that they can be easily distinguishable on the UI and analytics can be prepared based on this category.

2. Color: A category is assigned a color so that on the Audit tool, an Auditor can associate which Issue(s) belong to the same category when they select an Issue from the list.

3. Add an Issue Type, that will be visible on the Audit tool

4. If a taskflow is

   1. being created, click on Publish Taskflow

   2. being modified, click on Update

Default Template

A default template is provided by QuickServe. A user can modify it to create a new template out of it.

1. Select Default Template

2. Make modifications as needed

3. If a taskflow is

   1. being created, click on Publish Taskflow

   2. being modified, click on Update

Import Existing

Using an existing taskflow, the user can import the Audit Error template and continue modifying it.

1. Select Import Existing

2. Select the taskflow from which to import

3. If a taskflow is

   1. being created, click on Publish Taskflow

   2. being modified, click on Update

Validation Script

Quickserve allows users to add and manage validation scripts in taskflows, ensuring validation at multiple stages like OP, QC, and Audit. You can create, edit, and track validation scripts both before and after publishing a taskflow. The system supports script version management, tracking all revisions post-publishing, accessing revision history and restoring previous versions.

In case of any syntactical error, the platform will identify it and ask the user for resolution.

Attaching a Validation Script - While Publishing Taskflow

1. Navigate to the Advanced Features section.

2. Expand Validation Script section

3. Insert validation logic using appropriate decorators and function structures to specify the type of validation, such as frame-wise, class-wise, or task attribute validation.

4. Click Save

After Publishing the Taskflow - After Publishing Taskflow

1. Navigate to the Advanced Features section.

2. Expand Validation Script section

3. Edit the validation script

4. Click Save

Post-publication edits to the validation script will take affect to batches where the user will explicitly trigger the ‘Validation' feature again.

Types of Validation Scripts

Validation scripts are executed using a decorator-based approach. Each type of validation uses specific decorators to target different elements like frames, classes, or task attributes.

1. Frame-wise Validation

Frame-wise validation ensures that each individual frame is validated according to specific rules. A decorator for this type of validation specifies that the function will process one frame at a time.

Decorator Usage:

• The decorator @dec({"type": "frame"}) tells the system that the function is working on individual frame data.

Function Definition:

• The function receives one parameter, which is the data for a specific frame.

• The function processes this frame and can return an error log if any issue is found.

2. Class Validation Across Multiple Frames

Class validation checks specific classes across multiple frames. This ensures that particular classes (e.g., "Vehicle", "Trucks", etc.) are consistently annotated across all frames.

Decorator Usage:

• The decorator @dec({"type": "object", "selector": "class", "value": ["<class1>", "<class2>"]}) tells the system to pass annotations of the specified classes across all frames into the function.

Function Definition:

• The function receives one parameter for each specified class. If you validate two classes, you need two parameters.

• The function compares or processes the classes across multiple frames.

3. Task-wise Attribute Validation Across Frames

This type of validation ensures that attributes related to a task are validated across all frames in the task.

Decorator Usage:

• The decorator @dec({"type": "attribute", "selector": "task"}) indicates that the function will work with task-level attributes across multiple frames.

Function Definition:

• The function receives one parameter that includes all attributes related to the task, across all frames.

---

Taskflow Templates

On tool selection, the options to select a workflow template will appear. Selecting a Template will define the number of Nodes the Task will pass through in the labeling Process.

A Node defines the number of rounds and the order in which a task passes through the labelling process.

Users can start building their Taskflow by picking one of the 3 Templates: 1-3 Node Templates available.

Choosing a Template based on Nodes:

1. Choose the template based on the number of rounds a task pass through the labelling process.

2. A maximum of three nodes can be defined.

3. Multiple users can work simultaneously on the first node in different batches.

4. Example of choosing Templates:

   • Choose 3 Node Template if there is a need for the to undergo 3 rounds.

     Eg: 1 to Create, 2 to Check & Edit.

   • Choose 2 Node Templates if there is a need for 2 rounds.

     Eg: 1 to Create annotations and 1 to Check.

   • Choose 1 Node Template if multiple rounds are not required and one is enough.

The templates use dummy node names: OP(Operator), QC (Quality Check), Super QC. After picking the template the user can see its reflection on the pink highlighted area where they can rename and define functions at each node.