I found a bug with the overlay function. If I try to add an overlay image with a path in the filename, it embeds the state path in the kml file, thus when I load the kmz file into Google Earth, it goes looking for the file at the stated path. It does not use the file embedded with the kmz file.
I found this function much better than the standard matlab functions. I also was able to read VOB files off a DVD. I modified it slightly to read my video as monochromatic, thus saving memory. It would be nice to add this functionallity to the standard release.
From my understanding, this isn't a strict simulated annealing program, but more of a pure Monte Carlo.
To be simulated annealing, the 'Generator' would need to be modified so that the size of the changes it makes to the model parameters shrinks as the temperature shrinks.
04 Jun 2014
KML Toolbox v2.7
Create KML/KMZ files and view them in Google Earth. Supports 3D models, contours, overlays, and more
Hi, very good work thanks! Using the transfer function its easy display plots on google earth. To set the coordinates, one can change line 80 in the transfer.m file.
(default:[west,east,south,north] = deal(xlim(1),xlim(2),ylim(1),ylim(2));)
[west,east,south,north] = deal(98.804192,100.834833,38.663767,39.876606);
That error means that at least one value in at least one of your images is not a non-negative integer value.
I have not added error checking, as the point of this is speed. But if you wanted to ensure that you do not get this error, you can add the following lines to the top of this function:
J = J - min(J(:));
K = K - min(K(:));
J = round(255.4*J/(max(J(:)));
K = round(255.4*J/(max(J(:)));
All this does is recast the image into the 0-255 range. This should avoid the error you were getting, as long as you don't have any NaN or complex pixel values. Again, I didn't want to add this to the code, as I suspect the main use for this will be for iterative programs, and recasting is usually handled well in advance of any attempt to obtain MI or joint entropy..
But, if you add these lines and it continues not to work, please let me know, and if possible include the data you are using.
have you tested your code?
There is a bug that when calculating h(x,y).
Subscript indices must either be real positive integers or logicals.
Error in ent (line 39)
jhist(yy) = xx;
Error in testENT (line 6)
[jhist, jent, MI] = ent(imgA,imgB);