get the slope and some statistics of the slope.Instructions can be found at this solution.

This allows you to pass JVM options (such as the total and max memory for the heap) on MATLAB startup. That is to create or modify a java.opts file in the MATLAB startup directory. There is a solution to running out of Java memory that is usually safe, although sometimes produces unintended consequences if the numbers are made too large. Once all the java memory is used up, there is the potential of locking up MATLAB, as there might not be enough room to even create an out-of-memory dialog. One caution is that this space is shared between any objects you might create as well as objects created by the Desktop, Editor, Current Folder, etc. This is the demo that was running at the time of the jump: you can see the commands to discover the java memory, as well as the fact that the array creation ups the used java memory but does not affect the memory for MATLAB array creation: free = .freeMemory The actual double array isn’t shown on this graph as it is created and cleared faster than the sampling time of the graph. The jumps in the blue represent the objects created as I manipulated the editor and command window to set up this demo, and the dips are when those objects get garbage collected, freeing up memory. You can see this in the following animated graph, where the green (total memory) is bumped up when I create the large array of java doubles. When the amount of free memory starts to get low, java will increase the total memory until it equals the the max memory.

The total memory is the number of bytes allocated to the total heap space which is the size of the objects created + the free memory. The free memory is the number of bytes available in the heap space for creating new objects. To find out how much memory is available for creating Java objects, there are three numbers of importance: the free memory, the total memory, and the max memory. On a 32-bit windows machine, MATLAB might have up to 3 GB available for creating matrices and other MATLAB objects but only 64 or 128 MB (by default) for creating java objects. When a Java object is created in the MATLAB workspace, it is actually created in the Java heap space and not the main memory used by MATLAB. Following up with my previous post about using Java objects in MATLAB, this week I’m going to discuss the memory issues that can crop up.

Java for matlab