Skip to main content
Mathematica

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • $\begingroup$ +1, thanks. It helps to save the data. Remains a minor annoyance to have to reprocess the Interpolation between sessions when working with large irregularly gridded datasets, though. I'm still hoping someone finds a hack to store the interpolation, maybe by Blocking a key expression during the export/import... $\endgroup$ Commented Mar 21, 2012 at 17:58
  • $\begingroup$ @JxB, I doubt that is possible, since the bug was in the C code, but who knows perhaps someone has a clever idea. Why don't you send me an email of this site and we can have a chat. My email is ruebenko at the company name.com. $\endgroup$ Commented Mar 21, 2012 at 20:59
  • $\begingroup$ @ruebenko I just tried the workaround with NDSolve`FEM`ElementInterpolation[{mesh}, vals] and it returns Removed[$$Failure]. Are you sure it works (I use version 8.0.4)? $\endgroup$ Commented Aug 19, 2012 at 11:35
  • $\begingroup$ @ruebenko Which versions of Mathematica are affected by this bug? $\endgroup$ Commented Aug 19, 2012 at 14:13
  • 2
    $\begingroup$ @AlexeyPopkov, also fixed in the development version. For this slightly different case you can use mtemp = int[[3, 1]]; mesh = NDSolve`FEM`ElementMesh[ mtemp[[1]], {NDSolve`FEM`MeshElementCreate[ NDSolve`FEM`TriangleElement, mtemp[[2, 1, 1]]]}] to recreate the underlying mesh. Hope this helps. $\endgroup$ Commented Aug 20, 2012 at 20:13