XDMF Bug (Hard-coded drive letter C:)
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
It appears ParaView uses the wrong drive letter when writing or reading HDF5 files via XDMF.
Steps to reproduce: Start ParaView (I am using Version 4.2.0 64 Bit for Windows 7 64-bit) From the menu, select Sources --> Plane Set X Resolution 10 Set Y Resolution 10 Apply File --> Save Data File format Xdmf data file File name D:\SAMPLE.XMF
Open the XMF file in a text editor. Bug 1: The file refers to D:/SAMPLE.h5 . However, there is no such file. The HDF5 file is C:\SAMPLE.H5.
Bug 2: Reset the ParaView session and open the file D:\SAMPLE.XMF. Apply. The data loads properly, although the XMF file refers to D:/SAMPLE.h5, which does not exist.
Bug 2.1: Reset the ParaView session. Move the file SAMPLE.H5 to D:\ (The directory referenced in D:\SAMPLE.XMF) In Paraview, select File --> Open SAMPLE.XMF. Apply.
The program displays the Output Messages window with the following error message: ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Xdmf2\vtkXdmfReader.cxx, line 409 vtkXdmfReader (000000000EA5E7E0): Failed to read data.
ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 783 vtkPVCompositeDataPipeline (000000000DBCCA70): Algorithm vtkFileSeriesReader(000000000DBCC5C0) returned failure for request: vtkInformation (000000000C4FE530) Debug: Off Modified Time: 673302 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 FROM_OUTPUT_PORT: 0