File: fea.md

package info (click to toggle)
python-trame 3.12.0-2
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 101,620 kB
  • sloc: python: 13,515; sh: 183; javascript: 93; makefile: 7
file content (23 lines) | stat: -rw-r--r-- 1,375 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
# Finite Element Analysis

This example is a translation from a `dash-vtk` code described in that [repository](https://github.com/shkiefer/dash_vtk_unstructured) using trame.

In trame we are exposing 3 approaches:
- client view:
  This application simulate what dash-vtk is doing by defining the 3D scene in plain HTML structure.
- remote/local view:
  Those applications focus on the VTK/Python part by creating and configuring your vtkRenderWindow
  directly and letting the VtkRemoteView or VtkLocalView do their job of presenting it on the client
  side. In the case of the __VtkRemoteView__, the rendering is happening on the server side and images
  are sent to the client. For the __VtkLocalView__ use case, the geometry is sent instead and the client
  is doing the rendering using vtk.js under the cover.

The data files can be found [here in the original project](https://github.com/shkiefer/dash_vtk_unstructured/tree/main/data).

[![FEA Example](/assets/images/examples/FiniteElementAnalysis.jpg)](https://github.com/Kitware/trame/tree/master/examples/06_vtk/Applications/FiniteElementAnalysis)

::: code-group
<<< @/../../examples/06_vtk/Applications/FiniteElementAnalysis/app_client_view.py 
<<< @/../../examples/06_vtk/Applications/FiniteElementAnalysis/app_local_view.py 
<<< @/../../examples/06_vtk/Applications/FiniteElementAnalysis/app_remote_view.py
:::