Proper reaction to merged paths?

Eyewire Questions
#1

The GrimReaper is normally pretty fast with his/her scythe and so it is usually a minor problem… However, we SAC ninjas messed up the area around the point, where we started and it is weekend, so…


When I see I got a cube assigned that clearly doesn’t belong to the current path, should I:

 - mindlessly fill in the wrong branch, hit submit and be happy about double points for doing wrong, or
 - skip the cube (That’s what I do at the moment), or
 - call 911, or
 - hit finish and hope others will do the same so the branch won’t spawn new cubes of the wrong cell. (That’s what I think, I should do)


Edit:
 I just heard we are tracing multiple starbursts within the challenge. That’s a bit confusing… So, answer 1 seems to be correct for “Starburst Challenge”. However, the question is still valid for all the other single cells :slight_smile:
#2
As you already added in an edit to your question, the team simply opted to added new SAC branches to follow within the same overview. It aren't merge errors. If anything they are 'awesomeness' indicators, since after just 1 day of stargazing they had to add new synapses from which to trace since we already found the cell body of the first synapse. :)

Pfuh .. we starburst ninjas don't mess up. What did you think. ;p
#3

I just want to push that one since J-Cell #5 contains another cell right now :slight_smile:

#4
Possibly the error is as indicated below.

Z6dLhtQ.png1278×845 514 KB
#5

@nkem if you see a cueb that obviously contains a merger, type /debug into chat and email the resulting cube number to support@eyewire.org with the subject "merger report"


Does that answer your question?
a
#6

So if you are 100% positive that you are on a merger, you can reduce the likelihood that it will extend by not tracing across the cube. This will, as @nkem suggested, reduce the threshold for spawning new branches, therefore reducing the likelihood that the merger will grow.


Iif If you do this, please always type the /debug command  into chat and email the cube number to support@eyewire.org with the subject line "merger report"


NoNote that if you do this on cubes that are not mergers, it will severely disrupt the game so please only employ this strategy if you are positive that the cube is a merger and always report cubes to support.
so