Hi Samuel,
ok - interresting idea. I will check out what finally performs better. However
- as my tests with the multible block format in vtk (using one binary file for
each cell) show, that the handling of more then about 10k files is really a
mess. For my final case i will have around 100M cells - means theoretically
100M files - and this can be a real problem for the filesystem and for paraview
...
Best regards,
Stefan
________________________________
Von: ParaView [[email protected]]" im Auftrag von "Samuel Key
[[email protected]]
Gesendet: Donnerstag, 1. September 2016 16:59
An: [email protected]
Betreff: Re: [Paraview] Data handling in ParaView
Stefan,
The solution I use for this problem is the PART-construct that is provided by
the EnSight gold binary format. My 'PARTS' are defined by material ID's. Each
Point datum-item has its own file with all time-steps. Each Cell datum-item has
its own file with all time-steps. I have attached a typical EnSight case-file.
(The PART-construct is contained in the individual files.)
ParaView reads this format. EnSight reads this format. If you are interested in
pursuing this simulation results format, I can provide the format documentation
and an example Fortran95 writer.
Samuel W Key
FMA Development, LLC
1005 39th Ave NE
Great Falls, Montana 59404
On 9/1/2016 4:00 AM, Stefan Melber wrote:
Hi,
i have (maybe) a simple problem: For the visualization of the so called
dual-cells of an unstructured grid i use currently the block-structured
vtu-format. The data thereby consists of many complex cells which are itself
consists of a number of triangles - see the picture d1 attached. Therefore i
have to write out EVERY cell in another vtu-file and group them with am
vtm-file together. This way works well with a small number of cells (~1000 - as
for the picture) however the aim is to go up to 100e6 cells. Depending on the
numbers i got from 1000 cells this process will take ~70 days!
The bottleneck is clearly the huge number of files i have to write (and read in
ParaView). So are there ideas to have another representation in only one file
for such kind of data?
I did some experiments writing all cells in one vtk(vtu)-file and give them
scalar values depending on the cell number. But then, the n-th cell (its last
point) is connected to the n+1 (its first point) and so on. Looks ugly if the
n-th cell is not a direct neighbor to the n+1 cell - and that can be the case
in my data. And - cutting then the resulting stuff in ParaView i did not get
the cutting pictures (like d4) i like to have ...
Best regards and hoping for some nice ideas,
Stefan
_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
