Brian Benjamin Maranville
Brian Benjamin Maranville
The source of the errors is mysterious to me too. Might need help from the HDF group to unwind this.
When traversing a schema, it keeps track of a Set of "seen" items, but the "get" from the proxy handler returns a new Proxy object for every subschema, whether it...
@cgillin can you try this out and see if it works for you? I saw that you had a need for float16.
> @bmaranville I'm getting some warnings in the H5Wasm demo when I select a simple HDF5 file. > >  > > After the warnings, I get a `name not...
It seems to be calling file.close in the api.cleanUp method when the file is already closed... I suspect it is because of a change in how useEffect is handled in...
I can verify that the h5wasm loader works for a pre-built version of the demo, with react 18. So it does seem to be related to the change in useeffect...
Also you shouldn't close the file until you are done working with it. You would have to open and get a new file handle to e.g. navigate or read any...
Here is an example file that shows the issue: [live.sample.name6.zip](https://github.com/silx-kit/h5web/files/8845189/live.sample.name6.zip)
Sure, it allows us to plot our data. I don't love using the name "spectrum", since our scans are not over wavelengths but over angles, but that is a minor...
Yes, many of our NeXus files are incomplete or incorrectly constructed, and having the "axis" misidentified is worse than not having it identified at all.