Like many of you, I’m looking forward to the upcoming HDF5 Users Group event at ITER at the end of the month. After two days of exciting presentations, we are planning CodeCamp and Hands-on style sessions. Perhaps we can combine an idea that’s been in the air for some time with such a concentration of brilliant community minds and devote one session to exploring the idea of a Visual Studio Code extension for HDF5. If that idea has occurred or appeals to you, or even if you think this is a terrible idea, we would like to hear from you on this thread! Show us your (anti-)use cases, related efforts, and attempts! Share your concerns and reservations! Anything that helps us to get a headstart on this on June 2 will be welcome. And join us on the day, if you can! The registration for virtual attendance is still open.
Interesting idea! Do you have in mind a debugger extension that would let you show e.g. file/dataset properties on hover of file/dataset variable? BTW is it possible to tell the underlying type form just a hid_t?
Regarding visualizing HDF5 variables from the debugger, which does not sound to be the purpose of the proposed extension, it looks like VSCode support the Natvis Framework, shared with Visual Studio.
Most of you probably know H5Web, the web-based viewer for HDF5 files that we presented at several HUG instances.
We are pleased to announce that we recently released a VSCode extension (based on h5wasm) to be able to explore HDF5 files in VSCode with H5Web: GitHub - silx-kit/vscode-h5web: VSCode extension to explore and visualize HDF5 files
You are all welcome to install this extension and give us your feedback
@loic.huder Here’s a query: do you think this could possibly be extended to support netCDF4 files? I mean, those are HDF5 files (in a sense? Not sure of the complete relationship), and I can h5dump a netCDF4 file…so maybe?
I only ask because where I am is a netCDF4 shop, and having this capability might be quite nice to quick-look our files.
Note: I did try a simple "rename file to test.h5" but the extension threw Expected valid HDF5 file.
"Rename file to test.h5" should have worked, in fact it should have also worked without the rename, unless the extension is fussy. @matthew.thompson, assuming you are on a linux-type system, what does “file test.h5” or “file test.nc” say?
❯ diff -s test.h5 test.nc4
Files test.h5 and test.nc4 are identical
❯ file test.nc4
test.nc4: Hierarchical Data Format (version 5) data
❯ file test.h5
test.h5: Hierarchical Data Format (version 5) data
So, as far as file is concerned, they are the same type of file.
@matthew.thompson I tried the extension with a NetCDF file and it worked fine.
Please open an issue on the repo: https://github.com/silx-kit/vscode-h5web (ideally by attaching a sample file). This way, we will be able to track more easily the necessary steps to solve this.
@loic.huder Well this is…interesting. For some reason now, I can open the renamed test.h5 file in VS Code. I’m…not sure what changed. I mean, I did “Restart to update” it because Microsoft asked me to.
So, uh, thanks for your cool work!
Still, I think I might make a feature request for your extension so it can open .nc4 files like it can .h5 files.
(And of course, my dream would be if it saw the file had lats and lons to put the data on a project of the earth but that might be asking too much )
busy working on a project, Apache Flink/Apache Paimon and pushing data to a HDFS cluster, would be great to be able to browse the directory structure/files inside VSCode.
And with VSCode having Parquet/ORC/Avro/JSON capability, click on file and see contents or copy file around.
I apologise for necro’ing an old thread, but I had to say THANK YOU.
I work in MRI image reconstruction and generate multi-dimensional complex valued images. This viewer already does all the slicing and colormapping I want. This is frankly amazing. It’s rare these days to find something that works so well out of the box and makes me wish I found it sooner.
)