[Paraview] WG: Data handling in ParaView

2016-09-01 Thread Stefan.Melber
Von: Melber-Wilkending, Stefan Gesendet: Donnerstag, 1. September 2016 16:52 An: Moreland, Kenneth Betreff: AW: [Paraview] Data handling in ParaView Hi Kenneth, after some search i found a bug in the code: one variable which holds the offset from cell

Re: [Paraview] Data handling in ParaView

2016-09-01 Thread Stefan.Melber
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

Re: [Paraview] Data handling in ParaView

2016-09-01 Thread Samuel Key
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

Re: [Paraview] pv_web_visualizer.py segmentation fault when loading a pvsm file

2016-09-01 Thread Sebastien Jourdain
Hi Pepe, I am not aware of the issue do you mind sharing your state file with me so I can see what you were doing in your state file? Did you generate your state file from the Visualizer or ParaView? Thanks, Seb On Wed, Aug 31, 2016 at 4:49 AM, Jose Luis Cercós wrote:

Re: [Paraview] Data handling in ParaView

2016-09-01 Thread Moreland, Kenneth
Stefan, The idea of identifying each "cell" by a scalar value should work just fine and be scalable. However, I do not understand what the issue is that the n-th cell's last point is connected to the n+1-th cell's first point. If there is no connection. I honestly do not see anything wrong