The help of Mathematica doesn't say so much about the PrecisionGoal for NDSolve, and I never considered much about it even after I met the warning message
NDSolve::eerr
for several times when I was trying to solve a set of PDEs these days: every time I met it I would simply considered it as a proof for the defect of my assumption for the initial or boundary condition, and my resolution strategy for it is to modify the conditions or sometimes I will also lower the value of the PrecisionGoal as the help says.
However, this time I can't ignore it anymore, for I accidentally found that for one of my assumptions, the suitable PrecisionGoal for it is a negative integer…
The thing named "Precision" in my mind was always a positive integer, but this time it is negative! Why?…… What's the exact effect of "PrecisionGoal" option for NDSolve?


More Information(click on the yellow box to open it). About the log, if you look at the plots, you'll notice that it reduces to exactly what you'd expect if I fix egdx/xto be exactly 0.01 (ie, it's 2 then). About the "best place" thing, I meant that this is really a general question about putting things in dimensionless form; I talked a little about this here. But in general I guess some sort of math site would be better for that (it's not a Mathematica question really) – acl Aug 02 '12 at 13:00Solve[(s == 2 v) /. s -> 6, {v}],now I know that s has the unit m, 2 has the unit s and v has the unit m/s , so after I set s as 6 and solve the equation, though I only get v->3 I will still know the unit of 3 is m/s. – xzczd Aug 02 '12 at 14:22