Posted by
ericbarnhill on
Dec 19, 2014; 8:15am
URL: http://imagej.273.s1.nabble.com/MIJ-Miji-and-Matlab-2014-a-b-tp5011002.html
Miji / MIJ has become a central tool for our lab. There appears to be
a difference in how Matlab handles MIJ in the 2014 builds. In the 2013
builds and prior, starting MIJ created a persistent instance that
could be used for the entire session (notwithstanding unusual errors).
In 2014, Matlab appears to have thrown a spanner in the works.
Any MIJ instance created only lasts until the next non-MIJ-related
command. So if I open MIJ, then run my image processing pipeline, the
instance of MIJ is no longer accessible. I have to open Miji again,
and it creates a second ImageJ toolbar, etc. Any previous images
opened in MIJ are no longer accessible and the windows can't even be
closed only minimised. Eventually memory starts to get sapped by all
the open dead windows.
It's something of an inconvenience since I would like to keep tweaking
the pipeline, running it, and comparing the new image to the previous.
I am happy to work on the problem myself if it is still outstanding,
someone should just get in touch with me about how to contribute.
Eric
---
Eric Barnhill
Clinical Research Imaging Centre
The University of Edinburgh
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html