Stuart Berg

The latest production node (`0716`) also seems to suffer from this issue. In case it's useful, the following supervoxels have 0 size, but have non-zero mappings (as shown). Click for...

Note to self: Due to the fact that I've been writing "small" supervoxels as 0-byte files, I should go back and verify that I haven't inadvertently overwritten a few valid...

Apparently this issue can affect `/split-supervoxel`, too. I guess a client (neu3) must have created one of these weird "splits" that didn't change the shape of the supervoxel, thereby creating...

@DocSavage >there could be a situation where a split-complete message is successful but the actual split is not I don't understand. I guess I'll talk to you in person.

BTW (unrelated): I added a [`pyroaring` recipe to conda-forge][1], so conda users can now install it with the following command: [1]: https://github.com/conda-forge/pyroaring-feedstock ``` conda install -c conda-forge pyroaring ``` Perhaps...

Thanks for the response. I don't know if I need 64-bit support after all :-) >Would you want to do a pull request for the README to phrase it yourself?...

There is some hope that the situation will magically improve when we upgrade to Python 3, since it uses the "New GIL" implementation: http://www.dabeaz.com/python/NewGIL.pdf But it's difficult to say for...

Simplifying that window is a great idea. Currently, it exhibits the classic anti-pattern of a UI that too closely reflects the design of the underlying code, rather than the user's...

Based on the discussion above, it sounds like you can just discard the "edge region" features, which eliminates the "shape" checkbox...

@DocSavage I need help interpreting the error in the DVID log. Is that the message one would normally expect when using `HEAD .../tarfile/` if there are supervoxel meshes missing from...