Some quality control rules have the parameter which allows to calculate Toloker's responses from other pools. It sets the dynamic window, which the values are recalculated within. Depending on the rule, the dynamic window is measured:
In tasks: the Review results and Majority vote rules, the Recent tasks to use field.
In control tasks: the Control tasks rule, the Recent control and training task responses to use field.
In task suites: the Fast responses rule, the Recent task suites to use field.
The
Let's see how this parameter works with the Control tasks rule. Go to the project or pool settings and select this quality control rule.
In our example, the
Toloka calculates all control task responses only in the pool to which the rule applies.
The Toloker completes several tasks in pool A, where the rule calculates their skill. Then the Toloker goes to pool B with the same rule, where the field is also not filled in. In this case, the skill is calculated for pool B separately. The rule in pool B knows nothing about the Toloker's responses in pool A.
If you have previously filled in the Recent control and training task responses to use field, you can't change it to empty. But you can delete the rule and create a new one.
All rules work independently, even if they are united by one entity.
The Toloker's response history will be cleared under the following conditions:
Ban — within the dynamic window if the Recent control and training task responses to use field is filled in, or within the entire pool if the field is not filled in.
Pause on pool — within the entire pool if the field is not filled in.
When the ban or pause is lifted and the Toloker starts performing tasks, the calculation will start again without taking into account previously completed tasks.
Only the history of the rule which triggered the ban will be cleared.
Last updated: July 26, 2023