diff --git a/.github/workflows/cmake-par-source.yml b/.github/workflows/cmake-par-source.yml
index 8b29882f035..04e2cb1764f 100644
--- a/.github/workflows/cmake-par-source.yml
+++ b/.github/workflows/cmake-par-source.yml
@@ -140,7 +140,7 @@ jobs:
- name: Run ctest script (OpenMPI)
run: |
cd "${{ runner.workspace }}/hdf5"
- ctest -S HDF5config.cmake,CTEST_SITE_EXT=GH-${{ github.event.repository.full_name }}-OpenMPI-s,LOCAL_SUBMIT=ON,NINJA=TRUE,BUILD_GENERATOR=Unix,CTEST_SOURCE_NAME=${{ steps.set-file-base.outputs.SOURCE_BASE }} -C ${{ inputs.build_mode }} -VV -O hdf5.log
+ ctest -S HDF5config.cmake,CTEST_SITE_EXT=GH-${{ github.event.repository.full_name }}-OpenMPI-source,LOCAL_SUBMIT=ON,NINJA=TRUE,BUILD_GENERATOR=Unix,CTEST_SOURCE_NAME=${{ steps.set-file-base.outputs.SOURCE_BASE }} -C ${{ inputs.build_mode }} -VV -O hdf5.log
shell: bash
continue-on-error: true
@@ -255,7 +255,7 @@ jobs:
- name: Run ctest script (MPICH)
run: |
cd "${{ runner.workspace }}/hdf5"
- ctest -S HDF5config.cmake,CTEST_SITE_EXT=GH-${{ github.event.repository.full_name }}-MPICH-s,LOCAL_SUBMIT=ON,NINJA=TRUE,BUILD_GENERATOR=Unix,CTEST_SOURCE_NAME=${{ steps.set-file-base.outputs.SOURCE_BASE }} -C ${{ inputs.build_mode }} -VV -O hdf5.log
+ ctest -S HDF5config.cmake,CTEST_SITE_EXT=GH-${{ github.event.repository.full_name }}-MPICH-source,LOCAL_SUBMIT=ON,NINJA=TRUE,BUILD_GENERATOR=Unix,CTEST_SOURCE_NAME=${{ steps.set-file-base.outputs.SOURCE_BASE }} -C ${{ inputs.build_mode }} -VV -O hdf5.log
shell: bash
continue-on-error: true
diff --git a/HDF5Examples/C/H5FLT/tfiles/h5ex_d_zfp.tst b/HDF5Examples/C/H5FLT/tfiles/h5ex_d_zfp.tst
index 2bec93cce2f..8b95b6e205b 100644
--- a/HDF5Examples/C/H5FLT/tfiles/h5ex_d_zfp.tst
+++ b/HDF5Examples/C/H5FLT/tfiles/h5ex_d_zfp.tst
@@ -4,7 +4,7 @@ zfp filter is available for encoding and decoding.
....Close the file and reopen for reading ........
Filter info is available from the dataset creation property
Filter identifier is 32013
- Number of parameters is 6 with the value 268456209
+ Number of parameters is 6 with the value 269504785
To find more about the filter check H5Z-ZFP-1.1.1 (ZFP-1.0.1) github.com/LLNL/H5Z-ZFP
....Reading zfp compressed data ................
Maximum value in DS1 is 1890.0000
diff --git a/doxygen/aliases b/doxygen/aliases
index fffec1cc2aa..cbc6e81f6cf 100644
--- a/doxygen/aliases
+++ b/doxygen/aliases
@@ -7,10 +7,12 @@ ALIASES += THG="The HDF Group"
ALIASES += HDFURL="support.hdfgroup.org"
# URL for archived files
ALIASES += ARCURL="\HDFURL/archive/support/HDF5/doc"
+# URL for release files
+ALIASES += RELURL="\HDFURL/releases/hdf5"
# URL for documentation
-ALIASES += DOCURL="\HDFURL/releases/hdf5/documentation"
+ALIASES += DOCURL="\RELURL/documentation"
# URL for downloads
-ALIASES += DWNURL="\HDFURL/releases/hdf5/downloads"
+ALIASES += DWNURL="\RELURL/downloads/latest"
# URL for RFCs
ALIASES += RFCURL="\DOCURL/rfc"
ALIASES += AEXURL="\HDFURL/archive/support/ftp/HDF5/examples"
diff --git a/doxygen/dox/ExamplesAPI.dox b/doxygen/dox/ExamplesAPI.dox
index f3903cec1d2..cf44405db11 100644
--- a/doxygen/dox/ExamplesAPI.dox
+++ b/doxygen/dox/ExamplesAPI.dox
@@ -150,8 +150,8 @@ Languages are C, Fortran, Java (JHI5), Java Object Package, Python (High Level),
JavaObj
MATLAB PyHigh PyLow
-
h5ex_d_rdwrc.h5 |
-h5ex_d_rdwrc.tst |
+h5ex_d_rdwr.h5 |
+h5ex_d_rdwr.tst |
h5ex_d_rdwr.ddl |
@@ -483,7 +483,7 @@ FORTRAN
h5ex_t_convert.h5 |
h5ex_t_convert.tst |
-h5ex_t_convert.ddl |
+h5ex_t_convert.ddl not applicable |
Read / Write Complex Compound (Attribute) |
diff --git a/doxygen/dox/IntroHDF5.dox b/doxygen/dox/IntroHDF5.dox
index d008ddcfc86..e83f8b22280 100644
--- a/doxygen/dox/IntroHDF5.dox
+++ b/doxygen/dox/IntroHDF5.dox
@@ -625,7 +625,7 @@ For information on compiling in C, C++ and Fortran, see: \ref LBCompiling
IDL, MATLAB, and NCL Examples for HDF-EOS
Examples of how to access and visualize NASA HDF-EOS files using IDL, MATLAB, and NCL.
-Miscellaneous Examples
+Miscellaneous Examples
These (very old) examples resulted from working with users, and are not fully tested. Most of them are in C, with a few in Fortran and Java.
Using Special Values
diff --git a/doxygen/dox/LearnBasics.dox b/doxygen/dox/LearnBasics.dox
index 4db515c1a57..33426cf1311 100644
--- a/doxygen/dox/LearnBasics.dox
+++ b/doxygen/dox/LearnBasics.dox
@@ -75,7 +75,7 @@ These examples (C, C++, Fortran, Java, Python) are provided in the HDF5 source c
Read and write to a dataset
|
-C Fortran C++ Java Python
+ | C Fortran C++ Java Python
|
|
@@ -83,7 +83,7 @@ These examples (C, C++, Fortran, Java, Python) are provided in the HDF5 source c
Create an attribute
|
-C Fortran C++ Java Python
+ | C Fortran C++ Java Python
|
|
@@ -99,7 +99,7 @@ These examples (C, C++, Fortran, Java, Python) are provided in the HDF5 source c
Create groups in a file using absolute and relative paths
|
-C Fortran C++ Java Python
+ | C Fortran C++ Java Python
|
|
diff --git a/doxygen/dox/LearnBasics3.dox b/doxygen/dox/LearnBasics3.dox
index 6e569aa41bb..c93c23971c0 100644
--- a/doxygen/dox/LearnBasics3.dox
+++ b/doxygen/dox/LearnBasics3.dox
@@ -968,7 +968,7 @@ or on WINDOWS you may need to add the path to the bin folder to PATH.
\section secLBCompilingCMake Compiling an Application with CMake
\subsection subsecLBCompilingCMakeScripts CMake Scripts for Building Applications
-See Using CMake to Build Applications to build applications with different languages and options.
+See Using CMake to Build Applications to build applications with different languages and options.
For a more complete script (and to help resolve issues) see the script provided with the HDF5 Examples project.
@@ -976,7 +976,7 @@ For a more complete script (and to help resolve issues) see the script provided
The installed HDF5 can be verified by compiling the HDF5 Examples project, included with the CMake built HDF5 binaries
in the share folder or you can go to the HDF5 Examples in the HDF5 github repository.
-Go into the share directory and follow the instructions in Using CMake to Build Examples to build the examples.
+Go into the share directory and follow the instructions in Using CMake to Build Examples to build the examples.
In general, users must first set the HDF5_ROOT environment variable to the installed location of the CMake
configuration files for HDF5. For example, on Windows the following path might be set:
diff --git a/doxygen/dox/Overview.dox b/doxygen/dox/Overview.dox
index b472d4d2a8d..6caffd147aa 100644
--- a/doxygen/dox/Overview.dox
+++ b/doxygen/dox/Overview.dox
@@ -21,7 +21,7 @@ documents cover a mix of tasks, concepts, and reference, to help a specific
audience succeed.
\par Offline reading
- You can download it as an archive for offline reading.
+ You can download it as an archive for offline reading.
\par ToDo List
There is plenty of unfinished business.
diff --git a/doxygen/dox/Specifications.dox b/doxygen/dox/Specifications.dox
index 77bb0a8f407..de9c23d80aa 100644
--- a/doxygen/dox/Specifications.dox
+++ b/doxygen/dox/Specifications.dox
@@ -54,7 +54,101 @@
*/
/** \page TBL HDF5 Table Specification Version 1.0
+The HDF5 specification defines the standard objects and storage for the standard HDF5
+objects. (For information about the HDF5 library, model and specification, see the HDF
+documentation.) This document is an additional specification do define a standard profile
+for how to store tables in HDF5. Table data in HDF5 is stored as HDF5 datasets with standard
+attributes to define the properties of the tables.
+
+\section sec_tab_spec_intro Introduction
+A generic table is a sequence of records, each record has a name and a type. Table data
+is stored as an HDF5 one dimensional compound dataset. A table is defined as a collection
+of records whose values are stored in fixed-length fields. All records have the same structure
+and all values in each field have the same data type.
+
+The dataset for a table is distinguished from other datasets by giving it an attribute
+"CLASS=TABLE". Optional attributes allow the storage of a title for the Table and for
+each column, and a fill value for each column.
+
+\section sec_tab_spec_attr Table Attributes
+The attributes for the Table are strings. They are written with the #H5LTset_attribute_string
+Lite API function. "Required" attributes must always be used. "Optional" attributes must be
+used when required.
+
+Table 1. Attributes of an Image Dataset
+
+Attribute Name |
+Required Optional |
+Type |
+String Size |
+Value |
+Description |
+
+
+CLASS |
+Required |
+String |
+5 |
+"TABLE" |
+This attribute is type #H5T_C_S1, with size 5. For all Tables, the value of this attribute is
+TABLE. This attribute identifies this data set as intended to be interpreted as Table that
+conforms to the specifications on this page. |
+
+
+VERSION |
+Required |
+String |
+3 |
+"0.2" |
+This attribute is of type #H5T_C_S1, with size corresponding to the length of the version string.
+This attribute identifies the version number of this specification to which it conforms. The current
+version number is "0.2". |
+
+
+TITLE |
+Optional |
+String |
+ |
+ |
+The TITLE is an optional String that is to be used as the informative title of the whole table.
+The TITLE is set with the parameter table_title of the function #H5TBmake_table. |
+
+
+FIELD_(n)_NAME |
+Required |
+String |
+ |
+ |
+The FIELD_(n)_NAME is an optional String that is to be used as the informative title of column n
+of the table. For each of the fields the word FIELD_ is concatenated with the zero based field (n)
+index together with the name of the field. |
+
+
+FIELD_(n)_FILL |
+Optional |
+String |
+ |
+ |
+The FIELD_(n)_FILL is an optional String that is the fill value for column n of the table.
+For each of the fields the word FIELD_ is concatenated with the zero based field (n) index
+together with the fill value, if present. This value is written only when a fill value is defined
+for the table. |
+
+
+
+The following section of code shows the calls necessary to the creation of a table.
+\code
+// Create a new HDF5 file using default properties.
+file_id = H5Fcreate("my_table.h5", H5F_ACC_TRUNC, H5P_DEFAULT, H5P_DEFAULT);
+
+// Call the make table function
+H5TBmake_table("Table Title", file_id, "Table1", NFIELDS, NRECORDS, dst_size, field_names, dst_offset, field_type, chunk_size, fill_data, compress, p_data);
+
+// Close the file.
+status = H5Fclose(file_id);
+\endcode
+
+For more information see the @ref H5TB reference manual page and the @ref H5TB_UG, which includes examples.
-\htmlinclude TableSpec.html
*/
diff --git a/doxygen/dox/TechnicalNotes.dox b/doxygen/dox/TechnicalNotes.dox
index 787a0d8a448..b0f1c8f4cbc 100644
--- a/doxygen/dox/TechnicalNotes.dox
+++ b/doxygen/dox/TechnicalNotes.dox
@@ -1094,7 +1094,7 @@ A beneficial side effect of using SWMR access is better fault tolerance. It is m
\subsection subsec_swmr_doc Documentation
\subsubsection subsubsec_swmr_doc_guide User Guide
-SWMR User Guide
+SWMR User Guide
\subsubsection subsubsec_swmr_doc_apis HDF5 Library APIs
diff --git a/doxygen/examples/TableSpec.html b/doxygen/examples/TableSpec.html
deleted file mode 100644
index 474176e14d5..00000000000
--- a/doxygen/examples/TableSpec.html
+++ /dev/null
@@ -1,193 +0,0 @@
-
-
- HDF5 Table Specification
-
-
-The HDF5 specification defines the standard objects and storage for the
-standard HDF5 objects. (For information about the HDF5 library, model and
-specification, see the HDF documentation.) This document is an additional
-specification do define a standard profile for how to store tables in HDF5.
-Table data in HDF5 is stored as HDF5 datasets with standard attributes to define
-the properties of the tables.
-
-
-1. Overview
-A generic table is a sequence of records, each record has a name and a type.
-Table data is stored as an HDF5 one dimensional compound dataset. A table
-is defined as a collection of records whose values are stored in fixed-length
-fields. All records have the same structure and all values in each field have
-the same data type.
-The dataset for a table is distinguished from other datasets by giving
-it an attribute "CLASS=TABLE".
-Optional attributes allow the storage of a title for the Table and for
-each column, and a fill value for each column.
-
-2. Table Attributes
-The attributes for the Table are strings. They are written with the H5LTset_attribute_string
-Lite API function. "Required" attributes must always be used. "Optional" attributes
-must be used when required.
-
-
-Attributes
-
-
--
-Attribute name="CLASS" (Required)
-
--
-This attribute is type H5T_C_S1, with size 5.
-
--
-For all Tables, the value of this attribute is "TABLE".
-
--
-This attribute identifies this data set as intended to be interpreted as Table that conforms to the specifications on this page.
-
-
-
-Attribute name="VERSION" (Required)
-
--
-This attribute is of type H5T_C_S1, with size corresponding to the length
-of the version string. This attribute identifies the version number
-of this specification to which it conforms. The current version number
-is "0.2".
-
-
-
-
--
-Attribute name="TITLE" (Optional)
-
--
-The TITLE is an optional String that is to be used as the
-informative title of the whole table.
-The TITLE is set with the parameter
table_title
of the function
- H5TBmake_table
.
-
-
-
--
-Attribute name="FIELD_(n)_NAME" (Required)
-
--
-The FIELD_(n)_NAME is an optional String that is to be used as the
-informative title of column n of the table.
-For each of the fields the word FIELD_ is concatenated with
- the zero based field (n) index together with the name of the field.
-
-
-
--
-Attribute name="FIELD_(n)_FILL" (Optional)
-
--
-The FIELD_(n)_FILL is an optional String that is the fill value for
-column n of the table.
-For each of the fields the word FIELD_ is concatenated with
- the zero based field (n) index together with the fill value, if present.
-This value is written only when a fill value is defined for the table.
-
-
-
-
-
-
-
-Table 1. Attributes of an Image Dataset
-
-
-Attribute Name |
-
-(R = Required
- O= Optional) |
-
-Type |
-
-String Size |
-
-Value |
-
-
-
-CLASS |
-
-R |
-
-String |
-
-5 |
-
-"TABLE" |
-
-
-
-VERSION |
-
-R |
-
-String |
-
-3 |
-
-"0.2" |
-
-
-
-TITLE |
-
-O |
-
-String |
-
- |
-
-
-
- |
-FIELD_(n)_NAME |
-
-R |
-
-String |
-
- |
-
-
-
-
- |
-FIELD_(n)_FILL |
-
-O* |
-
-String |
-
- |
-
-
-
- |
-
-
-
-
-
-
-
-* The attribute FIELD_(n)_FILL is written to the table if a fill value is
-specified on the creation of the Table. Otherwise, it is not.The following
-section of code shows the calls necessary to the creation of a table.
-
-
/* Create a new HDF5 file using default properties. */
- file_id = H5Fcreate( "my_table.h5", H5F_ACC_TRUNC, H5P_DEFAULT, H5P_DEFAULT );
-
-/* Call the make table function */
-
H5TBmake_table( "Table Title", file_id, "Table1", NFIELDS, NRECORDS, dst_size,
- field_names, dst_offset, field_type,
- chunk_size, fill_data, compress, p_data )
-
- /* Close the file. */
- status = H5Fclose( file_id );
-
-
diff --git a/doxygen/hdf5_footer.html b/doxygen/hdf5_footer.html
index 520f3f57291..6023e109739 100644
--- a/doxygen/hdf5_footer.html
+++ b/doxygen/hdf5_footer.html
@@ -3,18 +3,15 @@
+