Difference between revisions of "The Consensus"
From Eyewire
m |
(Marked this version for translation) |
||
| Line 1: | Line 1: | ||
<translate> | <translate> | ||
| + | <!--T:1--> | ||
In order to produce the most accurate data, EyeWire accepts the consensus, a sophisticated combination of the players traces, for each cube. | In order to produce the most accurate data, EyeWire accepts the consensus, a sophisticated combination of the players traces, for each cube. | ||
| − | ===Weight=== | + | ===Weight=== <!--T:2--> |
| + | <!--T:3--> | ||
*Every time a player submits a cube, it gains 1 weight. | *Every time a player submits a cube, it gains 1 weight. | ||
*When the cube hasn't been [[FAQ#What is a trailblazer | trailblazed]] yet, its weight is 0. | *When the cube hasn't been [[FAQ#What is a trailblazer | trailblazed]] yet, its weight is 0. | ||
| − | ====Confidence Values==== | + | ====Confidence Values==== <!--T:4--> |
| + | <!--T:5--> | ||
*Since different players might trace a cube differently, the segments inside the cube may have different confidence values. | *Since different players might trace a cube differently, the segments inside the cube may have different confidence values. | ||
*A confidence value is the likelihood that a segment belongs in a cube. | *A confidence value is the likelihood that a segment belongs in a cube. | ||
*The likelihood that a segment is included in the consensus is dependent on how many players included that segment in their trace. | *The likelihood that a segment is included in the consensus is dependent on how many players included that segment in their trace. | ||
| − | ====Scythe Weight==== | + | ====Scythe Weight==== <!--T:6--> |
| + | <!--T:7--> | ||
*When reaping a cube, a [[Player_Roles#The_Order_of_the_Scythe | Scythe]] has weight 2. | *When reaping a cube, a [[Player_Roles#The_Order_of_the_Scythe | Scythe]] has weight 2. | ||
*This weight is used to fix a [[Mergers|merger]], missing branch, or missing nub. | *This weight is used to fix a [[Mergers|merger]], missing branch, or missing nub. | ||
*Often it is necessary for multiple Scythes to reap a cube in order to change the confidence of the segments. | *Often it is necessary for multiple Scythes to reap a cube in order to change the confidence of the segments. | ||
| − | ====Reaper Weight==== | + | ====Reaper Weight==== <!--T:8--> |
| + | <!--T:9--> | ||
*Admins and the [[GrimReaper]] have a weight of one million when reaping a cube. | *Admins and the [[GrimReaper]] have a weight of one million when reaping a cube. | ||
*They also use this this to fix mergers, missing branches, and missing nubs. | *They also use this this to fix mergers, missing branches, and missing nubs. | ||
| Line 26: | Line 31: | ||
*This can often cause problems when a [[Player_Roles#The_Order_of_the_Scouts| Scout]] or Scythe finds a merger, missing branch, or missing nub in a reaper weighted cube. | *This can often cause problems when a [[Player_Roles#The_Order_of_the_Scouts| Scout]] or Scythe finds a merger, missing branch, or missing nub in a reaper weighted cube. | ||
| − | ===Frozen Cubes=== | + | ===Frozen Cubes=== <!--T:10--> |
| + | <!--T:11--> | ||
*Admins freeze cubes to prevent players from playing them. | *Admins freeze cubes to prevent players from playing them. | ||
*[[Cell Body |Cell bodies]] are frozen because: | *[[Cell Body |Cell bodies]] are frozen because: | ||
| Line 37: | Line 43: | ||
Duplicate Cubes will also be frozen. | Duplicate Cubes will also be frozen. | ||
| − | ====Duplicate Cubes==== | + | ====Duplicate Cubes==== <!--T:12--> |
| + | <!--T:13--> | ||
*Duplicate cubes are cubes that share segments with a cube in another cell. | *Duplicate cubes are cubes that share segments with a cube in another cell. | ||
*This usually means that one of the cells has a [[Mergers | merger]] | *This usually means that one of the cells has a [[Mergers | merger]] | ||
| − | =====Spliced Branches===== | + | =====Spliced Branches===== <!--T:14--> |
| + | <!--T:15--> | ||
*If there was a merger in a past cell and it has been removed, the Duplicate cube will automatically splice the branch up until the point at which the merger was removed | *If there was a merger in a past cell and it has been removed, the Duplicate cube will automatically splice the branch up until the point at which the merger was removed | ||
*This can greatly accelerate the tracing process of the cell. | *This can greatly accelerate the tracing process of the cell. | ||
| − | ===The Spawner=== | + | ===The Spawner=== <!--T:16--> |
| + | <!--T:17--> | ||
*The Spawner creates a cube when the consensus shows that the branch extends. | *The Spawner creates a cube when the consensus shows that the branch extends. | ||
*It uses some parts of the last cube as the seed. | *It uses some parts of the last cube as the seed. | ||
*It also updates the weight and confidence values of a cube after a player submits it. | *It also updates the weight and confidence values of a cube after a player submits it. | ||
</translate> | </translate> | ||
Revision as of 16:11, 17 November 2015
In order to produce the most accurate data, EyeWire accepts the consensus, a sophisticated combination of the players traces, for each cube.
Contents
Weight
- Every time a player submits a cube, it gains 1 weight.
- When the cube hasn't been trailblazed yet, its weight is 0.
Confidence Values
- Since different players might trace a cube differently, the segments inside the cube may have different confidence values.
- A confidence value is the likelihood that a segment belongs in a cube.
- The likelihood that a segment is included in the consensus is dependent on how many players included that segment in their trace.
Scythe Weight
- When reaping a cube, a Scythe has weight 2.
- This weight is used to fix a merger, missing branch, or missing nub.
- Often it is necessary for multiple Scythes to reap a cube in order to change the confidence of the segments.
Reaper Weight
- Admins and the GrimReaper have a weight of one million when reaping a cube.
- They also use this this to fix mergers, missing branches, and missing nubs.
- Because of the high weight, it only requires one Admin to change a cube.
- This can often cause problems when a Scout or Scythe finds a merger, missing branch, or missing nub in a reaper weighted cube.
Frozen Cubes
- Admins freeze cubes to prevent players from playing them.
- Cell bodies are frozen because:
- they are not useful for the research that is being conducted.
- the AI does not segment them well since it is designed to segment branches.
- they take a long time to trace
- they slow down the players' computers.
- Some cubes will be frozen when there is a serious AI merger in the cube that cannot be removed.
Duplicate Cubes will also be frozen.
Duplicate Cubes
- Duplicate cubes are cubes that share segments with a cube in another cell.
- This usually means that one of the cells has a merger
Spliced Branches
- If there was a merger in a past cell and it has been removed, the Duplicate cube will automatically splice the branch up until the point at which the merger was removed
- This can greatly accelerate the tracing process of the cell.
The Spawner
- The Spawner creates a cube when the consensus shows that the branch extends.
- It uses some parts of the last cube as the seed.
- It also updates the weight and confidence values of a cube after a player submits it.
