-
...r mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.
531 B (91 words) - 19:16, 17 November 2015
-
*This weight is used to fix a [[Mergers|merger]], missing branch, or missing nub.
279 B (49 words) - 20:17, 17 November 2015
-
*'''[[Mergers|Merger]]''': Was genau sind "Merger" und wie sehen sie aus?
1 KB (179 words) - 15:11, 21 November 2015
-
*'''[[Mergers|Merger]]''': Was genau sind "Merger" und wie sehen sie aus?
1 KB (179 words) - 15:11, 21 November 2015
-
[[File:AddingDust.png|250 px|thumb|center|The green segment has a merger in it. "Dust" was added to the good part of the branch to allow the branch
195 B (36 words) - 17:38, 17 November 2015
-
*This weight is used to fix a [[Mergers|merger]], missing branch, or missing nub.
...s 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.
2 KB (421 words) - 17:41, 17 November 2015
-
====Misalignment Merger Tutorials====
37 B (3 words) - 18:22, 17 November 2015
-
...[Advanced Roles in EyeWire#Scythe | Scythe]], or Admin for help. If the AI merger exits the cube, a Scout, Scythe, or Admin should be notified as soon as pos
405 B (74 words) - 18:25, 17 November 2015
-
...s 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.
401 B (71 words) - 18:26, 17 November 2015
-
...cube will automatically splice the branch up until the point at which the merger was removed
231 B (42 words) - 18:31, 17 November 2015
-
*This usually means that one of the cells has a [[Mergers | merger]]
144 B (25 words) - 18:32, 17 November 2015
-
*Some cubes will be frozen when there is a serious AI merger in the cube that cannot be removed.
457 B (79 words) - 18:37, 17 November 2015
-
...it in green. The third image shows the cube after an admin has removed the merger.]]
257 B (49 words) - 18:41, 17 November 2015
-
...dd some "dust" that exits the cube in the same spot as the branch with the merger so that the branch will continue to grow.
227 B (44 words) - 17:10, 17 November 2015
-
...r mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.
...dd some "dust" that exits the cube in the same spot as the branch with the merger so that the branch will continue to grow.
4 KB (777 words) - 16:50, 17 November 2015
-
...ide of the cube, the player should remove the segment that attaches to the merger and continue to trace the good part of the branch to completion.
560 B (99 words) - 16:53, 17 November 2015
-
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 misalig
File:No_borders_player.jpg|no-borders merger on 2D that players have traced
1 KB (219 words) - 20:35, 7 November 2015
-
...r 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
5 KB (895 words) - 16:13, 17 November 2015
-
...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 coordinate
585 B (107 words) - 20:37, 7 November 2015
-
...r mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.
706 B (123 words) - 20:37, 7 November 2015
