"bayu " <gie.arie@yahoo.com> wrote in message
news:lmgtmk$coc$1@newscl01ah.mathworks.com...
> Hi Everyone i need some help, currently working on my final project about
> real option pricing, everything work well (i use some a little value for
> partition) until my lecture ask me to make the partition value smaller....
> my calculation is okay but when I try to plot it i got problems
> 1. figure 1 & 2 did not show up, only the colorbar and the meshgrid 3d did
> not shown. how to resolve it?
> 2. figure 3 shown properly the mesh grid, but because of the small
> partition it make the colormap did not shown properly so it can be said
> only black colour is shown in 3d object. how to change the range colour?
>
> I use matlab for Mac OS X R2013 and mac mid 2012 non-retina, with RAM 4,
> hdd 500,
> is the problem because of my hardware ? because i need to run 6000 x 6000
> matrix and it need almost 2 hours to process/iteration(trial)~(I input 10
> trial) when i saw the task manager my RAM space 3.99 is used
>
>
> here they are my code:
You've posted a LOT of code (though not all of it, I suspect) but we can't
run it because 1) it depends on what you type at various INPUT statements
and 2) it depends on the contents of variables you haven't showed us.
Simplify this down to a SMALL section of code and instructions that people
can execute and with which you can reproduce the behavior. Post that code
and instructions to the group (please do NOT send them to me directly.) Then
readers of the group can try it out and see if they can reproduce the
behavior you're describing.
As for the performance, I've got two ideas.
1) You're displaying a LOT of text to the Command Window with FPRINTF. Try
commenting those out or guarding them by IF statements controlled by a
variable you define at the top of your code, like:
debugging = false;
if debugging
fprintf(...
end
That way the text only displays when you turn debugging on.
2) You have a LOT of calls to HOLD throughout your code. My guess is that
you keep on adding line after line after line in the same axes, which will
cause rendering to slow down as the renderer has to figure out what to
display where and what's concealed "underneath" other graphics objects.
*snip*
--
Steve Lord
slord@mathworks.com
To contact Technical Support use the Contact Us link on
http://www.mathworks.com
