Thank you for your suggestions! Still: No matter which one I choose, I
would have to edit every new set of files, before I can load it into
ParaView.
I have now set up a (very small) pvypthon module vtuseries.py, which
looks like this:
import os,glob
import paraview.simple as pv
def
Well, if you don't want to rename the data files then you could use a PVD
wrapper file:
http://www.paraview.org/Wiki/ParaView/Data_formats
Never created one myself, but you could write out one from paraview and modify
it.
But maybe somebody else has a better idea altogether...
-Armin
On
Have you tried to name the files like this:
fileName..vtu
fileName.0001.vtu
fileName.0002.vtu
...
ParaView should recognize them as a time series.
That typically worked for me (cannot test it though at the moment).
-Armin
On Fri Mar 6 12:36:01 2015 GMT+0200, Ian Krukow wrote:
Hi all,
Yes, that would work. I could write me a script for renaming the files.
But I would rather avoid that, as I get the result files from a project
partner with the simulation time in the filename. So, they are named
something like
file_t=0.0012.vtu
file_t=0.0024.vtu
...
As soon as t passes 1,
Ian,
If the *.vtu files are using the XML-based format, the you can use a
*.vtd mother file (or meta file) that references the *.vtu files. An
example of a *.pvd file is attached, however, the 'name=...' item is
ignored (not used) by PV's Extract Block filter.
Sam
On 3/6/2015 6:13 AM, Ian
On Fri, Mar 6, 2015 at 3:06 PM, dkxl...@gmail.com wrote:
Well, if you don't want to rename the data files then you could use a PVD
wrapper file:
http://www.paraview.org/Wiki/ParaView/Data_formats
Never created one myself, but you could write out one from paraview and
modify it.
But maybe
Hi all,
I want to load a series of VTU files, which are all stored in one
directory, but not numbered in a way that ParaView recognises them as
one series. In a python script, I can do it like this:
import glob
import paraview.simple as pv
pattern = 'directory/*.vtu'
files =
