EnSightReader: Change input file
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Subject: [Paraview] EnSightReader: Change input file
From: Ian Krukow i.krukow@tu-braunschweig.de Date: Tue, Nov 11, 2014 at 8:39 AM To: ParaView paraview@paraview.org
Hi all,
I want to apply the same pipeline to a series of Ensight data files in order to save extractions in a different format. For the first file, this works fine. For the second file, I thought I could change the input file by changing the CaseFileName attribute:
reader.CaseFileName = nextfile
But when I run
reader.UpdatePipeline()
I get a segmentation fault. This depends neither on the file, nor on the pipeline following.
I tried a workaround by building up a new pipeline for each file. It works, and as I have only two files by now, it is ok to do that, but for more files, memory usage would explode. Therefore, my question is: Is it possible only to change the input file of the EnSightReader, while keeping the pipeline?
Kind regards Ian
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
Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
From: Utkarsh Ayachit utkarsh.ayachit@kitware.com Date: Fri, Nov 14, 2014 at 10:39 PM To: Ian Krukow i.krukow@tu-braunschweig.de Cc: ParaView paraview@paraview.org
Ability to change filenames depends on specific reader implementations. I am not entire familiar with the internal implementation, but if you have a couple of sample datasets/script to reproduce the segfault, I can check if its a minor fix to the reader to enable this or if it just can't support it.
Either case, you should be able to call Delete(reader) to delete old reader once you're done with it to avoid memory bloat.
Utkarsh
From: Ian Krukow i.krukow@tu-braunschweig.de Date: Tue, Nov 18, 2014 at 5:20 AM To: Utkarsh Ayachit utkarsh.ayachit@kitware.com
Ok, the problem obviously does depend on the input files to a certain degree. I use TAU as a flow solver (from the DLR, Germany), and it gives me two solution files, one for the fluid solution, one for the surface data. The problem with the EnSightReader occurs, when I try to switch from one category to the other (no matter, which direction). However, there is no problem loading another file of the same category, even with another geometry.
I attach two solution file sets, fluid and surface, with a short pvpython script to reproduce the error (sorry, that they are not smaller, but I do not create any grids of my own). The behaviour is the same with ParaView versions 3.14.1 and 4.2.0.
Kind regards Ian