I just quickly glanced over the overview and I think we have another merge error. The circled dendrite seems to be way too horizontal compared to others. My guess is it just passes through the J cell, and a merger error occurred on one of its branches.
You’re right, I’m actually working on removing that at the moment.
Sounds like we’ve got someone who’d like to be an admin and help trim mergers…
Just finished a cube in which I personally didn’t feel a branch was present, but when zooming out to the overview I saw that the majority did. There wasn’t a clear border between the branch and the original part, but the way they were connected seemed unnatural to me. It’s not a passer-by branch of another cell, but possibly a synapse or simply near contact?
So far this new branch has spawned just one new cube from it, but I’d keep an eye on it.
@balkamm, I’ll just continue posting possible errors here whenever I see them. Maybe we should create one dedicated thread for that while we wait for the reporting tools to be developed?
And another one. This one has actually gotten so big that I think a merge error occurred on the erroneous branch itself. 
That merge error I reported earlier is a lot clearer now. My bet is it still arised from the same attachment point I highlighted earlier. (Post on December 15th)
I’m less certain about this one. Risking losing my correctly spotted merge error streak I’m still reporting it though.
The location of this branch is suspiciously low:
Not only that, but the attachment point looks even weirder:
This somewhat feels like maintaining a bonsai tree. Perhaps a good name if there ever were to be developed a game for this?
This actually got me thinking for an algorithm to detect merge errors. Common in many merger errors so far were long stretches without any branches coming of it.
sharp acute edges with rough, jagged surfaces on the 3d view are also a hallmark of areas where the segmentation has left out a large chunk of a cell, leaving it looking like part of it was chopped off. That can be a result of part of an adjacent cell getting painted unintentionally or due to sloppy work. The above image is an excellent example of that. I don’t know how feasible it would be to automate checking for signs like that, but if it is doable it would help. Maybe if a potential merger were detected like that, the cube and all of the cubes distal from that cube relative to the cell body be temporarily removed from the pool of cubes that can be assigned to people, until someone qualified takes a look at the cube with the possible problem (or, if a good system of weighting people is implemented, someone with a high weight).
I can only hope I’m wrong about these …
SAC #1
Just saw this path below - it looks like it is caused by a merger, too. Am I right?
Edit: In order to find it: one part has a suspiciously high vertical expansion 
—FIXED—
SAC #1
Maybe another one? 
Obligatory edit: Maybe I colored too few red… The whole connection seems a bit odd to me. It is going back to the origin of the cell, but in a slightly lifted angle… oh, well - I try to make another screenshot. A picture is worth more than 1000 english words from me 
Edit 2: Ok, red is the one from the former pic, slightly less red the one I hope still belongs to the correct cell and was not introduced by multiple mergers.
Edit 3: Oh well… meanwhile this pink path got so long that you will see it as soon as you zoom out from the cell and watch it from top
—FIXED—
Looks like we might have a problem, look on the right side, right next to the “start playing” button
SAC #1
Same as on December 23rd
Thanks for sending these guys! Mad helpful! I think we took care of all the current problems, let us know if we missed something/something new appears.
Hey guys, I’m closing this post and linking it over to the Merge Issues in SAC#1 thread. I figure we can start a new thread for merge issues in each cell as they come up. Post the mergers you catch in there from now on.