[Paraview] Error when reading multiple spatially decomposed Exodus files
Cory Quammen
cory.quammen at kitware.com
Fri May 26 10:40:22 EDT 2017
Louis,
[adding list back in]
I'm afraid I am not an expert in the Exodus file format nor in how
ParaView reads it. However, if you have a set of files you can share
(with just me if necessary), I can take a quick look and see if
anything jumps out at me.
Thanks,
Cory
On Fri, May 26, 2017 at 10:31 AM, Steytler, Louis Louw
<steytle1 at illinois.edu> wrote:
> Cory,
>
> I think the problem with reading the multiple Exodus files is related to the information provided by the first file in the series of decomposed files.
>
> According to http://www.paraview.org/Wiki/ParaView/ParaView_Readers_and_Parallel_Data_Distribution,
>
> "The root node scans the directory for files in the set and reads metadata (blocks and variables defined on them) from a single file in the set. It then broadcasts this information to all processes. Each reads a different subset of files. "
>
> Something like this seems to be happening when reading in serial as well. It seems ParaView reads in this information and applies that when reading all the other pieces.
>
> Even though I have multiple Exodus blocks in my mesh, only one block appears in the ParaView Pipeline Browser. (My code only writes information relevant to a specific piece to that piece's data file.)
>
> Could you tell me what information should be provided in the first file in the series of files and is there any documentation I could look at to check that the code that I am using is writing the Exodus files in the correct format for ParaView to read it?
>
> Any advice would be much appreciated.
>
> Thanks very much,
>
> Louis Steytler
> Department of Mechanical Science and Engineering
> University of Illinois at Urbana-Champaign
> 1206 West Green Street
> Urbana, Il 61801
> steytle1 at illinois.edu
> ________________________________________
> From: Cory Quammen [cory.quammen at kitware.com]
> Sent: 25 May 2017 03:01 PM
> To: Steytler, Louis Louw
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Error when reading multiple spatially decomposed Exodus files
>
> Hi Louis,
>
> It looks like you are using ParaView 4.1, which is fairly old at this
> point. Could you try a more recent version such as 5.3 or 5.2 and see
> if the problem persists?
>
> Thanks, and best regards,
> Cory
>
> On Thu, May 25, 2017 at 3:20 PM, Steytler, Louis Louw
> <steytle1 at illinois.edu> wrote:
>> Hello,
>>
>> I am trying to read a set of spatially decomposed Exodus files as described
>> here:
>> http://www.paraview.org/Wiki/ParaView/ParaView_Readers_and_Parallel_Data_Distribution
>>
>> The ParaView client is being run on my laptop and the server on a remote
>> visualization cluster. I am connecting to the server via a client-server
>> connection.
>>
>> When I do so I get the error:
>>
>> ERROR: In
>> /projects/pvdev/common/pv-source/v4.1.0_test/VTK/Common/DataModel/vtkDataObjectTree.cxx,
>> line 377
>> vtkMultiBlockDataSet (0x7d96490): Structure does not match. You must use
>> CopyStructure before calling this method.
>>
>> multiple times. I running pvserver on one and many processes, each time
>> getting the same error.
>>
>> Any advice would be much appreciated.
>>
>> Thanks very much,
>>
>> Louis
>>
>> Louis Steytler
>> Department of Mechanical Science and Engineering
>> University of Illinois at Urbana-Champaign
>> 1206 West Green Street
>> Urbana, Il 61801
>> steytle1 at illinois.edu
>>
>> _______________________________________________
>> 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
>>
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
--
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
More information about the ParaView
mailing list