The RFC for the virtual datasets indicates that you can set a path in which to search for the source files referenced in the virtual datasets, using the H5Pset_virtual_source_path function. It doesn't appear that this was implemented, as my header files don't resolve that symbol. Am I just missing something?
At the moment, I'm using just the base filename as the source file, and h5dump (1.10.0 patch 1) works fine if my working directory is the same as the VDS file (collocated with the source files), but fails to resolve the data if I dump it from a different directory.
What I would like to do is have the HDF library search in "." relative to the location of the VDS file.
The RFC for the virtual datasets indicates that you can set a path in which to search for the source files referenced in the virtual datasets, using the H5Pset_virtual_source_path function. It doesn’t appear that this was implemented, as my header files don’t resolve that symbol. Am I just missing something?
At the moment, I’m using just the base filename as the source file, and h5dump (1.10.0 patch 1) works fine if my working directory is the same as the VDS file (collocated with the source files), but fails to resolve the data if I dump it from a different directory.
What I would like to do is have the HDF library search in “.” relative to the location of the VDS file.
Thanks. A simple enough work-around in our application is to chdir into the directory containing the file when accessing the virtual dataset, and then chdir back out when done.
Jarom
···
From: Hdf-forum [mailto:hdf-forum-bounces@lists.hdfgroup.org] On Behalf Of Elena Pourmal
Sent: Thursday, July 14, 2016 9:12 PM
To: HDF Users Discussion List
Subject: Re: [Hdf-forum] H5Pset_virtual_source_path
Hi Jarom,
The function was not implemented. We will try to address the issue in the release later this year.
The RFC for the virtual datasets indicates that you can set a path in which to search for the source files referenced in the virtual datasets, using the H5Pset_virtual_source_path function. It doesn’t appear that this was implemented, as my header files don’t resolve that symbol. Am I just missing something?
At the moment, I’m using just the base filename as the source file, and h5dump (1.10.0 patch 1) works fine if my working directory is the same as the VDS file (collocated with the source files), but fails to resolve the data if I dump it from a different directory.
What I would like to do is have the HDF library search in “.” relative to the location of the VDS file.
