Skip to content

Create a conflict task #140

Description

@shippy

In order to test the accessibility of the documentation, we've agreed that Austin and Megha will try to implement a new task.

Since the purpose of this exercise is to find which challenges users not intimately related with the guts of the framework will run into, it would be good if Austin and Megha used this issue to document any and all problems they encounter.

The task will have the following properties, each of which is a separate goal to accomplish.

Off-center occluder

Currently, all ambiguous lotteries have a midpoint at 50%. To alter that, there are two main challenges:

  1. Which setting, or which part of the code, determines where the midpoint of a lottery is drawn?
  2. How can the properties of a trial be changed?

Conflict condition

In a new condition, an alternative to ambiguous lotteries will be a display of two full-information lotteries with different breakdowns of probability. There are number of challenges, but the ones that immediately come to mind are the following:

  1. How can we display two lotteries at once?
  2. How can we make it display 2 separate things?
  3. How to tell the task that the current condition requires a different display of ambiguity?

Other changes

We talked about domain change etc, but this will be a good start.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions