FAQ

= Camera issues =

I get the error that a core property is read-only?
Due to a bug in the HamamatsuHam driver (which is not Open Source, unfortunately, otherwise we could try to fix things), the error messages are not quite stellar. They are even outright misleading.

The issue, most likely, is that Fiji reserves so much RAM for its own use that the Hamamatsu driver is unable to reserve space for its image buffers.

Just go to Edit>Options>Memory & Threads... and limit the RAM Fiji uses to, say, 1GB. Restart Fiji, and all should be fine.

= Community =

How to share images?
We have a WebDAV scratch now (for Windows, please install Cyberduck since Windows Explorer's WebDAV support is incapable of communicating with our server, for Linux or MacOSX refer to the capabilities of Nautilus and Finder, respectively).

Note, however, that Windows' network stack is not able to perform fast uploads. If you can, use Linux or MacOSX. The difference is huge: in one particular case, we measured ~300kB/sec on Windows and 17MB/sec on Linux.

The scratch space is located at http://openspim.org/scratch/. For core OpenSPIM developers, there is a shared account 'webdav', a write-only account will be added soon.

How to report bugs
We have a ticket system. If you add new tickets, please make sure to


 * the category is OpenSPIM
 * assign the ticket to yourself if you intend to solve it
 * add a target version if you want the ticket to show up in the roadmap
 * add a concise summary and additional useful information in the description
 * if you need this ticket to be visible only to the core developers of OpenSPIM, mark it as 'private'

Once you added a ticket, you might want to go back to it and make it a child of a goal ticket in the Relationship box.

= Software =

How do I autostart µManager when Fiji starts?
In Fiji, run the command Plugins>Macros>Startup Macros... and add the following lines to the end:

macro AutoRun { run("Micro-Manager Studio"); }

How do I autostart the OpenSPIM plugin when µManager starts up?
If you want the SPIM plugin to be called everytime when Micro-Manager starts, add the following lines to the Fiji.app/MMStartup.bsh file:

setAccessibility(true); import org.micromanager.MMStudioMainFrame.PluginItem; for (PluginItem plugin : gui.plugins_) if (plugin.className.equals("SPIMAcquisition")) { plugin.instantiate; plugin.plugin.show; }

How do I start µManager from the command-line?
There are two ways, really. The Fiji way:

fiji-win32 --run Micro-Manager_Studio

Call the Studio directly, without first starting ImageJ:

fiji-win32 --main-class=org.micromanager.MMStudioMainFrame

Can I run OpenSPIM with Windows 7 or 8?
At the time of writing, only Windows XP is supported, because there are problems with the DCAM driver. In our tests, it would install, but µManager was not able to find the camera on Windows 7.

How can I build the OpenSPIM software myself?
Please have a look at this page.

= Debugging =

Look at the CoreLog
Whatever you do, first have a look at the file CoreLog .txt, located in Fiji.app/ or whatever directory Micro-Manager was started in.

When Micro-Manager does not list the driver

 * 1) Make sure the .dll is present in dist/mm/Win32/
 * 2) Use the Dependency Walker to detect missing dependencies

Micro-Manager just crashes when I connect
Micro-Manager's memory management is not very safe on the driver side. Try to start Fiji with less memory reserved for Java, e.g. --mem=512m.

If that does not help, try to find out what's in the core log, and if that fails, too, you might have more luck.

Using Visual Studio's interactive debugger
Start Fiji, and before starting Micro-Manager use Visual Studio's Debug>Attach to Process... to attach to the process. After that, you may set breakpoints (optional) and then start Micro-Manager in Fiji.

Using Eclipse to debug MicroManager/SPIM Acquisition

 * 1) Make sure you have Eclipse installed.
 * 2) Add Fiji's JRE to Eclipse:
 * 3) Window -> Preferences; under Java, select Installed JREs and click Add...
 * 4) Use Standard VM.
 * 5) Set the JRE Home to Fiji.app/java/win32/jdk1.6.0_24 (or similar). Eclipse should fill in the rest.
 * 6) Click Finish.
 * 7) Check the checkbox next to the newly-added JRE.
 * 8) Create a new project for Micro-Manager Studio:
 * 9) File -> New -> Java Project...
 * 10) Uncheck "Use Default Location"
 * 11) Point Location to /src/fiji/3rdparty/micromanager/mmstudio
 * 12) Eclipse should auto-configure all sorts of useful things.
 * 13) Click Next.
 * 14) On the Libraries tab, click Add External JARs...
 * 15) From /src/fiji/3rdparty/bin_Win32/jars/:
 * 16) * bsh.jar
 * 17) * commons-math-2.0.jar
 * 18) * ij- .jar
 * 19) * MMCoreJ.jar
 * 20) * MMAcqEngine.jar
 * 21) * swing-layout-1.0.4.jar
 * 22) * swingx-0.9.5.jar
 * 23) Click Finish.
 * 24) Create a project for SPIMAcquisition:
 * 25) File -> New -> Java Project...
 * 26) Uncheck "Use Default Location"
 * 27) Point Location to /src/fiji/3rdparty/micromanager/plugins/SPIMAcquisition
 * 28) Let Eclipse auto-configure things.
 * 29) Click Next.
 * 30) On the Projects tab, click Add... and select the mmstudio project added above.
 * 31) On the Libraries tab, click Add External JARs...
 * 32) From /src/fiji/3rdparty/bin_Win32/jars/:
 * 33) * ij- .jar
 * 34) * MMCoreJ.jar
 * 35) Click Finish.
 * 36) Depending on your workspace settings, you may need to reduce the enforced JRE level for both projects:
 * 37) Right click on each project and go to Properties.
 * 38) Select Java Compiler.
 * 39) Enable project-specific settings and set the Compiler Compliance Level to 1.6 (depending on the JDK used by Fiji).
 * 40) Click Apply then OK.
 * 41) Set up the debug configuration:
 * 42) Run -> Debug Configurations...
 * 43) Create a fresh launch configuration
 * 44) Use SPIMAcquisition as the project.
 * 45) For the Main class, click Search... and find ij.ImageJ
 * 46) On the Arguments tab, under VM arguments, pass the following:   (modifying as appropriate).
 * 47) On the Classpath tab, select SPIMAcquisition, then Add External JARs...
 * 48) From fiji/3rdparty/micromanager/dist/jars:
 * 49) * MMAcqEngine.jar
 * 50) Click Apply.
 * 51) Click Debug to make sure everything works.