Neuromantic V1.6.2 now available!

OK, I have uploaded Neuromantic V1.6.2 to the site - I've made sure the ZIP file works this time, also ;)

V1.6.2 mainly adds some bug fixes and minor features over V1.6.1, and I'm quietly confident that I've finally squashed the horribly annoying byzantine error that I've been trying to track down for several releases.

I've altered the selectable bounding boxes on compartments so that they're now the entire width of the compartment, rather than always 10 pixels either side. Lone nodes (with parent nor child) also display their radius now in the form of a circle around the midpoint, and it should be easier to select/drag around the root soma point of a tree that's surrounded by child compartments.

Another handy addition is the ability to press Ctrl+W and cycle through all the currently selected segments. This could be useful when correcting trifurcations or similar.

In terms of semi-automatic reconstruction, a median radius filter operation has been added that helps compensate for radius estimation errors. The radius of each compartment is simply calculated as the median of the estimated radii of a 3 compartment neighbourhood along the neurite.

It's also now possible to Autoselect overlapping points i.e. points that have exactly the same coordinates as another point in the tree. It was primarily added for Duncan Donohue, who's currently administrating the NeuroMorpho archive, and shouldn't be needed in the standard course of a reconstruction. In the case of overlapping identical subtrees, it will currently just select one of the subtrees arbitrarily (depending on ordering in the list). I believe that it should select entire overlapping subtrees due to the way the tree sorting algorithms work, but it's conceivable that in some circumstances it will select some from both - let me know if this happens.

Labels: , , ,


Composite stack support

Neuromantic V1.6.0 will be released tomorrow - the main update here will be the support of composite stacks made of multiple image stacks. These composite stacks may be saved and loaded via project files (*.nproj).

For the first release, there will be several limitations:

* All stacks will be loaded at once and remain so, so no memory saving is made. This constraint will be quickly relaxed in future releases so that you can free/reload stacks as desired.

* Rotated composite stacks (if you've rotated in X/Y or Z) cannot be saved with a project file. This can be circumvented initially by saving the composite stack prior to rotation, and making sure that the stacks are rotated back to the original position before saving the reconstruction. This constraint will also be relaxed in future, although it will take longer as it relies on me finishing the improved stack viewing algorithms.

Labels: , , , , , ,