Error Types
Setting specific error types in Correction Requests helps to make feedback communication consistent, less ambiguous, and more specific.
Using error types with more specific names can make giving or understanding feedback easier.
Error types can be customized per organization and request. Limiting the available error types can help focus the review on important errors in a project.
The Review monitoringο»Ώ will allow you to analyze the quality based on the feedback given in Review tasks using the custom error types.
This table shows the default Kognic error types and what features they support in the UI.
Name | Comment | 2D/3D Pin | Shape reference | Value suggestion |
|---|---|---|---|---|
Incorrect class | Shape has incorrect class | β | β | β - can suggest class name |
Properties | Shape has incorrect property | β | β | β - can suggest correct property value |
Not an object | Drawn object is not a qualified object | β | β | β |
Incorrect Layer Order | ο»Ώ | β | β | β |
Incorrect position | ο»Ώ | β | β | β |
Incorrect dimension | ο»Ώ | β | β | β |
Missing object | Qualified object is missing | β | β | β |
Indicate incorrect dimension for object | To point out dimension extents of an object | β | β | β |
Other | ο»Ώ | β | β | β |
The default error types can be extended or replaced with custom error types. That might be interesting if your team is used to working with different error types or if your specific annotation task can benefit from error types tailored to the task and its quality drivers.
They can be connected to your organization on the platform anytime - our platform is backward compatible.
You can configure only specific error types for a request to focus the review and feedback on particular errors.
