On Thu, Dec 15, 2011 at 11:11 AM, Darren Dale <[email protected]> wrote: > Hi Quincey, > > On Wed, Dec 14, 2011 at 3:56 PM, Quincey Koziol <[email protected]> wrote: >> On Dec 14, 2011, at 9:46 AM, Darren Dale wrote: >>> I probably should have been more explicit: the >>> example illustrates that the problem is isolated to Datasets, Groups >>> are not effected. >> >> Whoops, sorry, yes, you are right. >> >>> H5py does not do any explicit name tracking. It delegates that task >>> completely to hdf5: for both Datasets and Groups, h5py simply calls >>> H5Iget_name. It seems to me that open dataset ids are not getting >>> their information updated, but open group ids are. Now that I think >>> about it, aren't there other issues with copying open datasets in >>> <hdf5-1.8.9? Perhaps the issues extend to moving open datasets as >>> well. >> >> That's pretty weird (that it would only affect datasets), since the >> H5Iget_name code doesn't depend on the object type. Can you >> replicate this with a short C program? > > Yes. See the attached modified version of one of the hdf5 examples. > After I move group1 from "old_loc" to "new_loc", the names of the > nodes contained in that group werereported by hdf5-1.8.8 to be: > > /new_loc/group > /old_loc/dataset
By the way, I see that H5Gmove2 has been deprecated in favor of H5Lmove. I see the same problem if I use H5Lmove. Darren _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
