MTURK payment variable

[eka...@umich.edu]

Hi everyone,

Are the payment number that shows up in MTurk payments tab after the experiment is over:

"participant.payoff_in_real_world_currency" and "participant.payoff_plus_participation_fee"?

Would overwriting those variables in "models.py" also overwrite them in MTurk?

Thanks.

EK

[Chris @ oTree]

The worker's bonus is defined by participant.payoff, which automatically stores the sum of player.payoff in all apps & rounds. However, you can also override it by setting it manually, like participant.payoff = 100.

If you're using points, participant.payoff will be in points, so oTree converts it to the MTurk bonus with participant.payoff.to_real_world_currency(session). So, keep that in mind and set participant.payoff to a value keeping in mind the real_world_currency_per_point conversion rate.

payoff_in_real_world_currency is not part of oTree's API. It may be some internal utility but you should not use it because it is unstable.

[eka...@umich.edu]

Thanks Chris.

My issue is that I have two treatments with different conversion rates.  I have defined two separate variables for the conversion rate instead of the original real_world_currency_per_point. 

real_world_currency_per_point_T1

and 

real_world_currency_per_point_T2

 Is there any way to update the dollar values with these custom conversion rates using models.py and pass it on to MTurk?

[Chris @ oTree]

oTree doesn't recognize those attributes. You need to modify participant.payoff such that when it's multiplied by session.config['real_world_currency_per_point'], it equals the amount you desire. So you need to work backwards from there to figure out what participant.payoff must be.

[Chris @ oTree]

(to make calculations easier, you should probably set the official real_world_currency_per_point to 1, so that it has no effect.)

[eka...@umich.edu]

Thanks! That's a great workaround.