[CIG-SHORT] cannot open the .xmf with paraview

[Brad Aagaard]

Yuval,

The data writer being used in tpv102 writes HDF5 files with external 
datasets, that is, the values are written by PETSc to raw binary files 
in parallel. The paths to those raw binary files is written in the HDF5 
file in addition to the path to the HDF5 file being written in the Xdmf 
file. All of this means that ParaView will only find the data values if 
the Xdmf (.xmf) file is opened from the tpv201 directory, not the output 
or any other directory. The easiest way to do this is to start ParaView 
from the command line in this directory. Note that this works on Macs as 
well as linux.

Brad

On 09/03/2013 11:45 AM, Yuval Tal wrote:
> Hello Brad,
>
> Sorry to bother you again.
>
> I have a problem to watch the results of the benchmark tpv102 simulation. I have tried to load the hex8_200m-fault.xmf file. when I try to "apply" it, I receive the following massage:
>
> ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/Xdmf2/vtkXdmfReader.cxx, line 395
> vtkXdmfReader (0x11828d810): Failed to read data.
>
>
> ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754
> vtkPVCompositeDataPipeline (0x1182d99a0): Algorithm vtkXdmfReader(0x11828d810) returned failure for request: vtkInformation (0x118f489e0)
> Debug: Off
> Modified Time: 1422891
> Reference Count: 1
> Registered Events: (none)
> Request: REQUEST_DATA
> FORWARD_DIRECTION: 0
> ALGORITHM_AFTER_FORWARD: 1
> FROM_OUTPUT_PORT: 0
>
> I have no idea how to debug it.
>
> Thanks,
> Yuval
>