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
Copy file name to clipboardExpand all lines: clinic/index.org
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -185,7 +185,7 @@ understand the context.
185
185
: world
186
186
: hello
187
187
: finished at 08:25:33
188
-
- Noticable speedup but not a panacea
188
+
- Noticeable speedup but not a panacea
189
189
#+begin_quote
190
190
Eventually I hope to have a version of =h5pyd= that supports =async= (or maybe
191
191
an entirely new package), that would make it a little easier to use.
@@ -250,7 +250,7 @@ I have an application that reads groups as units and all the datasets
250
250
use the contiguous data layout. I believe this option, if available,
251
251
can yield a good read performance.
252
252
#+end_quote
253
-
- Intersting suggestions
253
+
- Interesting suggestions
254
254
- Elena suggested to first create all datasets with =H5D_ALLOC_TIME_LATE=
255
255
- Mark suggested to =H5Pget_meta_block_size= to set aside sufficient
256
256
"group space" (Maybe also =H5Pset_est_link_info=?)
@@ -674,7 +674,7 @@ int main()
674
674
- A :: Currently, the code will skip entries >64K, because the underlying
675
675
=H5Dcreate= will fail. (The logic and code can be much improved.) It's better
676
676
to first run =archive_checker_64k= and see if there are any size warnings.
677
-
The =h5compactor= and =h5shredder= were sucessfully run on TAR archives with
677
+
The =h5compactor= and =h5shredder= were successfully run on TAR archives with
678
678
tens of millions of small images (<64K).
679
679
** Last week's highlights
680
680
*** Announcements
@@ -1126,7 +1126,7 @@ However, I cannot get this to work with h5py.
1126
1126
#+end_quote
1127
1127
- [[https://meetingorganizer.copernicus.org/EGU22/EGU22-11201.html][DIARITSup: a framework to supervise live measurements, Digital Twins modelscomputations and predictions for structures monitoring.]]
1128
1128
#+begin_quote
1129
-
DIARITSup is a chain of various softwares following the concept of ”system of
1129
+
DIARITSup is a chain of various software following the concept of ”system of
1130
1130
systems”. It interconnects hardware and software layers dedicated to in-situ
1131
1131
monitoring of structures or critical components. It embeds data assimilation
1132
1132
capabilities combined with specific Physical or Statistical models like
@@ -1227,7 +1227,7 @@ HDFS?
1227
1227
1228
1228
** Tips, tricks, & insights
1229
1229
*** SWMR (old) and compression "issues" - take 2
1230
-
- Free-space managment is disabled in the original SWMR implementation
1230
+
- Free-space management is disabled in the original SWMR implementation
1231
1231
- Can lead to file bloat when compression is enabled & overly aggressive
1232
1232
flushing
1233
1233
- **Question:** How does the new SWMR VFD implementation behave?
- "Partial I/O gets in the way" - sorting fields by name or offset
3792
3792
- Happens on each write call => overhead
3793
3793
- Can this be avoided? User might provide a patch...
3794
-
**** [[https://forum.hdfgroup.org/t/read-write-specific-coordiantes-in-multi-dimensional-dataset/9137][Read/write specific coordiantes in multi-dimensional dataset?]]
3794
+
**** [[https://forum.hdfgroup.org/t/read-write-specific-coordinates-in-multi-dimensional-dataset/9137][Read/write specific coordinates in multi-dimensional dataset?]]
3795
3795
- Thomas is looking for use cases from =h5py= users
Copy file name to clipboardExpand all lines: documentation/hdf5-docs/Migrating+from+HDF5+1.12+to+HDF5+1.14.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,4 +35,4 @@ The way optional operations are handled in the virtual object layer (VOL) change
35
35
The virtual file layer has changed in HDF5 1.14.0. Existing virtual file drivers (VFDs) will have to be updated to work with this version of the library.
36
36
37
37
## Virtual Object Layer (VOL) Changes
38
-
The virtual object layer has changed significantly in HDF5 1.14.0 and the 1.12 VOL API is now considered deprecated and unsupported. Existing virtual object layer connectors shoul be updated to work with this version of the library.
38
+
The virtual object layer has changed significantly in HDF5 1.14.0 and the 1.12 VOL API is now considered deprecated and unsupported. Existing virtual object layer connectors should be updated to work with this version of the library.
Copy file name to clipboardExpand all lines: documentation/hdf5-docs/release_specifics/Migrating_from_HDF5_1.12_to_HDF5_1.14.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,4 +35,4 @@ The way optional operations are handled in the virtual object layer (VOL) change
35
35
The virtual file layer has changed in HDF5 1.14.0. Existing virtual file drivers (VFDs) will have to be updated to work with this version of the library.
36
36
37
37
## Virtual Object Layer (VOL) Changes
38
-
The virtual object layer has changed significantly in HDF5 1.14.0 and the 1.12 VOL API is now considered deprecated and unsupported. Existing virtual object layer connectors shoul be updated to work with this version of the library.
38
+
The virtual object layer has changed significantly in HDF5 1.14.0 and the 1.12 VOL API is now considered deprecated and unsupported. Existing virtual object layer connectors should be updated to work with this version of the library.
*[16 bit floating point and Complex number datatypes](https://github.com/HDFGroup/hdf5doc/blob/master/RFCs/HDF5_Library/Float16/RFC__Adding_support_for_16_bit_floating_point_and_Complex_number_datatypes_to_HDF5.pdf)
0 commit comments