@@ -28,6 +28,12 @@ is scored three times.
28
28
29
29
The scores can then be used to sort the captions to choose the best captions as the final annotations.
30
30
31
+ In order to ensure that a worker does not end up seeing their own submissions from earlier tasks (e.g. scoring their
32
+ own description from the audio description task), the audio files and HITs should be divided into 10 batches.
33
+ Each worker will then be allowed to participate in one task per batch. This can be accomplished using custom AMT
34
+ qualifications. Once a batch of a given task is finished, the bath qualification should then be granted to the workers
35
+ who participated in the task in that batch.
36
+
31
37
----
32
38
33
39
## Requirements
@@ -104,6 +110,12 @@ AMT Sandbox is used by default.
104
110
8 ) To get submission data from AMT based on the ` CURRENT ` field data, run ` get_results.py ` .
105
111
The data will be written in the file listed in ` CURRENT.output_data_file ` .
106
112
113
+ Once you have received the results for a task in a given batch, the workers who participated in that task
114
+ should be granted the appropriate qualification. E.g. once all the results have been gathered for the
115
+ batch 5 audio description task, the workers who participated in the batch 5 audio description task should
116
+ be granted the batch 5 qualification. The batch 5 qualification ID is the fifth ID in the list in the field
117
+ ` BATCH ` in the file ` custom_qualifications.yaml ` .
118
+
107
119
HIT data such as rewards can be changed in the config file.
108
120
If you want to use task-specific requirements, you can copy the ` REQUIREMENTS ` field into the
109
121
task field directly, as is done in the ` CAPTION_SCORE ` task.
0 commit comments