I am running an FDTD compact explicit scheme simulation to solve the wave equation for a 3D geometry. The results are voxels of pressure point values. The files are saved as .vti and are workable in Paraview. But I am wondering if there is a more direct way to visualise them in Python. Any comments are welcome! Best regards.
Sahand Athari Hello.
This is for python integrated development environment IDLE. PYTHONPATH is set to the following:
/Users/berk/work/paraview3-build/lib:/Users/berk/work/paraview3-build/lib/site-packages
Note that depending on your build configuration, your *.libs files may not be under "lib" but under one of its sub-folders, like "lib/Release" or "lib/Debug". In those cases add the correct folder where the *.libs reside:
/Users/berk/work/paraview3-build/lib/Release:/Users/berk/work/paraview3-build/lib/site-packages
You may also need to set your path variable for searching for shared libraries (i.e. PATH on Windows and LD_LIBRARY_PATH on Unix/Linux/Mac). The corresponding LD_LIBRARY_PATH would be:
/Users/berk/work/paraview3-build/lib (/Users/berk/work/paraview3-build/bin for versions before 3.98)
(Under WindowsXP for a debug build of paraview, set both PATH and PYTHONPATH environment variables to include ${BUILD}/lib/Debug and ${BUILD}/lib/site-packages to make it work.)
>>> from paraview.simple import *
Note: Importing the paraview module directly is deprecated, although still possible for backwards compatibility. This refers to the simple module alone.
For more info., have a look at (it is very in general, but I thought it is relevant to what you are seeking) this example, where ParaView will be used in the stand-alone mode. Connecting to a ParaView server running on a cluster is covered later: https://www.paraview.org/Wiki/ParaView/Python_Scripting
It will help if you explain what you mean by "more direct". ParaView, and VTK in general, is very Python friendly and uses it all ways. If you already have vti files, then you can use ParaView thru' Python.
Sahand Athari Hello.
This is for python integrated development environment IDLE. PYTHONPATH is set to the following:
/Users/berk/work/paraview3-build/lib:/Users/berk/work/paraview3-build/lib/site-packages
Note that depending on your build configuration, your *.libs files may not be under "lib" but under one of its sub-folders, like "lib/Release" or "lib/Debug". In those cases add the correct folder where the *.libs reside:
/Users/berk/work/paraview3-build/lib/Release:/Users/berk/work/paraview3-build/lib/site-packages
You may also need to set your path variable for searching for shared libraries (i.e. PATH on Windows and LD_LIBRARY_PATH on Unix/Linux/Mac). The corresponding LD_LIBRARY_PATH would be:
/Users/berk/work/paraview3-build/lib (/Users/berk/work/paraview3-build/bin for versions before 3.98)
(Under WindowsXP for a debug build of paraview, set both PATH and PYTHONPATH environment variables to include ${BUILD}/lib/Debug and ${BUILD}/lib/site-packages to make it work.)
>>> from paraview.simple import *
Note: Importing the paraview module directly is deprecated, although still possible for backwards compatibility. This refers to the simple module alone.
For more info., have a look at (it is very in general, but I thought it is relevant to what you are seeking) this example, where ParaView will be used in the stand-alone mode. Connecting to a ParaView server running on a cluster is covered later: https://www.paraview.org/Wiki/ParaView/Python_Scripting
- Badges
- Science topic
- Similar topics
- Computer Science and Engineering
- Computer Graphics and Animation
- 3D