Introduction
I recently wondered whether I could use Tableau to graphically process results from finite-element models. This post just begins to answer that question.
I began to answer the question by loading an interesting 2D finite-element grid from some work I did a few years ago. As shown in Figure 1, this numerical modeling work was in south Florida, in the region known as the Everglades. A numerical model that simulates the simultaneous movement of groundwater and surface water was the actual job being completed.
The purpose of this post is to show results from my initial assessment of Tableau’s capabilities with respect to using it to process numerical model results. Although this work is just the beginning of this investigation, initial results indicate that Tableau can be used to handle some aspects of a numerical modeling job (at least in 2D).
If you like this article and would like to see more of what I write, please subscribe to my blog by taking 5 seconds to enter your email address below. It is free and it motivates me to continue writing, so thanks!
Loading the Nodes and Finite-Elements
Most numerical models use two data sets to define the computational nodes and the finite-elements. The nodes are defined as a node number, x coordinate, and a y coordinate. For a triangular finite-element grid like the one used in this example, the elements are defined as an element number, node #1, node #2, and node #3, as well as a material property integer.
For this example in Tableau, I simply made one file by merging the node and element files in Excel by using a little creative data mapping. The resulting data file for this example is shown in Figure 2.
Notice that for each triangular element, there are four entries needed to complete the triangular polygon because the fourth entry is needed to get back to the original starting node of the element. The path variable (1,2,3,4) describes the order in which Tableau will draw from point to point to complete each triangular element. In this example, there are a total of 28,027 finite-element nodes and 53,049 elements.
The finite-element nodes are not uniformly distributed in space as shown in Figure 3. There are more nodes where more detailed quantitative assessment of the hydrological system was needed, especially along the eastern coast and down south in the Miami-Dade area.
The finite-elements are drawn very nicely by Tableau. Figures 4 through 7 give examples of what these look like.
The elements are drawn in Tableau as polygons, which gives you the ability to label and color the elements.
Conclusion
Tableau does a good job in drawing the nodes and elements, although some thought is required to properly pre-process the data before sending it to Tableau. The rendering speed is terrific and there are only a few tricks needed to get these types of results completed like I described in building the data set.
The lack of dynamic zooming and panning, as well as a lack of real-time coordinates in the plot widow do hamper your ability know where you are spatially, but overall the experience is satisfactory. If Tableau had more of a dynamic workspace for x-y type plots, similar to what you get in Tecplot or AutoCad, doing this type of work would be very much more enjoyable. I guess I could add these features to my “Tableau Wish List“.
In an upcoming post, I’ll look at the capability that Tableau has to process results from a numerical model like this one.
Aftermath
After publication of this work, one of my favorite Tableau Zen Masters decided to look into how Tableau draws polygons. Using his typical well-documented approach to solving problems, Jonathan Drummey produced a Tableau public workbook to document his findings. You can find this workbook by clicking here to learn more about the techniques I used in this post. Many thank to Mr. JD for taking the time to think about this work.
That’s a very illuminating post, thanks for sharing it, Ken, and thanks to Jonathan for his input. I was a hydrogeologist in my past career so it’s very interesting to me to read about blending flow models with Tableau. I really enjoy your posts and would love to see more of your work utilizing Tableau in an engineering world.
Looking forward to your next post!
Hi George!
Wow. I never expected to see another hydrogeologist reading my blog! That is fantastic and it is so good to hear from you. Maybe we can talk a little about our pasts via email now that I have your address.
I have a dream of being able to use Tableau in the scientific world as much as I do in the business world but the functionality isn’t quite there yet. The interesting thing to me is that Tableau could relatively easily be changed to accomplish an number of things that it currently cannot do, which would explode its usage into the scientific field. I have outlined some of the needed changes in various posts but maybe I should dedicate a single post to this topic. My experience history allows me to very easily see the future of what I call “Scientific Tableau” but I’m not a decision maker. I would like to combine aspects of AutoCad, ArcGIS, Tecplot and Tableau into one product that would wipe out the competition. Like I said, it is just a dream at this point.
Thanks again for writing and I’ll show some more engineering applications in upcoming posts. Some of these are already underway.
Ken
Hi Ken – I will be very happy to share my experience with you. Please email me a quick note so I have your email address. Thanks!
George
Pingback: Reflections of the Past and a Vision of a #Tableau Future | 3danim8's Blog
Pingback: 3danim8's Blog - Test 2 of Tableau Vs Power BI: Visualizing Surface Water Flow