[OpenSPIM] OpenSPIM 64-bit [0000129]

[Luke Stuyvenberg]

Hey Nikul,

On 02/05/14, Nikul  wrote:
> If you could send me the code you used to produce the 32 bit self extracting archive, I can try
> modifying it to have a 64 bit version in the coming weeks. On a related note, references to
> commons-math3-3.2.jar might be necessary in the build xml files for 32 bit as well. I see that
> the switch to commons math 3 was made recently but I wasn't able to find it included in the 
> build files.

The self-extracting archive is produced by make-dev-env.sh in the main directory, but I hasten to point out that it doesn't include any of the actual code -- rather, it contains instructions to download the code from github (in fact, the development environment it sets up has the git source code management software very well-integrated.) Github is probably the best way to get the changed code to us, though it would involve deep familiarization with the SCM software (and an account/fork of our project on github to which to upload, followed by a pull request...).

Meanwhile, I added the reference to commons-math3-3.2.jar some time ago, but not on the main openspim branch -- it's there now, so executing 'git pull' will technically bring in that change (but it will probably also create some annoying merge conflicts...).

> In the video mode, I am able to get 50 fps in openspim, so it seems to be stemming from 
> repeated calls to snapImage() as opposed to initiating a sequence acquisition.



I suspected this might be the case. The main problem I've had is wanting to be sure that the motors had stopped at the correct position and grabbing a frame there. Continuous drive, as suggested by Michael Webber, makes for an excellent workaround to this concern; however, it has a bit of a shaky standing in the OpenSPIM software at present. There's some issues involved in it that I haven't had the opportunity to sort out yet; given the interest, I'll plan to give it a second look in the future.


Luke