优化 Mathematica 中的插值
作为我工作的一部分,我经常需要可视化复杂的 3 维密度。我使用的一个程序套件将密度的径向分量输出为对数网格上的一组 781 个点,ri = (Rmax/Rstep)^((i-1)/(pts-1),乘以球面谐波。对于低对称性系统,球面谐波的数量可以相当大,以确保精度,例如,一个系统需要 49 个谐波,对应于
lmax = 6
。在使用 v.6 并使用 Interpolation
和设置 r 构建插值径向函数时,我将得到最多 49 个插值函数的总和,每个插值函数乘以不同的球谐函数。 = Sqrt(x^2 + y^2 + z^2)
,我会在一个多小时后停止 ContourPlot3D
而没有显示任何内容,这包括减少 InterpolationOrder< /code> 和
MaxRecursion
为 1。
出现了几种替代方案:
- 评估固定网格上的密度函数,并使用
ListContourPlot
代替。 - 或者,对径向函数进行线性样条绘制,并使用分段将它们缝合在一起。 (这本身就存在,因为我可以使用简化来帮助降低结果函数的复杂性。)
我最终使用了两者,因为 InterpolatingFunction
在其评估中给出了明显的延迟,并且最多有 49 个插值函数来评估,任何延迟都会变得明显。此外,ContourPlot3D
使用样条线速度更快,但它并没有给我带来我想要的速度。
我坦白承认,我没有在 v.7 上尝试过插值,也没有在升级后的硬件(G4 v. Intel Core i5)上尝试过。然而,我正在寻找当前方案的替代方案;最好是我可以直接使用 ContourPlot3D 的地方。我可以尝试其他形式的样条线,例如 B-spline,并可能结合使用 UnitBox
而不是使用 Piecewise
。
编辑:澄清一下,我当前的实现涉及为每个径向部分创建一阶样条线,将每个样条线乘以各自的球谐函数,求和并简化
上的方程每个径向间隔,然后使用分段将它们绑定到一个函数中。因此,我的实现是半解析的,因为球谐函数是精确的,并且只有径向部分是数值的。这是我希望能够使用 ContourPlot3D 的部分原因,这样我就可以利用数据的半分析性质。值得注意的是,径向网格足够精细,可以生成径向部分的良好表示,并且可以平滑插值。虽然这给了我显着的加速,但当我编写代码时,对于我当时使用的硬件来说,速度仍然很慢。
因此,我不会使用 ContourPlot3D
,而是首先生成函数(如上所述),然后在 803 笛卡尔网格上对其进行评估。我在 ListContourPlot3D
中使用的就是这一步的数据。由于这不是自适应网格,因此在某些地方这太当然了,而且我缺少功能。
As part of my work, I often have to visualize complex 3 dimensional densities. One program suite that I work with outputs the radial component of the densities as a set of 781 points on a logarithmic grid, ri = (Rmax/Rstep)^((i-1)/(pts-1)
, times a spherical harmonic. For low symmetry systems, the number of spherical harmonics can be fairly large to ensure accuracy, e.g. one system requires 49 harmonics corresponding to lmax = 6
. So, to use this data within Mathematica, I would have a sum of up to 49 interpolated functions with each multiplied by a different spherical harmonic. While using v.6 and constructing the interpolated radial functions using Interpolation
and setting r = Sqrt(x^2 + y^2 + z^2)
, I would stop ContourPlot3D
after well over an hour without anything displayed. This included reducing both the InterpolationOrder
and MaxRecursion
to 1.
Several alternatives presented themselves:
- Evaluate the density function on a fixed grid, and use
ListContourPlot
instead. - Or, linearly spline the radial function and use
Piecewise
to stitch them together. (This presented itself, as I could use simplify to help reduce the complexity of the resulting function.)
I ended up using both, as InterpolatingFunction
gives a noticeable delay in its evaluation, and with up to 49 interpolated functions to evaluate, any delay can become noticeable. Also, ContourPlot3D
was faster with the spline, but it didn't give me the speed up I desired.
I'll freely admit that I haven't tried Interpolation
on v.7, nor I have tried this on my upgraded hardware (G4 v. Intel Core i5). However, I'm looking for alternatives to my current scheme; preferably, one where I can use ContourPlot3D
directly. I could try some other form of spline, such as a B-spline, and possibly combine that with UnitBox
instead of using Piecewise
.
Edit: Just to clarify, my current implementation involves creating a first order spline for each radial part, multiplying each one by their respective spherical harmonic, summing and Simplify
ing the equations on each radial interval, and then using Piecewise
to bind them into one function. So, my implementation is semi-analytical in that the spherical harmonics are exact, and only the radial part is numerical. This is part of the reason why I would like to be able to use ContourPlot3D
, so that I can take advantage of the semi-analytical nature of the data. As a point of note, the radial grid is fine enough that a good representation of the radial part is generated and can be smoothly interpolated. While this gave me a significant speed-up, when I wrote the code, it was still to slow for the hardware I was using at the time.
So, instead of using ContourPlot3D
, I would first generate the function, as above, then I would evaluate it on an 803 Cartesian grid. It is the data from this step that I used in ListContourPlot3D
. Since this is not an adaptive grid, in some places this was too course, and I was missing features.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
如果你可以不用 Mathematica,我建议你看看 Paraview (美国政府资助的 FOSS,所有平台)我发现在可视化大量数据时它优于一切。
该软件的核心是“可视化工具包”VTK,如果需要,您可以找到/编写其他前端。
VTK/Paraview 可以处理几乎任何数据类型:结构化网格上的标量和矢量或随机点、多边形、时间序列数据等。在 Mathematica 中,我经常将网格数据转储到 VTK 旧格式 在最简单的情况下看起来像这样的
HTH!
If you can do without Mathematica, I would suggest you have a look at Paraview (US government funded FOSS, all platforms) which I have found to be superior to everything when it comes to visualizing massive amounts of data.
The core of the software is the "Visualization Toolkit" VTK, and you can find/write other frontends if need be.
VTK/Paraview can handle almost any data-type: scalar and vector on structured grids or random points, polygons, time-series data, etc. From Mathematica I often just dump grid data into VTK legacy format which in then simplest case looks like this
HTH!
如果确实是径向函数的插值拖慢了您的速度,您可以考虑根据您对样本点的了解对该部分进行手动编码。如下所示,这提供了显着的加速:
我用您的符号进行了设置。
lookuprvals
是一个包含 100000 个用于查找计时的r
值的列表。首先,以股票插值为基准
切换到 0 阶插值已经快了一个数量级(一阶几乎相同的速度):
我们可以通过直接计算指数来获得另一个 1.5 个数量级:
作为中间立场,做手动对数线性插值。这比上面的解决方案慢,但仍然比库存插值快得多:
如果您有足够的内存,我会在整个网格上缓存球谐函数和半径(甚至半径索引)。然后展平网格缓存,以便您可以按
此处所述重新创建网格。
If it really is the interpolation of the radial functions that is slowing you down, you could consider hand-coding that part based on your knowledge of the sample points. As demonstrated below, this gives a significant speedup:
I set things up with your notation.
lookuprvals
is a list of 100000r
values to look up for timing.First, look at stock interpolation as a basemark
Switching to 0th-order interpolation is already an order of magnitude faster (first order is almost same speed):
We can get another 1.5 order of magnitude by calculating indices directly:
As a middle ground, do a log-linear interpolation by hand. This is slower than the above solution but still much faster than stock interpolation:
If you have the memory for it, I would cache the spherical harmonics and radius (or even radius-index) on the full grid. Then flatten the grid caches so you can do
and recreate your grid as discussed here.