[bug #68251] Load-Save support for MAT-file v7.3 (HDF5-based format)
Rik <[email protected]> Wed, 22 Apr 2026 16:16:17 -0400 (EDT)
| Newsgroups | gmane.comp.gnu.octave.bugs |
|---|---|
| Message-ID | <[email protected]> |
Please use the bug tracker to post updates to a bug report. The mailing list is intended as a read-only notification stream. Info posted to this mailing list address won't appear in the tracker database where it is most useful.
Follow-up Comment #4, bug #68251 (group octave):
We should absolutely clean up Octave's implementation of HDF5 to use modern
API. There is even an ancient bug report about this from 2013! See bug
#39491.
Your fix for bug #68237 got me to look at the load/save implementation in
Octave. For one thing, I found that saving in some formats such as Octave's
very own *-text* format takes a really long time. See the thread I opened on
Discourse at
https://octave.discourse.group/t/performance-improvements-for-save-in-octaves-native-text-format/7504.
Native HDF5 in Octave is quick, and also can represent arrays with more than
2^31 elements which Octave's own binary format cannot.
One of the problems I encountered with saving long files is that it could take
up to 10 minutes and Ctrl+C was not working. See this new changeset
(https://hg.savannah.gnu.org/hgweb/octave/rev/1fab643922fb) where I added
*octave_quit()* calls in strategic places to make it possible to interrupt the
load/save operation.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68251>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaekskQAKCRCqLAuaBUf3 TkjKAQDPXrp7LIoV+Zxhoi3iEcVj4ZzwyQq3v8+GJ6rqG4oVMgEAvjntavXxbvkI iesXkHxAA2962Obt5ZanDntOKyVc4Qc= =oXhO -----END PGP SIGNATURE-----