Differences

This shows you the differences between two versions of the page.

--- blogtng:2010-06-07:notes_on_mipav_tried_with_win32 [2010/06/09 22:05] – added installing procedure of visualization modules. kota
+++ blogtng:2010-06-07:notes_on_mipav_tried_with_win32 [2020/11/26 09:11] (current) – external edit 127.0.0.1
@@ Line 12: / Line 12: @@
 **Installation procedure**
 quote from installation instruction\\
-<quote>
+<blockquote>
 After installing the MIPAV from the jar file, be aware that for full functionality you will need the following installed into the Java Virtual Machine you will be using to execute MIPAV:\\
@@ Line 33: / Line 33: @@
 Nightly md5sum: d6ae2449be40a418b74b162a3f94255c
 </code>
-</quote>
+</blockquote>
 ** === comment on istallation === **
-Not necessary to have above java modules for installation (but as instruction says, some functions will not do job. I will check later). \\
+Not necessary to have above java modules for installation (but as instruction says, some functions will not do job. I will check later). For manually setting class path for visualization, google "set Classpath" or so. \\
-JOGL (Java bindings for OpenGL(C++ library) ) is not straight forward since one should manually place files and also set environment variables in your system (not necessary if you are using only MIPAV, since you must set the path for MIPAV anyways).
-===== Installing Java3D =====
-Go to java3D site and download Installer:\\
-https://java3d.dev.java.net/binary-builds.html\\
-After installation, check if CLASSPATH is correctly set, just be sure.
-===== Installing JOGL =====
-Go to the JOGL site below and download JOGL.
-http://jogamp.org/deployment/archive/jogl-latest/
-In my case, I downloaded jogl-1.1.1a-windows-i586.zip, unzip the archive and then placed lib file under\\
-C:\SUN\jogl\ \\
-If you google, you could find many cases that recommends placing files under jre/lib, but this is not encouraged by the JOGL user guide. \\
-<quote>
-The JOGL distribution for developers comes in the form of a zip archive which contains the Java classes to call OpenGL from Java, as well as the associated JNI native libraries. JOGL depends on some run-time support classes and native code provided by the GlueGen project; these classes and native code are also provided in the zip bundles.
-If you are developing a new application which uses JOGL, download the zip archive for your platform (for example., jogl-[version]-windows-i586.zip) and unzip it. Modify your CLASSPATH environment variable to include the full paths to jogl.all.jar, nativewindow.all.jar, gluegen-rt.jar, and optionally newt.all.jar; for example, ".;C:\Some\Other\Package\foo.jar;C:\Users\myhome\jogl-[version]-windows-i586\lib\jogl.all.jar;C:\Users\myhome\jogl-[version]-windows-i586\lib\nativewindow.all.jar;C:\Users\myhome\jogl-[version]-windows-i586\lib\gluegen-rt.jar;C:\Users\myhome\jogl-[version]-windows-i586\lib\newt.all.jar". (If you did not previously set the CLASSPATH environment variable, you may want to make sure that ".", the current directory, is on your new CLASSPATH.) Modify your PATH environment variable (Windows), LD_LIBRARY_PATH environment variable (Solaris and Linux), or DYLD_LIBRARY_PATH environment variable (Mac OS X) to contain the full path to the "lib" directory; for example, on Windows, add "C:\Users\myhome\jogl-[version]-windows-i586\lib" to your PATH using the System control panel, Advanced tab, Environment Variables button. At this point your Java installation should be able to see the JOGL class files. Users of IDEs such as NetBeans and Eclipse should consult the IDE's documentation to see how to add jar files and native libraries to their current project.
-Note that the per-platform zip archives contain many more jar files than just the three or four mentioned above. The additional jars illustrate how JOGL may be partitioned to achieve a smaller deployment size, in particular on smaller devices.
-Dropping the JOGL jars and native libraries into the extension directory of the JRE is strongly discouraged. Doing so will cause conflicts with third-party applications launched via Java Web Start, and causes confusion later when upgrading the distribution.
-</quote>
-Find instruction for manually setting files and env. variables, in case you will be using JOGL for development. I referred to the link below.
-http://www3.ntu.edu.sg/home/ehchua/programming/opengl/HowTo_JOGL.html
-[[http://jogamp.org/deployment/jogl-next/javadoc_public/|JOGL Java DOC]]\\
 **Installing Plugins**
@@ Line 104: / Line 73: @@
 http://mipav.cit.nih.gov/documentation/api/gov/nih/mipav/model/algorithms/filters/package-summary.html\\
-<quote>
+<blockquote>
 c:\usr\local\bin\ITKAlgorithmsJava.dll
 c:\usr\local\bin\ITKBasicFiltersAJava.dll
@@ Line 118: / Line 87: @@
 This path of c:\usr\local is hard-coded into the build for the INSTALL project.
 You can relocate these files in a different folder and on a different machine, but you must keep the relative path locations between the ITK*Java.dll files and InsightToolkit.jar file the same. The reason for keeping the path relative is because the software in the InsightToolkit.jar file searches for the runtime DLLs using the relative path of "..\..\bin".
-</quote>
+</blockquote>
 ITK: http://www.itk.org/itkindex.html
@@ Line 124: / Line 93: @@
 **visualizaiton**
-Documentation is under development and could not really evaluate. \\
+Documentation is under development and could not really evaluate, but then: \\
---> install java3D and maybe JOGL as well. currently some funcitons seems not working (no error message, but just stalls. )\\
+  * tri-plane view of 4D sequence synchronized with the slider of the original stack.
+  * surface rendering is not supporting 4D\\