Difference between revisions of "Mergers"

From Eyewire
Jump to: navigation, search
(Grammar, organization, and capitalization)
 
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
<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.
  
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.
+
<!--T:2-->
 +
In the event that the players create a merger, [[Player_Roles#The_Order_of_the_Scythe|Scythes]] or an [[Player_Roles#Administrators|Admin]] is needed to remove it.
  
==AI Mergers==
+
==AI Mergers== <!--T:3-->
  
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.
+
<!--T:4-->
 +
For varying reasons the AI can create mergers. It can be because of a misalignment, 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 the 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>
 
File:AI_merger.jpg|AI merger
 
File:AI_merger.jpg|AI merger
Line 11: 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 18: Line 23:
 
</gallery>
 
</gallery>
  
 +
====Misalignment Merger Tutorial==== <!--T:7-->
  
===No-Borders AI mergers===
+
<!--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.]
  
 +
===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>
 
File:No_borders.png|AI merger due to no-borders between the neurons. Thankfully here it doesn't create a problem so long as its not traced by players.
 
File:No_borders.png|AI merger due to no-borders between the neurons. Thankfully here it doesn't create a problem so long as its not traced by players.
File:No_borders2.png|merger due to no-borders between the neurons. Here the problem is severe as the merged branch touches the cube's wall on two different sides which means that it will spawn cubes and probably create a second Cell. It was however removed by an admin.
+
File:No_borders2.png|Merger due to no-borders between the neurons. Here the problem is severe as the merged branch touches the cube's wall on two different sides which means that it will spawn cubes and probably create a second cell. It was, however, removed by an admin.
File:Royal_mess.jpg|Here a misalignment and a no-borders merger have made the AI cause one heck of a royal mess of an AI merger. Because of the no-borders the AI seed merger is one single fused segment that cannot be removed by admins. It has been traced and frozen so that only the healthy, correct branch can grow.
+
File:Royal_mess.jpg|Here a misalignment and a no-borders merger have made the AI cause a royal mess of an AI merger. Because of the no-borders the AI seed merger is one single fused segment that cannot be removed by admins. It has been traced and frozen so that only the healthy, correct branch can grow.
 
</gallery>
 
</gallery>
  
==Player made mergers==
+
==Player made mergers== <!--T:11-->
  
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.
+
<!--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), 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>
File:No_borders_player.jpg|no-borders merger on 2D that players have traced
+
File:No_borders_player.jpg|No-Borders merger on 2D that players have traced
 
File:Merger_in_the_trace.jpg|Red line correct trace, blue line merged neuron, in this case you trace the merger, find the correct path if there's one and then deselect the merger segment leaving a gap. Leaving the blue line branch would create a merger.
 
File:Merger_in_the_trace.jpg|Red line correct trace, blue line merged neuron, in this case you trace the merger, find the correct path if there's one and then deselect the merger segment leaving a gap. Leaving the blue line branch would create a merger.
 
File:Player_merger.png|Player merger
 
File:Player_merger.png|Player merger
File:No-borders player merger.jpg|This is a good example of a no-borders merger created by players. The circled piece in the image is to show where the merger is. It is usually presented in extremely white in the 2D and such segments must never be added even if they make a bouton/branch/nub/etc rounder and fuller as they do not belong and may lead to larger merger creation.
+
File:No-borders player merger.jpg|This is a good example of a No-Borders merger created by players. The circled piece in the image is to show where the merger is. It is usually presented in extremely white in the 2D and such segments must never be added even if they make a bouton/branch/nub/etc rounder and fuller as they do not belong and may lead to larger merger creation.
 
</gallery>
 
</gallery>
 +
 +
==Not a merger==
 +
<gallery mode=packed heights=250px>
 +
File:Glued autapse.jpg|Glued autapse is not a merger
 +
</gallery>
 +
 +
==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.)
 +
 +
<!--T:15-->
 +
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>
 +
File:Merger reporting.jpg|Required info in reporting a merger
 +
</gallery>
 +
 +
</translate>
 +
[[ko:Mergers]]

Latest revision as of 02:48, 16 November 2019

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, 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 the 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), 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.

Not a merger

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.