You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test_add_get_mesh
test_mesh_rename
test_iter_mesh
test_delete_mesh
So I assume that this is happening because the python get_xxx() functions of h5_cuds.py are returning the container by copy. This does not cause problems if the original objects is "normal" object, since the group does not exist, but when python group = self._root.mesh._f_get_child(name) is not empty it duplicates the groups.
I have been able to duplicate this as well with the h5_lattice class, and it looks that h5_particles is going to behave the same way
reported by @roigcarlo
In general, each time that a container is generated here ( for the mesh case for example ):
https://github.com/simphony/simphony-common/blob/master/simphony/io/h5_cuds.py#L211
Specifically, this error is being triggered by
test_add_get_mesh
test_mesh_rename
test_iter_mesh
test_delete_mesh
So I assume that this is happening because the python get_xxx() functions of h5_cuds.py are returning the container by copy. This does not cause problems if the original objects is "normal" object, since the group does not exist, but when python group = self._root.mesh._f_get_child(name) is not empty it duplicates the groups.
I have been able to duplicate this as well with the h5_lattice class, and it looks that h5_particles is going to behave the same way