# 3. Attributes
Define attributes on the right highlighted section below. The saved attribute(s) will appear in rows highlighted on the left of the image.
***
## Create Attributes
To create a new attribute, the user has to give details of the following three sections:
1. [Attribute Type](#id-1.-attribute-type)
2. [UI Component](#id-2.-ui-component)
3. [Identity](#id-3.-identity)
***
## 1. Attribute Type
### **A. Class Level**
Select this if the attribute is linked to a [class](https://docs.imerit-prod.io/project-setup/create-recipe/2.-classes). The user must give the following inputs if the attribute type belongs to this one:
#### **Global Attribute: ON / OFF**
If this attribute is associated with all the classes created, toggle this **ON**. For example, there are 2 classes: ‘Car’ and ‘Truck’. The ‘Headlight’ attribute can be marked as **Global** to link it to both the created classes. If the attribute is associated with only one or a few classes, leave this toggle **OFF**. These can be linked to the specific classes in the [association](https://docs.imerit-prod.io/project-setup/create-recipe/4.-associations) tab in the next step.
#### **Attribute Mode**
Specify which of the following mode it belongs to:
* **Constant:** Toggle this **ON** if the attribute value remains constant within a [frame](https://docs.imerit-prod.io/pre-process-data#frame) and across [frames](https://docs.imerit-prod.io/pre-process-data#frame) (i.e. the [batch](https://docs.imerit-prod.io/pre-process-data#batch)). For example, the value of a vehicle's *color* attribute cannot change across [frames](https://docs.imerit-prod.io/pre-process-data#frame). Continuing with this example, consider the below representation of object Car\_1 and attribute *color,*
* The checkmarks indicate the presence of the Car\_1 object and its corresponding annotation on the specified sensor.
* The **singular** color-filled boxes indicate that the constant attribute value remains **uniform** across the [batch](https://docs.imerit-prod.io/pre-process-data#batch) and within each [frame](https://docs.imerit-prod.io/pre-process-data#frame).
{% hint style="success" %}
The constant attribute value will remain consistent across the entire sequence.
{% endhint %}
* **Time-Varying:** Toggle this **ON** if the attribute value remains constant within a [frame](https://docs.imerit-prod.io/pre-process-data#frame) but changes across the [frames](https://docs.imerit-prod.io/pre-process-data#frame) (i.e. the [batch](https://docs.imerit-prod.io/pre-process-data#batch)). For example, the value of a vehicle's *headlight* attribute will remain uniform within a [frame](https://docs.imerit-prod.io/pre-process-data#frame), however, can change across [frames](https://docs.imerit-prod.io/pre-process-data#frame). Continuing with this example, consider the below representation of object Car\_1 and attribute *headlight,*
* The checkmarks indicate the presence of the Car\_1 object and its corresponding annotation on the specified sensor.
* The **singular** color-filled boxes within the [frame](https://docs.imerit-prod.io/pre-process-data#frame) indicate that the value remains **uniform.**
* The **multiple** color-filled boxes across the [frame](https://docs.imerit-prod.io/pre-process-data#frame) indicate that the value can change with time.
{% hint style="success" %}
The time-varying attribute value will stay consistent across different sensors within a single [frame](https://docs.imerit-prod.io/pre-process-data#frame) but may change across the sequence.
{% endhint %}
* **Sensor Specific:** Toggle this **ON** if the attribute changes both within a [frame](https://docs.imerit-prod.io/pre-process-data#frame) and across the [frames](https://docs.imerit-prod.io/pre-process-data#frame) (i.e. the [batch](https://docs.imerit-prod.io/pre-process-data#batch)). For example, the value of a vehicle's *occlusion* attribute will change both within and across [frames](https://docs.imerit-prod.io/pre-process-data#frame). Continuing with this example, consider the below representation of object Car\_1 and attribute *occlusion*,
* The checkmarks indicate the presence of the Car\_1 object and its corresponding annotation on the specified sensor.
* The **multiple** color-filled boxes within the [frame](https://docs.imerit-prod.io/pre-process-data#frame) indicate that the value can change.
* The **multiple** color-filled boxes across the [frame](https://docs.imerit-prod.io/pre-process-data#frame) indicate that the value can change with time.
{% hint style="success" %}
The sensor specific attribute value may change across different sensors within a single [frame](https://docs.imerit-prod.io/pre-process-data#frame) AND may change throughout the sequence.
{% endhint %}
***
### **B. Task Level**
Choose this option if the attribute is associated with a specific [frame](https://docs.imerit-prod.io/pre-process-data#frame). For instance, the attribute ‘Foggy’ can be used by annotators to label a particular frame as ‘Foggy,’ indicating the scene's condition in that specific frame within the [batch](https://docs.imerit-prod.io/pre-process-data#batch).
There are two type of modes,
1. Time-Varying : This type of attribute propagates the value across the sequence to reduce the subject expert having to set it everytime on each frame. However, when the user changes the value in the following frames, it will propagate it forward.
[Learn how to use](https://docs.imerit-prod.io/annotation-tool/key-features/task-level-attribute-propagation#time-varying-task-level-attribute).
2. Manual : This type of attribute requires the subject expert to set the task level attribute for each frame manually.
[Learn how to use](https://docs.imerit-prod.io/annotation-tool/key-features/task-level-attribute-propagation#manual-task-level-attribute).
### **C. Batch Level**
Choose this option if the attribute applies to all the [frames](https://docs.imerit-prod.io/pre-process-data#frame) within a [batch](https://docs.imerit-prod.io/pre-process-data#batch). For instance, the attribute ‘Time of Day’ can be used by annotators to highlight a specific time of day for the entire sequence.
***
## 2. UI Component
Indicate how the annotator should enter the values of the attribute created and whether it is optional for marking or not.
### **Boolean**
The value of this attribute can either be true or false. When selected, a toggle appears at the end of the form called ‘**Default Value**’. To decide the default behaviour of the boolean attribute on the annotation tool toggle the Default Value switch;
* When switched off, the value is false on the annotation tool.
* When switched on, the value is true on the annotation tool.
### **Inputbox**
Select this when the value is to be entered in an Input Box and define the condition of the text by selecting the input type. A toggle appears to mark this Input as Optional or not at the end of the form. **Note**: ‘Float’ in Input Type allows any numbers with decimal points.
### **Multi-Select**
When Attributes can have multiple values, this option is selected. Define the option name (Value, Text, Abbr.)
* Value: Enter the option name reflected in the output data
* Text: Enter the option name reflected in the [Annotation Tool](https://docs.imerit-prod.io/annotation-tool)
* Abbreviation: Abbreviation reflecting in case of less space.
### **Select**
When attributes have a single value, this option is selected. The options will need to be defined like above. (Value, Text, Abbr)
