See the full list here.Įxodus is used in DOE codes that run on supercomputers. Voigt-notation of tensors) at nodes or cell-centers.Įxodus supports 1D (bars & beams), 2D (quads, tris), and 3D (hex, wedge, pyramid, tet) elements. Natively and rigorously supported in ParaViewĮxodus is FEM-centric, can store scalars, vectors, or matrices (i.e. Also, see my discussion at end of this post regarding the multitude of SEACAS conversion utilities, APIs, etc. Easy to understand for a part-time, self-taught programmer like myselfĮxodus is essentially a schema built upon either NetCDF or HDF5 (your choice).I don’t believe Exodus supports face-values, but it does support elements and nodes (Exodus is FEM-centric). The only question I have is whether in your vocabulary a “cell” is an element or the face of an element. The Exodus file format is part of the open-source “Sandia Engineering Analysis Code Access System” (SEACAS) and is natively (and rigorously) supported by ParaView. If I failed to provide crucial bits of information, or should clarify some points, please let me know.Īdded sample image of what meshes typically look like: Really looking forward to comments and suggestions. Sooner or later, we will have cases with more than 1 billion cells. Speaking of cell count: I am currently having trouble with ~400 million cells.But they translate and rotate between time steps. There is no deformation, the cubes retain their shape. We haven’t implemented moving meshes yet, but will start with it quite soon. Part of the mesh must be able to move.From what I understood, VTK does require writing the geometry for each time step in transient cases, even if it does not change. This is one constraint that kept me from looking further into VTK. The geometry is mostly stationary, while the values vary between time steps.The solvers writing the result files are MPI-parallel with domain decomposition.So if there is a simple-to-use element type for this application, I would be over the moon. The geometry is usually sparsely filled, and there are different cell sizes (I call it “levels”) in each mesh, with a 2:1 cell size ratio between different levels. However, the mesh itself is not Cartesian in the strictest sense of the word. mesh elements/cells are exclusively Cartesian cubes, or axis-aligned cubes if that makes it any clearer.Results are usually defined at cell centers, but an option for vertex-based values seems to come in handy on occasion. at least scalar and 3D vector quantities, symmetric tensors would be nice to have.easy to understand for a part-time, self-taught programmer like myself.Here is what I need from the file format: And unless I messed something up with my file exports, I might have surpassed an element count limit, at least with file import in ParaView. Using it with an MPI parallel solver is not exactly straightforward. But I feel like I am beginning to push its limits. And to be honest, I stuck with it because I actually understood the documentation. Part of the reason why I used it is because that’s what the was used in the group back when I joined. So far, I have been using ensight gold file format to get the data from my fluid simulations into ParaView. Could someone recommend a file format for transient result files from a CFD solver to read and analyze in ParaView?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |