[Paraview] EnSightReader: Change input file

[Utkarsh Ayachit]

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

On Tue, Nov 11, 2014 at 8:39 AM, Ian Krukow <i.krukow at tu-braunschweig.de> wrote:
> 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