Databases
StackOverflow2013
Postsdbo
POMemory exhaustion while running NDSolve
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMemory exhaustion while running NDSolve
    primarykey
    data
    text
    <p>I run into the "No more memory available" error message in Mathematica. I understand that "Parallelize[]" isn't (obviously) going to help me. Neither has "ClearSystemCache[]".</p> <p>What gives? Do I just need more RAM?</p> <h2>My Code</h2> <pre><code>Needs["VectorAnalysis`"] Needs["DifferentialEquations`InterpolatingFunctionAnatomy`"]; Clear[Eq4, EvapThickFilm, h, S, G, E1, K1, D1, VR, M, R] Eq4[h_, {S_, G_, E1_, K1_, D1_, VR_, M_, R_}] := \!\( \*SubscriptBox[\(\[PartialD]\), \(t\)]h\) + Div[-h^3 G Grad[h] + h^3 S Grad[Laplacian[h]] + (VR E1^2 h^3)/(D1 (h + K1)^3) Grad[h] + M (h/(1 + h))^2 Grad[h]] + E1/( h + K1) + (R/6) D[D[(h^2/(1 + h)), x] h^3, x] == 0; SetCoordinates[Cartesian[x, y, z]]; EvapThickFilm[S_, G_, E1_, K1_, D1_, VR_, M_, R_] := Eq4[h[x, y, t], {S, G, E1, K1, D1, VR, M, R}]; TraditionalForm[EvapThickFilm[S, G, E1, K1, D1, VR, M, R]]; L = 318; TMax = 10; Off[NDSolve::mxsst]; Clear[Kvar]; Kvar[t_] := Piecewise[{{1, t &lt;= 1}, {2, t &gt; 1}}] (*Ktemp = Array[0.001+0.001#^2&amp;,13]*) hSol = h /. NDSolve[{ (*S,G,E,K,D,VR,M*) EvapThickFilm[1, 3, 0.1, 7, 0.01, 0.1, 0, 160], h[0, y, t] == h[L, y, t], h[x, 0, t] == h[x, L, t], (*h[x,y,0] == 1.1+Cos[x] Sin[2y] *) h[x, y, 0] == 1 + (-0.25 Cos[2 \[Pi] x/L] - 0.25 Sin[2 \[Pi] x/L]) Cos[ 2 \[Pi] y/L] }, h, {x, 0, L}, {y, 0, L}, {t, 0, TMax}, MaxStepSize -&gt; 0.1 ][[1]] hGrid = InterpolatingFunctionGrid[hSol]; </code></pre> <h2>Error message</h2> <pre><code>No more memory available. Mathematica kernel has shut down. Try quitting other applications and then retry. </code></pre> <h2>My OS specs</h2> <p>Intel Core 2 Duo with 4.00 GB ram, 64 bit OS (Windows 7)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDr. belisarius
    1. USdrN
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMemory exhaustion while running NDSolve
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMemory exhaustion while running NDSolve
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMemory exhaustion while running NDSolve
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONot that it matters here probably, but if you ever get this message the first thing to do is First, set $HistoryLength=0. A number of these error messages for larger programs are caused by this. Second, Isolate the actual line of code which causes the memory problem. If possible run it in a way that you can monitor the memory usage.
      singulars
      1. POMemory exhaustion while running NDSolve
      1. USSearke
    2. CO@Searke That is a very useful suggestion. If I may ask, how should I _isolate_ the portion of code that is causing the problem? I am new to Mathematica and I don't know of functions off the top of my head.
      singulars
      1. POMemory exhaustion while running NDSolve
      1. USdrN
    3. CO@DNA See related [answer on memory usage control](http://stackoverflow.com/questions/6773009/subkernel-memory-control-in-mathematica/6805237#6805237).
      singulars
      1. POMemory exhaustion while running NDSolve
      1. USAlexey Popkov
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload