ultimatum: Documentation ************************ Accessed: 2024-04-24 Ultimatum game with two treatments: direct response and strategy method. In the former, one player makes an offer and the other either accepts or rejects. It comes in two flavors, with and without hypothetical questions about the second player's response to offers other than the one that is made. In the latter treatment, the second player is given a list of all possible offers, and is asked which ones to accept or reject. Participant id_in_session type positive integer doc code type text doc Randomly generated unique identifier for the participant. If you would like to merge this dataset with those from another subsession in the same session, you should join on this field, which will be the same across subsessions. label type text doc Label assigned by the experimenter. Can be assigned by passing a GET param called 'participant_label' to the participant's start URL _is_bot type NullBooleanField doc choices True: Yes False: No _index_in_pages type positive integer doc _max_page_index type positive integer doc _current_app_name type text doc _round_number type positive integer doc _current_page_name type text doc ip_address type GenericIPAddressField doc time_started type DateTimeField doc visited type NullBooleanField doc Whether this user's start URL was opened choices True: Yes False: No mturk_worker_id type text doc mturk_assignment_id type text doc payoff type decimal doc Player id_in_group type positive integer doc Index starting from 1. In multiplayer games, indicates whether this is player 1, player 2, etc. payoff Group id_in_subsession type positive integer doc use_strategy_method type NullBooleanField doc Whether this group uses strategy method choices True: Yes False: No amount_offered type decimal doc choices 0 points: 0 points 10 points: 10 points 20 points: 20 points 30 points: 30 points 40 points: 40 points 50 points: 50 points 60 points: 60 points 70 points: 70 points 80 points: 80 points 90 points: 90 points 100 points: 100 points offer_accepted type NullBooleanField doc if offered amount is accepted (direct response method) choices True: Yes False: No response_0 type NullBooleanField doc choices True: Yes False: No response_10 type NullBooleanField doc choices True: Yes False: No response_20 type NullBooleanField doc choices True: Yes False: No response_30 type NullBooleanField doc choices True: Yes False: No response_40 type NullBooleanField doc choices True: Yes False: No response_50 type NullBooleanField doc choices True: Yes False: No response_60 type NullBooleanField doc choices True: Yes False: No response_70 type NullBooleanField doc choices True: Yes False: No response_80 type NullBooleanField doc choices True: Yes False: No response_90 type NullBooleanField doc choices True: Yes False: No response_100 type NullBooleanField doc choices True: Yes False: No Subsession round_number type positive integer doc If this subsession is repeated (i.e. has multiple rounds), this field stores the position (index) of this subsession, among subsessions in the same app. For example, if a session consists of the subsessions: [app1, app2, app1, app1, app3] Then the round numbers of these subsessions would be: [1, 1, 2, 3, 1] Session code type text doc Randomly generated unique identifier for the session. label type text doc experimenter_name type text doc mturk_HITId type text doc mturk_HITGroupId type text doc comment type text doc is_demo type NullBooleanField doc choices True: Yes False: No