27/08/2010

Neuromantic V1.7.5 is available

As promised, here is a download link for the newest version of
Neuromantic (V1.7.5) produced for DIADEM. It's a bit.ly shortened
link that lets me keep track of the number of downloads and vaguely
where they're coming from, but it points directly to my DropBox
account.

http://bit.ly/buYykd

The contents of the zip should work in a self-contained fashion, and
should not require any files from any previous downloads.

Now, I'm pretty sure that I've included all the dependent DLLs in the
zip file, but I don't have a clean platform to test on so I can't be
sure. Let me know if it fails on start-up and I'll host the missing
files asap.

The main changes to the application are:
* Dynamic memory management. You should hopefully not get annoying
access violations when you load in a stack that's too big, as
Neuromantic will automatically load/unload images dynamically to keep
the memory footprint acceptable. There will probably still be memory
issues if you attempt to visualise large stacks in 3D, though, which
is something I may address in future now that I have a working build.
* Multi-stack GUI - this lets you use large-tiled projects and show/
hide different tiles as tiled, as well as manually entering offsets.
The "Load/Save Tiled Project" menu options will save all the stack
positional data to an .nproj file (the reconstruction itself will
still need to be save separately to SWC). If you lose the multi-stack
GUI, open it again through Window->Show Multistack GUI
* Custom labelling schemes - you can now change the colours associated
with each segment type, so no more endless yellow after segment type
6. See also Load/Save labelling scheme on the main menu.
* A few 3D GUI fixes - the aspect ratio now remains correct when
resizing the window, which had been bugging me for ages, and the lines
are properly anti-aliased.

For other minor changes see the _README.txt file.

Feel free to pass on the download link to anyone who might be
interested (once you're sure it's not missing any files!).

In general, I shall be posting links to new version on the NeuromanticUsersGroup, so please join that if you're interested.

Labels: , , ,

03/03/2008

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: , , , , , ,

27/07/2007

Update on Multiple Stacks with Neuromantic

At CNS 2007, several people requested functionality for Neuromantic such that multiple image stacks could be loaded in simultaneously, some as a prerequisite before it could be useful to them.

Now, mainly because I find it hard to resist a challenge, I have been working on this very problem. It is not complete yet, but in my current test version it is now possible to load and display several stacks (although the semi-automatic tracing has not yet been updated to work with this). Also, it is not yet possible to register the stacks yet, but that's just a straightforward case of adding functionality to the GUI to alter the various stack parameters.

As well as each stack having its own global offsets in the space, each individual stack bitmap will be able to be perturbed in x,y a little to account for any jitter that may be present, in a similar way to the Reconstruct application.

Finally, I'll need to sort out some appropriate memory management so that the application will load/free bitmaps as required dependent on the memory available.

Labels: , , ,