From 265494b5b94c9f83ce80e06669bab83398c1970b Mon Sep 17 00:00:00 2001 From: Dana Robinson <43805+derobins@users.noreply.github.com> Date: Mon, 1 May 2023 09:06:39 -0700 Subject: Remove "the the" from comments and docs (#2865) --- doxygen/dox/LearnBasics2.dox | 2 +- doxygen/dox/LearnBasics3.dox | 2 +- doxygen/dox/ViewTools.dox | 2 +- doxygen/examples/H5.format.1.0.html | 2 +- doxygen/examples/H5.format.1.1.html | 2 +- doxygen/examples/ImageSpec.html | 12 ++++++------ doxygen/examples/tables/propertyLists.dox | 2 +- doxygen/hdf5_navtree_hacks.js | 2 +- fortran/src/H5Af.c | 6 +++--- fortran/src/H5Lf.c | 2 +- fortran/src/H5Sf.c | 4 ++-- fortran/src/H5Tf.c | 2 +- fortran/test/tH5A_1_8.F90 | 12 ++++++------ hl/test/test_ds.c | 2 +- hl/test/test_dset_append.c | 2 +- release_docs/HISTORY-1_0-1_8_0.txt | 2 +- release_docs/HISTORY-1_8_0-1_10_0.txt | 4 ++-- test/tselect.c | 6 +++--- tools/lib/h5tools_dump.c | 2 +- 19 files changed, 35 insertions(+), 35 deletions(-) diff --git a/doxygen/dox/LearnBasics2.dox b/doxygen/dox/LearnBasics2.dox index 6f94c7f..87bbe87 100644 --- a/doxygen/dox/LearnBasics2.dox +++ b/doxygen/dox/LearnBasics2.dox @@ -788,7 +788,7 @@ The function #H5Tarray_create creates a new array datatype object. Parameters sp \li the dimension permutation of the array, i.e., whether the elements of the array are listed in C or FORTRAN order.

Working with existing array datatypes

-When working with existing arrays, one must first determine the the rank, or number of dimensions, of the array. +When working with existing arrays, one must first determine the rank, or number of dimensions, of the array. The function #H5Tget_array_dims returns the rank of a specified array datatype. diff --git a/doxygen/dox/LearnBasics3.dox b/doxygen/dox/LearnBasics3.dox index 2fe0f52..06afacd 100644 --- a/doxygen/dox/LearnBasics3.dox +++ b/doxygen/dox/LearnBasics3.dox @@ -210,7 +210,7 @@ For details on compiling an HDF5 application: an extendible array dataset, pass in #H5P_DATASET_CREATE for the property list class. \li The #H5Pset_chunk call modifies a Dataset Creation Property List instance to store a chunked layout dataset and sets the size of the chunks used. -\li To extend an unlimited dimension dataset use the the #H5Dset_extent call. Please be aware that +\li To extend an unlimited dimension dataset use the #H5Dset_extent call. Please be aware that after this call, the dataset's dataspace must be refreshed with #H5Dget_space before more data can be accessed. \li The #H5Pget_chunk call retrieves the size of chunks for the raw data of a chunked layout dataset. \li Once there is no longer a need for a Property List instance, it should be closed with the #H5Pclose call. diff --git a/doxygen/dox/ViewTools.dox b/doxygen/dox/ViewTools.dox index 2212d4b..66b2def 100644 --- a/doxygen/dox/ViewTools.dox +++ b/doxygen/dox/ViewTools.dox @@ -465,7 +465,7 @@ example h5_crtgrpar.c. To disp \endcode \subsubsection subsubsecViewToolsViewDset_h5dumpEx5 Example 5 -The -p option is used to examine the the dataset filters, storage layout, and fill value properties of a dataset. +The -p option is used to examine the dataset filters, storage layout, and fill value properties of a dataset. This option can be useful for checking how well compression works, or even for analyzing performance and dataset size issues related to chunking. (The smaller the chunk size, the more chunks that HDF5 diff --git a/doxygen/examples/H5.format.1.0.html b/doxygen/examples/H5.format.1.0.html index 4eb0548..26d0421 100644 --- a/doxygen/examples/H5.format.1.0.html +++ b/doxygen/examples/H5.format.1.0.html @@ -1488,7 +1488,7 @@ Elena> "Free-space object" - Object Size This is the size of the the fields + Object Size This is the size of the fields above plus the object data stored for the object. The actual storage size is rounded up to a multiple of eight. diff --git a/doxygen/examples/H5.format.1.1.html b/doxygen/examples/H5.format.1.1.html index 9d03a76..3af50d6 100644 --- a/doxygen/examples/H5.format.1.1.html +++ b/doxygen/examples/H5.format.1.1.html @@ -6091,7 +6091,7 @@ TABLE.list TD { border:none; } Used by the library before version 1.6.1. In this version, the Flags field is used to indicate whether the actual message is stored in the global heap (never implemented). The Pointer field - either contains the the header message address in the global heap + either contains the header message address in the global heap (never implemented) or the address of the shared object header. diff --git a/doxygen/examples/ImageSpec.html b/doxygen/examples/ImageSpec.html index 1b700ff..130d86e 100644 --- a/doxygen/examples/ImageSpec.html +++ b/doxygen/examples/ImageSpec.html @@ -851,7 +851,7 @@ This defines the color model that the entries in the palette data set represent. "RGB"
-Each color index contains a triplet where the the first value defines the +Each color index contains a triplet where the first value defines the red component, second defines the green component, and the third the blue component.
@@ -859,7 +859,7 @@ component. "CMY"
-Each color index contains a triplet where the the first value defines the +Each color index contains a triplet where the first value defines the cyan component, second defines the magenta component, and the third the yellow component.
@@ -867,7 +867,7 @@ yellow component. "CMYK"
-Each color index contains a quadruplet where the the first value defines +Each color index contains a quadruplet where the first value defines the cyan component, second defines the magenta component, the third the yellow component, and the forth the black component.
@@ -875,7 +875,7 @@ yellow component, and the forth the black component. "YCbCr"
-Class Y encoding model. Each color index contains a triplet where the the +Class Y encoding model. Each color index contains a triplet where the first value defines the luminance, second defines the Cb Chromonance, and the third the Cr Chromonance.
@@ -884,14 +884,14 @@ the third the Cr Chromonance.
Composite encoding color model. Each color index contains a triplet where -the the first value defines the luminance component, second defines the +the first value defines the luminance component, second defines the chromonance component, and the third the value component.
"HSV"
-Each color index contains a triplet where the the first value defines the +Each color index contains a triplet where the first value defines the hue component, second defines the saturation component, and the third the value component. The hue component defines the hue spectrum with a low value representing magenta/red progressing to a high value which would diff --git a/doxygen/examples/tables/propertyLists.dox b/doxygen/examples/tables/propertyLists.dox index 4e20197..a260c9d 100644 --- a/doxygen/examples/tables/propertyLists.dox +++ b/doxygen/examples/tables/propertyLists.dox @@ -245,7 +245,7 @@ file access property list. #H5Pset_page_buffer_size/#H5Pget_page_buffer_size -Set/get the the maximum size for the page buffer. +Set/get the maximum size for the page buffer. #H5Pset_sieve_buf_size/#H5Pget_sieve_buf_size diff --git a/doxygen/hdf5_navtree_hacks.js b/doxygen/hdf5_navtree_hacks.js index dda8984..804701f 100644 --- a/doxygen/hdf5_navtree_hacks.js +++ b/doxygen/hdf5_navtree_hacks.js @@ -141,7 +141,7 @@ function initNavTree(toroot,relpath) $(window).on("load", showRoot); } -// return false if the the node has no children at all, or has only section/subsection children +// return false if the node has no children at all, or has only section/subsection children function checkChildrenData(node) { if (!(typeof(node.childrenData)==='string')) { for (var i in node.childrenData) { diff --git a/fortran/src/H5Af.c b/fortran/src/H5Af.c index ba3b62d..0fdd8fd 100644 --- a/fortran/src/H5Af.c +++ b/fortran/src/H5Af.c @@ -359,7 +359,7 @@ done: * loc_id - Object identifier * OUTPUTS * - * corder_valid - Indicates whether the the creation order data is valid for this attribute + * corder_valid - Indicates whether the creation order data is valid for this attribute * corder - Is a positive integer containing the creation order of the attribute * cset - Indicates the character set used for the attribute’s name * data_size - indicates the size, in the number of characters, of the attribute @@ -427,7 +427,7 @@ done: * lapl_id - Link access property list * OUTPUTS * - * corder_valid - Indicates whether the the creation order data is valid for this attribute + * corder_valid - Indicates whether the creation order data is valid for this attribute * corder - Is a positive integer containing the creation order of the attribute * cset - Indicates the character set used for the attribute’s name * data_size - indicates the size, in the number of characters, of the attribute @@ -493,7 +493,7 @@ done: * lapl_id - Link access property list * OUTPUTS * - * corder_valid - Indicates whether the the creation order data is valid for this attribute + * corder_valid - Indicates whether the creation order data is valid for this attribute * corder - Is a positive integer containing the creation order of the attribute * cset - Indicates the character set used for the attribute’s name * data_size - indicates the size, in the number of characters, of the attribute diff --git a/fortran/src/H5Lf.c b/fortran/src/H5Lf.c index 63bed99..c7ce511 100644 --- a/fortran/src/H5Lf.c +++ b/fortran/src/H5Lf.c @@ -232,7 +232,7 @@ done: * lapl_id - Link access property list * OUTPUTS * - * corder_valid - Indicates whether the the creation order data is valid for this attribute + * corder_valid - Indicates whether the creation order data is valid for this attribute * corder - Is a positive integer containing the creation order of the attribute * cset - Indicates the character set used for the attribute’s name * data_size - indicates the size, in the number of characters, of the attribute diff --git a/fortran/src/H5Sf.c b/fortran/src/H5Sf.c index d04b639..00b97f8 100644 --- a/fortran/src/H5Sf.c +++ b/fortran/src/H5Sf.c @@ -176,7 +176,7 @@ h5scopy_c(hid_t_f *space_id, hid_t_f *new_space_id) * h5sget_select_hyper_nblocks_c * PURPOSE * Call H5SH5Sget_select_hyper_nblocks to - * get the the number of hyperslab blocks in + * get the number of hyperslab blocks in * the current dataspace selection if successful * INPUTS * space_id - identifier of the dataspace @@ -215,7 +215,7 @@ h5sget_select_hyper_nblocks_c(hid_t_f *space_id, hssize_t_f *num_blocks) * h5sget_select_elem_npoints_c * PURPOSE * Call H5Sget_select_elem_npoints to - * get the the number of element points in + * get the number of element points in * the current dataspace selection if successful * INPUTS * space_id - identifier of the dataspace diff --git a/fortran/src/H5Tf.c b/fortran/src/H5Tf.c index 11f62b7..a74f5d1 100644 --- a/fortran/src/H5Tf.c +++ b/fortran/src/H5Tf.c @@ -1373,7 +1373,7 @@ DONE: * type_id - identifier of the dataspace * member_no - Number of the field whose offset is requested * OUTPUTS - * offset - byte offset of the the beginning of the field of + * offset - byte offset of the beginning of the field of * a compound datatype * RETURNS * always 0 diff --git a/fortran/test/tH5A_1_8.F90 b/fortran/test/tH5A_1_8.F90 index d43279e..03e26ec 100644 --- a/fortran/test/tH5A_1_8.F90 +++ b/fortran/test/tH5A_1_8.F90 @@ -234,7 +234,7 @@ SUBROUTINE test_attr_corder_create_compact(fcpl,fapl, total_error) INTEGER(HID_T) :: attr !String Attribute identifier INTEGER(HSIZE_T), DIMENSION(7) :: data_dims - LOGICAL :: f_corder_valid ! Indicates whether the the creation order data is valid for this attribute + LOGICAL :: f_corder_valid ! Indicates whether the creation order data is valid for this attribute INTEGER :: corder ! Is a positive integer containing the creation order of the attribute INTEGER :: cset ! Indicates the character set used for the attribute’s name INTEGER(HSIZE_T) :: data_size ! indicates the size, in the number of characters @@ -411,7 +411,7 @@ SUBROUTINE test_attr_null_space(fcpl, fapl, total_error) INTEGER(HSIZE_T) :: storage_size ! attributes storage requirements - LOGICAL :: f_corder_valid ! Indicates whether the the creation order data is valid for this attribute + LOGICAL :: f_corder_valid ! Indicates whether the creation order data is valid for this attribute INTEGER :: corder ! Is a positive integer containing the creation order of the attribute INTEGER :: cset ! Indicates the character set used for the attribute’s name INTEGER(HSIZE_T) :: data_size ! indicates the size, in the number of characters @@ -753,7 +753,7 @@ SUBROUTINE test_attr_info_by_idx(new_format, fcpl, fapl, total_error) INTEGER(HID_T) :: attr !String Attribute identifier INTEGER(HSIZE_T), DIMENSION(7) :: data_dims - LOGICAL :: f_corder_valid ! Indicates whether the the creation order data is valid for this attribute + LOGICAL :: f_corder_valid ! Indicates whether the creation order data is valid for this attribute INTEGER :: corder ! Is a positive integer containing the creation order of the attribute INTEGER :: cset ! Indicates the character set used for the attribute’s name INTEGER(HSIZE_T) :: data_size ! indicates the size, in the number of characters @@ -934,7 +934,7 @@ SUBROUTINE attr_info_by_idx_check(obj_id, attrname, n, use_index, total_error ) CHARACTER(LEN=*) :: attrname INTEGER(HSIZE_T) :: n LOGICAL :: use_index - LOGICAL :: f_corder_valid ! Indicates whether the the creation order data is valid for this attribute + LOGICAL :: f_corder_valid ! Indicates whether the creation order data is valid for this attribute INTEGER :: corder ! Is a positive integer containing the creation order of the attribute INTEGER :: cset ! Indicates the character set used for the attribute’s name INTEGER(HSIZE_T) :: data_size ! indicates the size, in the number of characters @@ -1397,7 +1397,7 @@ SUBROUTINE test_attr_delete_by_idx(new_format, fcpl, fapl, total_error) INTEGER(HID_T) :: attr !String Attribute identifier INTEGER(HSIZE_T), DIMENSION(7) :: data_dims - LOGICAL :: f_corder_valid ! Indicates whether the the creation order data is valid for this attribute + LOGICAL :: f_corder_valid ! Indicates whether the creation order data is valid for this attribute INTEGER :: corder ! Is a positive integer containing the creation order of the attribute INTEGER :: cset ! Indicates the character set used for the attribute’s name INTEGER(HSIZE_T) :: data_size ! indicates the size, in the number of characters @@ -2690,7 +2690,7 @@ SUBROUTINE attr_open_check(fid, dsetname, obj_id, max_attrs, total_error ) INTEGER :: u CHARACTER (LEN=8) :: attrname INTEGER :: error - LOGICAL :: f_corder_valid ! Indicates whether the the creation order data is valid for this attribute + LOGICAL :: f_corder_valid ! Indicates whether the creation order data is valid for this attribute INTEGER :: corder ! Is a positive integer containing the creation order of the attribute INTEGER :: cset ! Indicates the character set used for the attribute’s name INTEGER(HSIZE_T) :: data_size ! indicates the size, in the number of characters diff --git a/hl/test/test_ds.c b/hl/test/test_ds.c index b74b62a..70af31a 100644 --- a/hl/test/test_ds.c +++ b/hl/test/test_ds.c @@ -3673,7 +3673,7 @@ out: * Function: match_dim_scale * * Purpose: example operator function used by H5DSiterate_scales, used - * to verify the the DSID scale size matches the dataset DIM size + * to verify the DSID scale size matches the dataset DIM size * * Return: * The return values from an operator are: diff --git a/hl/test/test_dset_append.c b/hl/test/test_dset_append.c index f8d38c2..c4afe89 100644 --- a/hl/test/test_dset_append.c +++ b/hl/test/test_dset_append.c @@ -1265,7 +1265,7 @@ main(void) /* * The following tests illustrate the scenarios when H5DOappend does not work with extensible array * indexing: - * - when the the dataset has 1 unlimited dimension and the other dimension is fixed but extendible + * - when the dataset has 1 unlimited dimension and the other dimension is fixed but extendible * - the dataset expands along 1 dimension and then expands along the other dimension */ flush_ct = 0; /* Reset flush counter */ diff --git a/release_docs/HISTORY-1_0-1_8_0.txt b/release_docs/HISTORY-1_0-1_8_0.txt index 3669f4d..333d0dc 100644 --- a/release_docs/HISTORY-1_0-1_8_0.txt +++ b/release_docs/HISTORY-1_0-1_8_0.txt @@ -1407,7 +1407,7 @@ Known Problems for your installation. Observe that the basic idea is to insert the script as the first item - on the command line which executes the the test. The script then + on the command line which executes the test. The script then executes the test and filters out the offending text before passing it on. diff --git a/release_docs/HISTORY-1_8_0-1_10_0.txt b/release_docs/HISTORY-1_8_0-1_10_0.txt index 7b84fbc..cc42d3b 100644 --- a/release_docs/HISTORY-1_8_0-1_10_0.txt +++ b/release_docs/HISTORY-1_8_0-1_10_0.txt @@ -791,7 +791,7 @@ Bug Fixes since HDF5-1.8.0 release and the external filters are being built, the CMAKE_BUILD_TYPE define must be set to the same value as the configuration (-DCMAKE_BUILD_TYPE:STRING=Release if using -C Release). This is needed - by the the szip and zlib filter build commands. (ADB - HDFFV-8695) + by the szip and zlib filter build commands. (ADB - HDFFV-8695) - CMake: Remove use of XLATE_UTILITY program. (ADB - 2014/03/28 HDFFV-8640) - CMake: Added missing quotes in setting the CMAKE_EXE_LINKER_FLAGS for the MPI option. (ADB - 2014/02/27 HDFFV-8674) @@ -1698,7 +1698,7 @@ Known Problems for your installation. Observe that the basic idea is to insert the script as the first item - on the command line which executes the the test. The script then + on the command line which executes the test. The script then executes the test and filters out the offending text before passing it on. diff --git a/test/tselect.c b/test/tselect.c index 3dd739c..d67e5bd 100644 --- a/test/tselect.c +++ b/test/tselect.c @@ -2280,7 +2280,7 @@ test_select_hyper_contig_dr__run_test(int test_num, const uint16_t *cube_buf, co * H5Sselect_shape_same() views as being of the same shape. * * Start by writing small_rank D slices from the in memory large cube, to - * the the on disk small cube dataset. After each write, read the small + * the on disk small cube dataset. After each write, read the small * cube dataset back from disk, and verify that it contains the expected * data. Verify that H5Sselect_shape_same() returns true on the * memory and file selections. @@ -3309,7 +3309,7 @@ test_select_hyper_checker_board_dr__run_test(int test_num, const uint16_t *cube_ * H5Sselect_shape_same() views as being of the same shape. * * Start by writing small_rank D slices from the in memory large cube, to - * the the on disk small cube dataset. After each write, read the small + * the on disk small cube dataset. After each write, read the small * cube dataset back from disk, and verify that it contains the expected * data. Verify that H5Sselect_shape_same() returns true on the * memory and file selections. @@ -15840,7 +15840,7 @@ test_hyper_io_1d(void) hsize_t chunk_dims[1]; /* Chunk dimension size */ hsize_t offset[1]; /* Starting offset for hyperslab */ hsize_t stride[1]; /* Distance between blocks in the hyperslab selection */ - hsize_t count[1]; /* # of blocks in the the hyperslab selection */ + hsize_t count[1]; /* # of blocks in the hyperslab selection */ hsize_t block[1]; /* Size of block in the hyperslab selection */ unsigned int wdata[CHUNKSZ]; /* Data to be written */ unsigned int rdata[NUM_ELEMENTS / 10]; /* Data to be read */ diff --git a/tools/lib/h5tools_dump.c b/tools/lib/h5tools_dump.c index 435ca87..57a1712 100644 --- a/tools/lib/h5tools_dump.c +++ b/tools/lib/h5tools_dump.c @@ -3747,7 +3747,7 @@ h5tools_dump_dcpl(FILE *stream, const h5tool_format_t *info, h5tools_context_t * /*------------------------------------------------------------------------- * Function: dump_comment * - * Purpose: prints the comment for the the object name + * Purpose: prints the comment for the object name * * Return: void *------------------------------------------------------------------------- -- cgit v0.12