Difference between revisions of "Mergers"

From Eyewire
Jump to: navigation, search
m
(Marked this version for translation)
Line 1: Line 1:
 
<translate>
 
<translate>
 +
<!--T:1-->
 
Mergers are one of the most common problems in EyeWire. Mergers are created when either the [[Artificial Intelligence |Artificial Intelligence (AI)]] has included pieces from two different cells in a single segment, or when players mistakenly add a segment that does not belong. When the AI includes pieces from two different cells in a single segment, there is no way for the player to separate it into two segments, so they must learn to work around them. For smaller mergers that do not exit the cube a player may ignore them and continue their trace as normal. For larger mergers and/or mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.
 
Mergers are one of the most common problems in EyeWire. Mergers are created when either the [[Artificial Intelligence |Artificial Intelligence (AI)]] has included pieces from two different cells in a single segment, or when players mistakenly add a segment that does not belong. When the AI includes pieces from two different cells in a single segment, there is no way for the player to separate it into two segments, so they must learn to work around them. For smaller mergers that do not exit the cube a player may ignore them and continue their trace as normal. For larger mergers and/or mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.
  
 +
<!--T:2-->
 
In the event that the players create a merger, [[Player_Roles#The_Order_of_the_Scythe|scythes]] or an admin is needed to remove it.
 
In the event that the players create a merger, [[Player_Roles#The_Order_of_the_Scythe|scythes]] or an admin is needed to remove it.
  
==AI Mergers==
+
==AI Mergers== <!--T:3-->
  
 +
<!--T:4-->
 
For varying reasons the AI can create mergers. It can be because of a misalignment, because of a damage in the neuron that the AI navigated through wrongly or because in the parent cube players created a merger and the AI created both the correct and the merger paths in the child cube creating thus an AI merger. In that last possibility removing the merger from the parent cube may not also remove it from the child cube, so an admin needs to remove it from there as well.
 
For varying reasons the AI can create mergers. It can be because of a misalignment, because of a damage in the neuron that the AI navigated through wrongly or because in the parent cube players created a merger and the AI created both the correct and the merger paths in the child cube creating thus an AI merger. In that last possibility removing the merger from the parent cube may not also remove it from the child cube, so an admin needs to remove it from there as well.
 
<gallery mode=packed heights=250px>
 
<gallery mode=packed heights=250px>
Line 12: Line 15:
 
</gallery>
 
</gallery>
  
===Misalignment AI mergers===
+
===Misalignment AI mergers=== <!--T:5-->
  
 +
<!--T:6-->
 
Sometimes misalignments in the 2D slides can cause the AI to get confused and create a seed merger.
 
Sometimes misalignments in the 2D slides can cause the AI to get confused and create a seed merger.
 
<gallery mode=packed heights=250px>
 
<gallery mode=packed heights=250px>
Line 19: Line 23:
 
</gallery>
 
</gallery>
  
====Misalignment Merger Tutorial====
+
====Misalignment Merger Tutorial==== <!--T:7-->
  
 +
<!--T:8-->
 
One of EyeWire's gamemasters, sorek.m, created a video on [https://www.youtube.com/watch?v=ktuLSIIVl9Q&list=UUFWepnO6PHChOTIXsNePEYQ| how to trace around misalignment mergers.]
 
One of EyeWire's gamemasters, sorek.m, created a video on [https://www.youtube.com/watch?v=ktuLSIIVl9Q&list=UUFWepnO6PHChOTIXsNePEYQ| how to trace around misalignment mergers.]
  
===No-Borders AI mergers===
+
===No-Borders AI mergers=== <!--T:9-->
  
 +
<!--T:10-->
 
There are spots inside the dataset that for whatever reason the neuron(s) were damaged and create "no border mergers" meaning that the borders between them are either damaged or gone and so the AI thinks that whole thing to be one single neuron when in fact its two different ones (or even possibly more than 2)
 
There are spots inside the dataset that for whatever reason the neuron(s) were damaged and create "no border mergers" meaning that the borders between them are either damaged or gone and so the AI thinks that whole thing to be one single neuron when in fact its two different ones (or even possibly more than 2)
 
<gallery mode=packed heights=250px>
 
<gallery mode=packed heights=250px>
Line 32: Line 38:
 
</gallery>
 
</gallery>
  
==Player made mergers==
+
==Player made mergers== <!--T:11-->
  
 +
<!--T:12-->
 
Players can also create mergers even when there's not an AI merger that can mislead them into tracing a wrong neuron/segment(s). Be it misalignment(s), no-borders (usually shown as pure white in the 2D), fuzzy, unclear borders and so on. There have been a couple of isolated cases of players who traced everything in a cube on purpose. They were caught and "gifted" by the [[GrimReaper]] with -10,000,000 points and subsequent removal from the game.
 
Players can also create mergers even when there's not an AI merger that can mislead them into tracing a wrong neuron/segment(s). Be it misalignment(s), no-borders (usually shown as pure white in the 2D), fuzzy, unclear borders and so on. There have been a couple of isolated cases of players who traced everything in a cube on purpose. They were caught and "gifted" by the [[GrimReaper]] with -10,000,000 points and subsequent removal from the game.
 
<gallery mode=packed heights=250px>
 
<gallery mode=packed heights=250px>
Line 42: Line 49:
 
</gallery>
 
</gallery>
  
==Reporting a merger==
+
==Reporting a merger== <!--T:13-->
  
 +
<!--T:14-->
 
If a player finds a merger in the overview, they can email [mailto:support@eyewire.org support@eyewire.org], with the coordinates of the merger and the cell name or cell ID. To get the coordinates, type '/debug' into chat (including the forward-slash), then alt+click on the point where you think the merger is. The more zoomed in you are the more accurate your coordinates will be. Also rotate the 3D to make sure you are actually centered on the merger. A screenshot of the overview can be provided in addition to the coordinates. (The cell ID can also be found in the debug window.)  
 
If a player finds a merger in the overview, they can email [mailto:support@eyewire.org support@eyewire.org], with the coordinates of the merger and the cell name or cell ID. To get the coordinates, type '/debug' into chat (including the forward-slash), then alt+click on the point where you think the merger is. The more zoomed in you are the more accurate your coordinates will be. Also rotate the 3D to make sure you are actually centered on the merger. A screenshot of the overview can be provided in addition to the coordinates. (The cell ID can also be found in the debug window.)  
  
 +
<!--T:15-->
 
If you are unsure on whether or not you found a merger, you can ask in chat for some help.
 
If you are unsure on whether or not you found a merger, you can ask in chat for some help.
 
<gallery mode=packed heights=500px>
 
<gallery mode=packed heights=500px>

Revision as of 20:35, 7 November 2015

Mergers are one of the most common problems in EyeWire. Mergers are created when either the Artificial Intelligence (AI) has included pieces from two different cells in a single segment, or when players mistakenly add a segment that does not belong. When the AI includes pieces from two different cells in a single segment, there is no way for the player to separate it into two segments, so they must learn to work around them. For smaller mergers that do not exit the cube a player may ignore them and continue their trace as normal. For larger mergers and/or mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.

In the event that the players create a merger, scythes or an admin is needed to remove it.

AI Mergers

For varying reasons the AI can create mergers. It can be because of a misalignment, because of a damage in the neuron that the AI navigated through wrongly or because in the parent cube players created a merger and the AI created both the correct and the merger paths in the child cube creating thus an AI merger. In that last possibility removing the merger from the parent cube may not also remove it from the child cube, so an admin needs to remove it from there as well.

Misalignment AI mergers

Sometimes misalignments in the 2D slides can cause the AI to get confused and create a seed merger.

Misalignment Merger Tutorial

One of EyeWire's gamemasters, sorek.m, created a video on how to trace around misalignment mergers.

No-Borders AI mergers

There are spots inside the dataset that for whatever reason the neuron(s) were damaged and create "no border mergers" meaning that the borders between them are either damaged or gone and so the AI thinks that whole thing to be one single neuron when in fact its two different ones (or even possibly more than 2)

Player made mergers

Players can also create mergers even when there's not an AI merger that can mislead them into tracing a wrong neuron/segment(s). Be it misalignment(s), no-borders (usually shown as pure white in the 2D), fuzzy, unclear borders and so on. There have been a couple of isolated cases of players who traced everything in a cube on purpose. They were caught and "gifted" by the GrimReaper with -10,000,000 points and subsequent removal from the game.

Reporting a merger

If a player finds a merger in the overview, they can email support@eyewire.org, with the coordinates of the merger and the cell name or cell ID. To get the coordinates, type '/debug' into chat (including the forward-slash), then alt+click on the point where you think the merger is. The more zoomed in you are the more accurate your coordinates will be. Also rotate the 3D to make sure you are actually centered on the merger. A screenshot of the overview can be provided in addition to the coordinates. (The cell ID can also be found in the debug window.)

If you are unsure on whether or not you found a merger, you can ask in chat for some help.