universeodon.com is part of the decentralized social network powered by Mastodon.
Be one with the #fediverse. Join millions of humans building, creating, and collaborating on Mastodon Social Network. Supports 1000 character posts.

Administered by:

Server stats:

3.3K
active users

Learn more

#hdf5

1 post1 participant0 posts today
mgorny-nyan (he) :autism:🙀🚂🐧<p><a href="https://social.treehouse.systems/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> is doing great. So basically:</p><p>1. Originally, upstream used autotools. The build system installed a h5cc wrapper which — besides being a compiler wrapper — had a few config-tool style options.<br>2. Then, upstream added <a href="https://social.treehouse.systems/tags/CMake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CMake</span></a> build system as an alternative. It installed a different h5cc wrapper that did not have the config-tool style options anymore.<br>3. Downstreams that tried CMake quickly discovered that the new wrapper broke a lot of packages, so they reverted to autotools and reported a bug.<br>4. Upstream closed the bug, handwaving it as "CMake h5cc changes have been noted in the Release.txt at the time of change - archived copy should exist in the history files."<br>5. Upstream announced the plans to remove autotools support.</p><p>So, to summarize the current situation:</p><p>1. Pretty much everyone (at least <a href="https://social.treehouse.systems/tags/Arch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Arch</span></a>, <a href="https://social.treehouse.systems/tags/Conda" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Conda</span></a>-forge, <a href="https://social.treehouse.systems/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Debian</span></a>, <a href="https://social.treehouse.systems/tags/Fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fedora</span></a>, <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Gentoo</span></a>) is building using autotools, because CMake builds cause too much breakage.<br>2. Downstreams originally judged this to be a HDF5 issue, so they didn't report bugs to affected packages. Not sure if they're even aware that HDF5 upstream rejected the report.<br>3. All packages remain "broken", and I'm guessing their authors may not even be aware of the problem, because, well, as I pointed out, everyone is still using autotools, and nobody reported the issues during initial CMake testing.<br>4. I'm not even sure if there is a good "fix" here. I honestly don't know the package, but it really sounds like the config-tool was removed with no replacement, so the only way forward might be for people to switch over to CMake (sigh) — which would of course break the packages almost everywhere, unless people also add fallbacks for compatibility with autotools builds.<br>5. The upstream's attitude suggests that HDF5 is pretty much a project unto itself, and doesn't care about its actual users.</p><p><a href="https://github.com/HDFGroup/hdf5/issues/1814" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/HDFGroup/hdf5/issue</span><span class="invisible">s/1814</span></a></p>
Howard Chu @ Symas<p>Three Ways of Storing and Accessing Lots of Images in <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a><br><a href="https://realpython.com/storing-images-in-python/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">realpython.com/storing-images-</span><span class="invisible">in-python/</span></a></p><p>Using plain files, <a href="https://mastodon.social/tags/LMDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LMDB</span></a>, and <a href="https://mastodon.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a>. It's too bad there's an explicit serialization step for the LMDB case. In C we'd just splat the memory in and out of the DB as-is, with no ser/deser overhead.</p><p>Also they use two separate tables for image and metadata in HDF5, but only one table in LMDB (with metadata concat'd to image). I don't see why they didn't just use two tables there as well.</p>
Roadskater, Ph.D.<p>I could have sworn <a href="https://mastodon.social/tags/HDF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF</span></a> was only up to version 5.something, but maybe I lost track.</p><p><a href="https://mastodon.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a></p>
ing.grid<p>New software descriptor published on ing.grid! "h5RDMtoolbox - A Python Toolbox for FAIR Data Management around HDF5" by Matthias Probst and Balazs Pritz <a href="https://www.inggrid.org/article/id/4028/" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="">inggrid.org/article/id/4028/</span><span class="invisible"></span></a> <a href="https://nfdi.social/tags/RDM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RDM</span></a> <a href="https://nfdi.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> <a href="https://nfdi.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>python</span></a> <a href="https://nfdi.social/tags/FAIR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FAIR</span></a> <a href="https://nfdi.social/tags/kit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kit</span></a></p>
DAPHNE 4 NFDI<p>NeXus ist ein in unseren ommunities weitverbreitetes <a href="https://nfdi.social/tags/Datenformat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Datenformat</span></a>. Es bietet einen Standard, welche Parameter gespeichert und wie sie im <a href="https://nfdi.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a>-Datei strukturiert werden sollen, um <a href="https://nfdi.social/tags/Metadaten" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Metadaten</span></a> zusammen mit den Daten in einer hochstrukturierten Weise zu integrieren.</p><p>Darauf aufbauend gibt es eine maschinenlesbare <a href="https://nfdi.social/tags/Ontologie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ontologie</span></a>; diese definiert eindeutige Bezeichner und schafft ein kontrolliertes Vokabular für die Namen aller experimentellen Parameter und gemessenen Variablen im Experiment.</p><p>2/3</p>
DAPHNE 4 NFDI<p>Gestern haben Rolf und Heike beim <a href="https://nfdi.social/tags/NFDI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NFDI</span></a>-Netzwerktreffen Berlin-Brandenburg unser Daphne-Konsortium vorgestellt. Speziell sind sie auf die Terminologien und Datenformate eingegangen, welche für <a href="https://nfdi.social/tags/Synchrotron" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Synchrotron</span></a>- und <a href="https://nfdi.social/tags/Neutronen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Neutronen</span></a>-Experimente genutzt werden.</p><p>1/3</p><p>Die Folien gibt's bei Zonodo:<br><a href="https://zenodo.org/records/12728050" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="">zenodo.org/records/12728050</span><span class="invisible"></span></a></p><p><a href="https://nfdi.social/tags/RDM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RDM</span></a> <a href="https://nfdi.social/tags/Ontologien" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ontologien</span></a> <a href="https://nfdi.social/tags/NeXus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NeXus</span></a> <a href="https://nfdi.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a></p>
Maltimore<p>STOP DOING HDF5</p><p>- Years of HDF5 yet no real-world use-case found<br>- Files were never meant to be hierarchical or "self explaining"<br>- "Hello I would like a file system within a file please" ...statements dreamt up by the utterly deranged<br>- Look at what the HDF5 group has been demanding our respect for all this time<br>- wanted to have an explanation for the stuff in a folder? We had a tool for that: it was called a Readme</p><p>They have played us for absolute fools</p><p><a href="https://social.tchncs.de/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a></p>
Howard Chu @ Symas<p><a href="https://mastodon.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> is still a popular file format in scientific computing, but <a href="https://mastodon.social/tags/LMDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LMDB</span></a> is always superior, especially in machine learning. <a href="https://www.reddit.com/r/MachineLearning/comments/1ad6j2i/d_how_to_make_my_training_faster/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">reddit.com/r/MachineLearning/c</span><span class="invisible">omments/1ad6j2i/d_how_to_make_my_training_faster/</span></a></p>
Markus Osterhoff<p>HELPMI:<br>Develop a user-driven <a href="https://academiccloud.social/tags/NeXus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NeXus</span></a> extension proposal for laser-plasma (<a href="https://academiccloud.social/tags/laser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>laser</span></a> <a href="https://academiccloud.social/tags/plasma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>plasma</span></a>) experiments, by <a href="https://academiccloud.social/tags/Helmholtz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Helmholtz</span></a> <a href="https://academiccloud.social/tags/Metadata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Metadata</span></a> Collaboration</p><p>Basically, having nice and standardised metadata (e.g. in <a href="https://academiccloud.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> files) for <a href="https://academiccloud.social/tags/pewpew" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pewpew</span></a> experiments, making data <a href="https://academiccloud.social/tags/FAIR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FAIR</span></a> for others – and also more easy to access for yourself ;)</p>
Markus Osterhoff<p>Now we're learning about h5wasm, especially viewing compressed <a href="https://academiccloud.social/tags/hdf5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hdf5</span></a> data files with web assembly <a href="https://academiccloud.social/tags/wasm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>wasm</span></a>.</p>
Markus Osterhoff<p>Maintenance of <a href="https://academiccloud.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> filters, plugins:</p><p>Who fixes problems?<br>What happens when, filter maintainers disappear?<br>When underyling libraries are no longer maintained?<br>API changes?</p><p>Who cares, who pays?</p>
Markus Osterhoff<p>This week, I'm at <span class="h-card"><a href="https://helmholtz.social/@DESY" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>DESY</span></a></span> for the <a href="https://academiccloud.social/tags/HDF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF</span></a> User Group <a href="https://academiccloud.social/tags/HUG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HUG</span></a> summit on plugins and data compression.</p><p>We will start with latest updates on plugins:<br>“HDF5 and plugins – overview and roadmap“, Dana Robinson.<br>Then, Elena Pourmal will hopefully have good news: “Expanding HDF5 capabilities to support multi-threading access and new types of storage“.</p><p>Currently, reading big datasets can be quite a burden due to some … challenges of <a href="https://academiccloud.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> with multi-threading.</p>
Markus Osterhoff<p>And after … a couple of days, here the <a href="https://academiccloud.social/tags/bugfix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bugfix</span></a> for my <a href="https://academiccloud.social/tags/memoryLeak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>memoryLeak</span></a><br>It turns out that using <a href="https://academiccloud.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> needs some cleanup routines – that's totally okay, but I have plenty of <a href="https://academiccloud.social/tags/Terabytes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terabytes</span></a> that worked without 🤔</p>
Markus Osterhoff<p>The <a href="https://academiccloud.social/tags/HDF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF</span></a> User Group will hold their annual European meeting on 19-21 September at <a href="https://academiccloud.social/tags/DESY" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DESY</span></a>, Hamburg, Germany.</p><p>The special topic of this meeting will be <a href="https://academiccloud.social/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a> plugins and <a href="https://academiccloud.social/tags/data" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>data</span></a> <a href="https://academiccloud.social/tags/compression" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>compression</span></a>, and the meeting is hosted in collaboration with the LEAPS-INNOV EU project. The HDF Group will give an update on the latest developments within HDF5 and present the roadmap for the future.</p><p><a href="https://indico.desy.de/e/ehug2023" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="">indico.desy.de/e/ehug2023</span><span class="invisible"></span></a></p>
Christopher J Burke<p><span class="h-card" translate="no"><a href="https://mastodon.online/@ExoHugh" class="u-url mention">@<span>ExoHugh</span></a></span> I really hate getting an undocumented or poorly documented <a href="https://universeodon.com/tags/HDF5" class="mention hashtag" rel="tag">#<span>HDF5</span></a> file. It is very challenging to parse it&#39;s contents. Having the human readable header metadata at beginning of fits/asdf files is a godsend for simply cat/less a file to figure out what&#39;s in it.</p>
Hugh Osborn<p>I'm at ESTEC (ESA's European Space Research and Technology Centre) in the Netherlands this week for my first <a href="https://mastodon.online/tags/PLATO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PLATO</span></a> science working team meeting as community scientist. One interesting discussion has been on astronomical file formats (honestly)... Future NASA missions look like they might move from <a href="https://mastodon.online/tags/fits" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fits</span></a> to <a href="https://mastodon.online/tags/ASDF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ASDF</span></a>, while other astronomical surveys have started using <a href="https://mastodon.online/tags/HDF5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HDF5</span></a>. But it's tough to try to predict exactly where the community will be in 5-10 years time. Input welcome!</p>