User Portlet
| Discussions |
|---|
| I do this regularly. My approach is to generate an interpolating function, typically using ListInterpolation or SpatialEstimate, based on the xyz coordinates of the surface mesh nodes (you can use MeshCoordinates to extract the xyz coordinates of... |
| Thanks for the suggestion. But, as you say, this is suitable for display purposes only. The Head of the output expression is Row and cannot be used for calculation. Furthermore, I don't relish the prospect of having to apply a replacement rule... |
| Perhaps 1D finite elements – such as beams and the like – could one-day be incorporated into the Wolfram Finite Element Package? |
| Agreed. Thanks again for the detailed explanation. Much appreciated. |
| Update… Wolfram Support has confirmed that this issue is a bug. Hopefully, it’ll be fixed soon. |
| Neat - I’ve not come across SetAccuracy before. Another useful nugget to stash away for future use. |
| I think I've (partly) answered my own question. And thought my findings worth sharing. With a bit of trial and error, I've found that if I prescribe all dimensions used to define my Regions as integer values (by converting the length units from... |
| Thanks for the confirmations Jose. If the information ever becomes available, it would be really useful to know when the available satellite images were captured. Here's hoping... All the best, Ian |
| I think I may have stumbled across an issue with Mathematica’s built-in ConcaveHullMesh function that doesn’t seem to arise with Jon McLoone's NonConvexHullMesh resource function. The issue is illustrated in the attached notebook. My guess is that... |
| Hi Brett, I've figured out how to build the contour plot on a cell-by-cell basis. Just need to explicitly specify a ColorFunction and set ColorFunctionScaling -> False as per the attached notebook. This seems like a good approach for contouring... |