Eyewire Release Report 11/18/2016

amazing ganglions, neurons, eyewire, 3D neurons, citizen science, neuroscience, Seung Lab, MIT, Alex Norton, Amy Robinson

As detailed here, every few Fridays we’re sharing which bug fixes and tiny features our developers have released into the wild. Apart from bigger changes that have received their own posts, here are the releases on Eyewire since the last report.

  • A bug had appeared such that jumping to a cube moved players to the correct cube and cell but did not update the cell name accordingly. This source of confusion is now fixed.
  • We have pushed a potential fix for several bugs in watch mode. Those bugs included but were not limited to: mentors not seeing 3D meshes, only overview; mentors not seeing any 3D or overview; Eyewire freezing after a few seconds of watch mode; mentors seeing random dust segments in watch mode; mentors not seeing any trace besides the seed; players not seeing what mentors added; watch mode simply failing to initialize. It’s possible that some of these issues may continue, but hopefully not.
  • At some point, players stopped having their trace preserved in-cube when they jumped out to overview and then back in again. The same thing happened in inspect mode. This should also now be fixed. (Note: in the past, apparently it was also possible for a trace in regular play to be carried over to inspect mode by changing modes through overview. We have elected not to restore this, in favor of guaranteeing that Scouts & Scythes always see the real consensus for a cube when they inspect it.)

If it turns out that any of the above bugs persist for you, you may need to perform a hard refresh on your browser, log out and log in again, or empty the cache. But if this doesn’t work, please e-mail support@eyewire.org with as much information as you can provide (screenshots and browser console logs are great), including your browser/OS specifications. Please note that you will have the smoothest Eyewire experience if you use the most recent 64-bit version of Firefox or Chrome, a recent operating system like Windows 10/macOS Sierra/Ubuntu 16.04.1, and a machine with at least 8 GB of RAM.

Next report will be in a couple weeks, though in the meantime you may see new feature posts anyway. For science!

Leave a Reply

Your email address will not be published.