diff --git a/.codespellrc b/.codespellrc new file mode 100644 index 00000000..7a80203c --- /dev/null +++ b/.codespellrc @@ -0,0 +1,6 @@ +# Ref: https://github.com/codespell-project/codespell#using-a-config-file +[codespell] +skip = .git,.codespellrc,*.pdf,*.pdf_*,*.ai,*.cgns,./CGNS-ReST-site/sidslexer.py +check-hidden = true +#ignore-regex = +ignore-words-list = categorie,otation,Udo,collet,Celcius diff --git a/.github/workflows/codespell.yml b/.github/workflows/codespell.yml new file mode 100644 index 00000000..e12dd8bc --- /dev/null +++ b/.github/workflows/codespell.yml @@ -0,0 +1,15 @@ +# GitHub Action to automate the identification of common misspellings in text files +# https://github.com/codespell-project/codespell +# https://github.com/codespell-project/actions-codespell +# +# uses ".codespellrc" for configuration +# +name: codespell +on: [push, pull_request] +jobs: + codespell: + name: Check for spelling errors + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - uses: codespell-project/actions-codespell@master \ No newline at end of file diff --git a/BuildingCGNS/build_cgns_MS.bat~ b/BuildingCGNS/build_cgns_MS.bat~ deleted file mode 100644 index bf235526..00000000 --- a/BuildingCGNS/build_cgns_MS.bat~ +++ /dev/null @@ -1,24 +0,0 @@ -@echo OFF -:: Run the cmake command -cmake -G "Visual Studio 15 Win64"^ - -D CMAKE_PREFIX_PATH:PATH="C:\Program Files\HDF_Group\HDF5\1.11.2\cmake" ^ - -D CMAKE_BUILD_TYPE=Debug ^ - -D CGNS_ENABLE_FORTRAN:BOOL=OFF ^ - -D CGNS_BUILD_SHARED:BOOL=OFF ^ - -D CMAKE_STATIC_LINKER_FLAGS:STRING="/NODEFAULTLIB:library" ^ - -D CMAKE_EXE_LINKER_FLAGS:STRING="/NODEFAULTLIB:library" ^ - -D CGNS_USE_SHARED:BOOL=OFF ^ - -D CGNS_ENABLE_LEGACY=ON ^ - -D CGNS_ENABLE_64BIT=BOOL=ON ^ - -D CGNS_BUILD_CGNSTOOLS:BOOL=OFF ^ - -D CGNS_ENABLE_TESTS:BOOL=ON ^ - -D CMAKE_VERBOSE_MAKEFILE:BOOL=ON ^ - -D CGNS_ENABLE_HDF5:BOOL=ON ^ - -D CGNS_ENABLE_PARALLEL:BOOL=OFF ^ - -D HDF5_BUILD_SHARED_LIBS:BOOL=OFF ^ - -D HDF5_NEED_MPI:BOOL=OFF ^ - -D HDF5_NEED_ZLIB:BOOL=OFF ^ - -D HDF5_NEED_SZIP:BOOL=OFF ^ - ../CGNS - - cmake --build . diff --git a/CGNS-ReST-site/MIGRATION.txt b/CGNS-ReST-site/MIGRATION.txt index 8bc0465e..eb8cbf4b 100644 --- a/CGNS-ReST-site/MIGRATION.txt +++ b/CGNS-ReST-site/MIGRATION.txt @@ -5,7 +5,7 @@ The migration is supposed to be a straightforward translation from a doc format to another. This is not exactly the case, the first reason is that some parts have be written for paper docs, with duplicated parts. The second is -the use of the reference links which implies some doc hirarchy reorganisation. +the use of the reference links which implies some doc hierarchy reorganisation. The existing pages of the original reference web site are sometimes kept unchanged, sometime reorganized. No information is deleted, some diff --git a/CGNS-ReST-site/source/current/CPEX.rst b/CGNS-ReST-site/source/current/CPEX.rst index ac18f0d8..4cdd301f 100644 --- a/CGNS-ReST-site/source/current/CPEX.rst +++ b/CGNS-ReST-site/source/current/CPEX.rst @@ -48,7 +48,7 @@ Comments on proposals should be sent to cgnstalk@lists.nasa.gov and/or written d .. - _Comment: Bellow should be listed all CPEX implemented or waiting for review + _Comment: Below should be listed all CPEX implemented or waiting for review .. _CPEX0046: diff --git a/CGNS-ReST-site/source/current/examples.rst b/CGNS-ReST-site/source/current/examples.rst index 06712c2c..bdd6cab3 100644 --- a/CGNS-ReST-site/source/current/examples.rst +++ b/CGNS-ReST-site/source/current/examples.rst @@ -190,7 +190,7 @@ Business Jet - July.29.04 - :Description: Multiblock stuctured grids for a business jet, a wing/body, and a wing/body/nacelle/pylon configuration are available from Stanford. + :Description: Multiblock structured grids for a business jet, a wing/body, and a wing/body/nacelle/pylon configuration are available from Stanford. :Data File: `Stanford CGNS test files `_ (link to external site) diff --git a/CGNS-ReST-site/source/current/news.rst b/CGNS-ReST-site/source/current/news.rst index b9246f1e..e2746317 100644 --- a/CGNS-ReST-site/source/current/news.rst +++ b/CGNS-ReST-site/source/current/news.rst @@ -58,12 +58,12 @@ the documentation news and fixes and end of this page. - Added :ref:`CPEX0042` Storing bounding box of a grid (:issue:`CGNS-149`). - Added :ref:`CPEX0043` Family hierarchy as a tree (:issue:`CGNS-180`). -.. topic:: Febuary 17, 2020 +.. topic:: February 17, 2020 - :version:`v4.0.0` of the CGNS Software is released. - Added :ref:`CPEX0041` NGON modification proposal (:issue:`CGNS-121`). -.. topic:: Febuary 17, 2020 +.. topic:: February 17, 2020 - :version:`v3.4.1` (patch) of the CGNS Software is released. - Removed :ref:`CPEX0041` NGON modification proposal (:issue:`CGNS-121`). @@ -97,7 +97,7 @@ the documentation news and fixes and end of this page. are set then FCFLAGS is ignored. - Replaced the hid_t to double (and vice-versa) utilities to_HDF_ID and to_ADF_ID from a type cast to a function which uses memcpy for the - conversion. This is needed for the upcomming release of HDF5 1.10 where + conversion. This is needed for the upcoming release of HDF5 1.10 where hid_t was changed from a 32 bit integer to a 64 bit integer. Should be transparent to user. - Implemented :ref:`CPEX0039` : To enable with CGNS_ENABLE_BASE_SCOPE @@ -229,7 +229,7 @@ the documentation news and fixes and end of this page. a file number (suggestion from Marc Poinet), adds HTMLHelp interface to cmake scripts, fixes a compiler complaint about comparison between int and enum, and fixes Fortran detection and MPI path problems - in the CMake scripts. Compatability with version 2.5 + in the CMake scripts. Compatibility with version 2.5 (file type CG_FILE_ADF2) is also fixed for both CG_MODE_WRITE and CG_MODE_MODIFY. The CGNStools documentation has been removed from the source distribution, and is now accessed from @@ -249,7 +249,7 @@ the documentation news and fixes and end of this page. with MPI. It also implements the Hierarchy of families (CPEX 0033), Multiple families (CPEX 0034), and Cubic elements (CPEX 0036). Compression (rewriting) of modified CGNS files is no longer automatically - done, since this may interfere with parallel I/O. This may be reenabled + done, since this may interfere with parallel I/O. This may be re-enabled within an application with the cg_set_compress function, or done later through the CGNSview GUI or with the cgnscompress program in the tools subdirectory. Conversion programs to and from AFLR3, FAST, and TetGen @@ -352,7 +352,7 @@ the documentation news and fixes and end of this page. .. topic:: March 11, 2007: Version 2.5.3 released. - - This version changes the mispelled Celcius to Celsius, fixes handling of + - This version changes the misspelled Celcius to Celsius, fixes handling of soft links when rewriting the CGNS file, and fixes a number of gcc compiler warnings. @@ -406,7 +406,7 @@ the documentation news and fixes and end of this page. than a "Windows" type color scheme. Fixes some minor bugs and adds some improvement to the cgnscheck program. Allows reading of both HDF5 and ADF - based CGNS files (requires the adf2hdf and hdf2adf - convertor programs). + converter programs). .. topic:: Spring, 2006: @@ -416,7 +416,7 @@ the documentation news and fixes and end of this page. The first is a Panel discussion, tentatively titled "CGNS Practical Applications in CFD". This will occur during the regular AIAA sessions at the conference. - The second is a "CGNS Tutorial Session", currently scheduled for Wednsday, + The second is a "CGNS Tutorial Session", currently scheduled for Wednesday, 7 June 2006 in the evening. This session will be conducted in two parts: (1) Basic usage of CGNS (including examples for structured @@ -1357,7 +1357,7 @@ Documentation news Corrected an error in the SIDS document, in the Elements_t data structure examples. The examples included DataArray_t data structures defining ParentData for 3-D elements, where it doesn't apply. ## topic:: In the list of :issue:`CGNS-related` conference papers, added R. Magn - - an as an author for AIAA Paper 2005-0334. Apologies for inadvertantly omitting him in the original update. + - an as an author for AIAA Paper 2005-0334. Apologies for inadvertently omitting him in the original update. ## topic:: 19 Jan 2005 @@ -1402,7 +1402,7 @@ Documentation news ## topic:: 2 Jun 2004 - - Removed the wording "in the same manner as grid connectivity" in the description of the BC_t node in the SIDS-to-ADF File Mapping Manual, that was inadvertantly left in when the documentation was updated with the release of CGNS Version 2.3. + - Removed the wording "in the same manner as grid connectivity" in the description of the BC_t node in the SIDS-to-ADF File Mapping Manual, that was inadvertently left in when the documentation was updated with the release of CGNS Version 2.3. ## topic:: 18 May 2004 diff --git a/CGNS-ReST-site/source/general/FAQ.rst b/CGNS-ReST-site/source/general/FAQ.rst index 180be7a1..0f5ea33e 100644 --- a/CGNS-ReST-site/source/general/FAQ.rst +++ b/CGNS-ReST-site/source/general/FAQ.rst @@ -56,7 +56,7 @@ What do I do if CGNS is not capable of handling my particular application? CGNS has been designed to be very flexible, for handling a wide range of physics applications. However, if you find an application that is not covered, you are encouraged to utilize the "``UserDefined``" construct as needed. -In fact, the ``UserDefined`` node can be used to create an entire tree consisting of multilpe levels of ``UserDefined`` children nodes, so you can create an entire "pattern" for storing particular information. +In fact, the ``UserDefined`` node can be used to create an entire tree consisting of multiple levels of ``UserDefined`` children nodes, so you can create an entire "pattern" for storing particular information. Furthermore, if you feel that a change or addition is needed to the SIDS, or if you feel that a particular "pattern" you have created might be useful to others, please consider submitting a proposal for extension (see :ref:`CPEX guidelines ` and :ref:`Proposed Extensions page `). diff --git a/CGNS-ReST-site/source/general/glossary.rst b/CGNS-ReST-site/source/general/glossary.rst index a3e4a20b..d20a5336 100644 --- a/CGNS-ReST-site/source/general/glossary.rst +++ b/CGNS-ReST-site/source/general/glossary.rst @@ -15,7 +15,7 @@ Glossary API Stands for **Application Programming Interface**, it is a set of functions, constants, requirements written in a specific - programming langage for application developpers. + programming language for application developers. CGNS/MLL The **Mid-Level Library** (MLL) is an example implementation of the diff --git a/CGNS-ReST-site/source/general/overview.rst b/CGNS-ReST-site/source/general/overview.rst index b88381c4..c6dd9cd9 100644 --- a/CGNS-ReST-site/source/general/overview.rst +++ b/CGNS-ReST-site/source/general/overview.rst @@ -180,7 +180,7 @@ Structure of a CGNS Database In this section, the conceptual structure of a CGNS database, and the nodes from which it is built, are discussed. This describes the way in which the CGNS software "sees" the database, not necessarily the way in which it is -implementated. The details of the implementation are left to the +implemented. The details of the implementation are left to the underlying database manager. A CGNS database consists of a collection of elements called @@ -244,7 +244,7 @@ By definition, the root node of a CGNS database has the Label CGNSBase_t. The name of the CGNS database can be specified by the user and is stored in the "Name" field of the CGNSBase_t node. Current CGNS conventions require that the CGNSBase_t node be located directly below -a "root node" in the database file indentified by the name "/". +a "root node" in the database file identified by the name "/". A database file may contain multiple CGNS databases, and thus multiple CGNSBase_t nodes. However, each node labeled CGNSBase_t in a single diff --git a/CGNS-ReST-site/source/general/what.rst b/CGNS-ReST-site/source/general/what.rst index f5eb16df..243f450b 100644 --- a/CGNS-ReST-site/source/general/what.rst +++ b/CGNS-ReST-site/source/general/what.rst @@ -100,7 +100,7 @@ freely, subject to the following restrictions: not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. This license is borrowed from the zlib/libpng License, - and supercedes the GNU Lesser General Public License (LGPL) which + and supersedes the GNU Lesser General Public License (LGPL) which previously governed the use and distribution of the software. **Reference** diff --git a/CGNS-ReST-site/source/governance/support.rst b/CGNS-ReST-site/source/governance/support.rst index 9539b57d..3a88b787 100644 --- a/CGNS-ReST-site/source/governance/support.rst +++ b/CGNS-ReST-site/source/governance/support.rst @@ -246,7 +246,7 @@ header Fourth level ~~~~~~~~~~~~ - Fith level + Fifth level ++++++++++ The index is generated, you just have to mention an index entry in the text. @@ -278,7 +278,7 @@ Internal link ~~~~~~~~~~~~~ An internal link is composed of its *anchor* (the place in the web site -where you want to go to) and a *reference* (the words wich triggers +where you want to go to) and a *reference* (the words which triggers the jump to the anchor). An *anchor* is defined with: diff --git a/CGNS-ReST-site/source/license.rst b/CGNS-ReST-site/source/license.rst index 380343c2..674ec833 100644 --- a/CGNS-ReST-site/source/license.rst +++ b/CGNS-ReST-site/source/license.rst @@ -21,6 +21,6 @@ subject to the following restrictions: 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. -This license is borrowed from the zlib/libpng License, and supercedes the GNU Lesser General Public License (LGPL) which previously governed the use and distribution of the software. +This license is borrowed from the zlib/libpng License, and supersedes the GNU Lesser General Public License (LGPL) which previously governed the use and distribution of the software. .. last line diff --git a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_database.rst b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_database.rst index 0dce3fc1..9874dd6d 100644 --- a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_database.rst +++ b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_database.rst @@ -64,18 +64,18 @@ cgio_open_file - :code:`int file_mode` IN: Mode used for opening the file. The supported modes are. CGIO_MODE_READ, CGIO_MODE_WRITE, and CGIO_MODE_MODIFY. - :code:`int* cgio_num` - OUT: Indentifier for the open database file. + OUT: Identifier for the open database file. :Returns: ier - Error status :Modes: `r w m` :Description: - Opens a database file of the specified type and mode. If successfull, returns 0, and the database identifier in cgio_num, otherwise returns an error code. The database identifier is used to access the database in subsequent function calls. + Opens a database file of the specified type and mode. If successful, returns 0, and the database identifier in cgio_num, otherwise returns an error code. The database identifier is used to access the database in subsequent function calls. The mode in which the database is opened is given by file_mode, which may take the value CGIO_MODE_READ, CGIO_MODE_WRITE, or CGIO_MODE_MODIFY. New databases should be opened with CGIO_MODE_WRITE, while existing databases are opened with either CGIO_MODE_READ (for read-only access) or CGIO_MODE_MODIFY (for read/write access). - A specific database type may be specified by file_type, which may be one of CGIO_FILE_NONE, CGIO_FILE_ADF, CGIO_FILE_HDF5, or CGIO_FILE_ADF2. When opening a database in write mode, CGIO_FILE_NONE indicates that the default database type should be used, otherwise the specified database type will be opened. When opening in read or modify mode, CGIO_FILE_NONE indicates that any database type is acceptable, otherwise if the database type does not match that given by file_type an error will be retuned. + A specific database type may be specified by file_type, which may be one of CGIO_FILE_NONE, CGIO_FILE_ADF, CGIO_FILE_HDF5, or CGIO_FILE_ADF2. When opening a database in write mode, CGIO_FILE_NONE indicates that the default database type should be used, otherwise the specified database type will be opened. When opening in read or modify mode, CGIO_FILE_NONE indicates that any database type is acceptable, otherwise if the database type does not match that given by file_type an error will be returned. cgio_close_file @@ -88,7 +88,7 @@ cgio_close_file :Parameters: - :code:`int cgio_num` - OUT: Indentifier for the open database file. + OUT: Identifier for the open database file. :Returns: ier - Error status @@ -107,7 +107,7 @@ cgio_get_file_type :Parameters: - :code:`int cgio_num` - IN: Indentifier for the open database file. + IN: Identifier for the open database file. - :code:`int *file_type` OUT: Type of database file. acceptable values are :code:`CGIO_FILE_NONE`, :code:`CGIO_FILE_ADF`, :code:`CGIO_FILE_HDF5` and :code:`CGIO_FILE_ADF2`. @@ -116,7 +116,7 @@ cgio_get_file_type :Modes: `r w m` :Description: - Gets the type of the database given by cgio_num. Returns 0 and the type in file_type if successfull, else an error code. + Gets the type of the database given by cgio_num. Returns 0 and the type in file_type if successful, else an error code. cgio_get_root_id @@ -129,7 +129,7 @@ cgio_get_root_id :Parameters: - :code:`int cgio_num` - IN: Indentifier for the open database file. + IN: Identifier for the open database file. - :code:`double *rootid` OUT: Node identifier for the root node of the database. @@ -138,7 +138,7 @@ cgio_get_root_id :Modes: `r w m` :Description: - Gets the unique node identifier for the root node in the database given by :code:`cgio_num`. Returns 0 and the identifier in :code:`rootid` if successfull, else an error code. + Gets the unique node identifier for the root node in the database given by :code:`cgio_num`. Returns 0 and the identifier in :code:`rootid` if successful, else an error code. diff --git a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_example.rst b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_example.rst index 30d7623d..94b67f96 100644 --- a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_example.rst +++ b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_example.rst @@ -462,7 +462,7 @@ Fortran example PRINT *,' DATA:' WRITE(*,200)(ID(I),I=1,6) C - C 4.) N13 THROUTH L2 + C 4.) N13 THROUGH L2 C CALL CGIO_GET_NODE_ID_F(ICGIO,RID,'N3/N11/L2',CID,IERR) CALL CGIO_GET_LABEL_F(ICGIO,CID,TSTLBL,IERR) diff --git a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_links.rst b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_links.rst index 089fc14c..34f871d7 100644 --- a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_links.rst +++ b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_links.rst @@ -30,7 +30,7 @@ cgio_is_link :Modes: `r w m` :Description: - Determines if the node indentified by :code:`id` in the database given by :code:`cgio_num` is a link or not. The function returns 0 if successfull, else an error code. If this node is a link, then the total length of the linked-to file and node information is returned in :code:`link_len`. If the node is not a link, :code:`link_len` will be 0. + Determines if the node identified by :code:`id` in the database given by :code:`cgio_num` is a link or not. The function returns 0 if successful, else an error code. If this node is a link, then the total length of the linked-to file and node information is returned in :code:`link_len`. If the node is not a link, :code:`link_len` will be 0. cgio_link_size @@ -92,7 +92,7 @@ cgio_create_link :Modes: `- w m` :Description: - Creates a link node as a child of the parent node identified by pid in the database given by cgio_num. The name of the node is given by name, the name of the linked-to file by filename, and the pathname to the linked-to node by name_in_file. If this is an internal link (link to a node in the same database), then filename should be defined as NULL or an empty string. The function returns 0 and the indentifier of the new node in id on success, otherwise an error code is returned. + Creates a link node as a child of the parent node identified by pid in the database given by cgio_num. The name of the node is given by name, the name of the linked-to file by filename, and the pathname to the linked-to node by name_in_file. If this is an internal link (link to a node in the same database), then filename should be defined as NULL or an empty string. The function returns 0 and the identifier of the new node in id on success, otherwise an error code is returned. cgio_get_link @@ -122,7 +122,7 @@ cgio_get_link :Modes: `r w m` :Description: - Gets the link information for the node identified by id in the database given by cgio_num. If successfull, the function returns 0 and the linked-to file name in filename and the node pathname in name_in_file. These strings are '0'-terminated, and thus should be dimensioned at least (file_len + 1) and (name_len + 1), respectively If this is an internal link (link to a node in the same database), then filename will be an empty string. The maximum length for a file name is given by CGIO_MAX_FILE_LENGTH (1024) and for a link pathname by CGIO_MAX_LINK_LENGTH (4096). + Gets the link information for the node identified by id in the database given by cgio_num. If successful, the function returns 0 and the linked-to file name in filename and the node pathname in name_in_file. These strings are '0'-terminated, and thus should be dimensioned at least (file_len + 1) and (name_len + 1), respectively If this is an internal link (link to a node in the same database), then filename will be an empty string. The maximum length for a file name is given by CGIO_MAX_FILE_LENGTH (1024) and for a link pathname by CGIO_MAX_LINK_LENGTH (4096). diff --git a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_misc.rst b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_misc.rst index 5f5324bb..ba837c32 100644 --- a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_misc.rst +++ b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_misc.rst @@ -26,7 +26,7 @@ cgio_flush_to_disk :Modes: `- w m` :Description: - Forces any buffered data in the database manager to be written to disk. Returns 0 if successfull, else an error code. + Forces any buffered data in the database manager to be written to disk. Returns 0 if successful, else an error code. cgio_library_version -------------------- @@ -53,7 +53,7 @@ cgio_library_version :Description: Gets the current library version for the database given by :code:`cgio_num`. The version is returned in version which is of maximum length :code:`CGIO_MAX_VERSION_LENGTH` (32). - In C, version should be dimensioned at least 33 in the calling routine to allow for the terminating :code:`'0'`. The function returns 0 if successfull, else an error code. + In C, version should be dimensioned at least 33 in the calling routine to allow for the terminating :code:`'0'`. The function returns 0 if successful, else an error code. cgio_file_version @@ -87,7 +87,7 @@ cgio_file_version The creation date is returned in :code:`creation_date`, and the last modified date in :code:`modified_date`, which are of maximum length :code:`CGIO_MAX_DATE_LENGTH` (32). In C, these should be dimensioned at least 33 in the calling routine to allow for the terminating :code:`'0'`. - The function returns 0 if successfull, else an error code. + The function returns 0 if successful, else an error code. .. last line diff --git a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_node.rst b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_node.rst index 42cadd4e..5f69b3e3 100644 --- a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_node.rst +++ b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_node.rst @@ -34,7 +34,7 @@ cgio_get_node_id :Description: Gets the node identifier for the node specified by :code:`pathname` in the database given by :code:`cgio_num`. if :code:`pathname` starts with :code:`'/'`, then it is taken as an absolute path and is located based on the root id of the database, - otherwise it is taken to be a relative path from the parent node identifed by :code:`pid`. + otherwise it is taken to be a relative path from the parent node identified by :code:`pid`. The function returns 0 and the node identifier in :code:`id` on success, else an error code. cgio_get_name @@ -93,7 +93,7 @@ cgio_set_name :Modes: `- w m` :Description: - Sets (renames) the node identied by :code:`id` in the database given by :code:`cgio_num` to :code:`name`. + Sets (renames) the node identified by :code:`id` in the database given by :code:`cgio_num` to :code:`name`. The parent node identifier is given by :code:`pid`. There must not already exist a child node of :code:`pid` with that name. The function return 0 on success, else an error code. cgio_get_label @@ -148,7 +148,7 @@ cgio_set_label :Modes: `- w m` :Description: - Sets the label of the node identied by :code:`id` in the database given by :code:`cgio_num` to label. + Sets the label of the node identified by :code:`id` in the database given by :code:`cgio_num` to label. The function return 0 on success, else an error code. cgio_get_data_type diff --git a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_structure.rst b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_structure.rst index b85485dc..2cd37929 100644 --- a/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_structure.rst +++ b/CGNS-ReST-site/source/standard/CGIO/CGNS_CGIO_structure.rst @@ -150,7 +150,7 @@ cgio_move_node :Modes: `- w m` :Description: - Moves the node indentified by :code:`id` below the parent node identified by :code:`pid` to below the new parent node identified by :code:`new_pid` in the database given by :code:`cgio_num`. A node by the same name as that that for id must not already exist under :code:`new_pid`. A node may only be moved if it and the parent nodes all reside in the same physical database. Returns 0 on success, else an error code. + Moves the node identified by :code:`id` below the parent node identified by :code:`pid` to below the new parent node identified by :code:`new_pid` in the database given by :code:`cgio_num`. A node by the same name as that that for id must not already exist under :code:`new_pid`. A node may only be moved if it and the parent nodes all reside in the same physical database. Returns 0 on success, else an error code. cgio_number_children @@ -220,7 +220,7 @@ cgio_children_names The size reserved for each name in :code:`child_names` is given by :code:`name_len`. The array :code:`child_names` should be dimensioned at least (:code:`name_len * max_ret`). Since node names are limited to a length of :code:`CGIO_MAX_NAME_LENGHT` (32), :code:`name_len` should be at least 32 to ensure the returned names are not truncated. - In C, an additional byte should be added to :code:`name_len` allow for the terminating :code:`'0'` for each name. If successfull, the function returns 0; the actual number of returned names is given by :code:`num_ret`, and the array of names in :code:`child_names`. In C, the names are '0'-terminated within each name field. In Fortran, any unused space is padded with blanks (space character). + In C, an additional byte should be added to :code:`name_len` allow for the terminating :code:`'0'` for each name. If successful, the function returns 0; the actual number of returned names is given by :code:`num_ret`, and the array of names in :code:`child_names`. In C, the names are '0'-terminated within each name field. In Fortran, any unused space is padded with blanks (space character). cgio_children_ids @@ -257,7 +257,7 @@ cgio_children_ids The starting index for the array of ids is given by :code:`start`, and the maximum ids to return by :code:`max_ret`. Both :code:`start` and :code:`max_ret` should be between 1 and :code:`num_child`, inclusively. The array :code:`child_ids` should be dimensioned at least (:code:`max_ret`). - If successfull, the function returns 0; the actual number of returned ids is given by :code:`num_ret`, and the array of identifiers in :code:`child_ids`. + If successful, the function returns 0; the actual number of returned ids is given by :code:`num_ret`, and the array of identifiers in :code:`child_ids`. .. last line diff --git a/CGNS-ReST-site/source/standard/CGNS_CGIO.rst b/CGNS-ReST-site/source/standard/CGNS_CGIO.rst index 7f629d87..0db0ebe6 100644 --- a/CGNS-ReST-site/source/standard/CGNS_CGIO.rst +++ b/CGNS-ReST-site/source/standard/CGNS_CGIO.rst @@ -153,7 +153,7 @@ Conventions and Implementations The implications of the assumed array structure convention can be quite subtle. The subroutines :code:`cgio_write_data` and :code:`cgio_read_data_type` assume the Fortran array structure in order to index the data. Again, unless the user is aware of the implications of this, it is possible to write an array on disk and later try to change a portion of the data and not change the correct numbers. As long as users are aware of how their data structure maps onto the database, there will not be any problems. -:return codes: The CGIO routines return an integer code indicating whether they were successfull or not. On success, :code:`0` (:code:`CGIO_ERR_NONE`) is returned. A non-zero return indicates an error. Return codes < 0 indicate an error at the CGIO level; codes > 0 indicate an error in the database manager. See Error Messages for a list of error codes and mesages. +:return codes: The CGIO routines return an integer code indicating whether they were successful or not. On success, :code:`0` (:code:`CGIO_ERR_NONE`) is returned. A non-zero return indicates an error. Return codes < 0 indicate an error at the CGIO level; codes > 0 indicate an error in the database manager. See Error Messages for a list of error codes and messages. Limits and Sizes diff --git a/CGNS-ReST-site/source/standard/CGNS_FMM.rst b/CGNS-ReST-site/source/standard/CGNS_FMM.rst index 8ee91e32..0f6980fc 100644 --- a/CGNS-ReST-site/source/standard/CGNS_FMM.rst +++ b/CGNS-ReST-site/source/standard/CGNS_FMM.rst @@ -171,7 +171,7 @@ The Child Table The database manager maintains a table recording the children of each node, which is adjusted when children are added or deleted -Children may be identified by their names and labels, and, thence, by their node IDs once these have been determined. There is no provision for the notion of order among children. In particular, the order of a list of children returned by the database manager may or may not have anything to do with the order in which they were inserted in the file. However, the order returned is consistent from call to call provided the file has not been closed and the node structure has not been modifed. +Children may be identified by their names and labels, and, thence, by their node IDs once these have been determined. There is no provision for the notion of order among children. In particular, the order of a list of children returned by the database manager may or may not have anything to do with the order in which they were inserted in the file. However, the order returned is consistent from call to call provided the file has not been closed and the node structure has not been modified. Note that there is no *parent* table; that is, a node has no direct knowledge of its parent. Since calling software must open the file from the root, it presumably cannot access a child without having first accessed the parent. It is the responsibility of the calling software to record the node ID of the parent if this information will be required. diff --git a/CGNS-ReST-site/source/standard/MLL/CGNS_MLL_general.rst b/CGNS-ReST-site/source/standard/MLL/CGNS_MLL_general.rst index ea51bd91..ef431b1e 100644 --- a/CGNS-ReST-site/source/standard/MLL/CGNS_MLL_general.rst +++ b/CGNS-ReST-site/source/standard/MLL/CGNS_MLL_general.rst @@ -53,7 +53,7 @@ Error Status ^^^^^^^^^^^^ All C functions return an integer value representing the error status. All Fortran functions have an additional parameter, :code:`ier`, which contains the value of the error status. -An error status different from zero implies that an error occured. The error message can be printed using the error handling functions of the CGNS library. +An error status different from zero implies that an error occurred. The error message can be printed using the error handling functions of the CGNS library. The error codes are coded in the C and Fortran include files *cgnslib.h* and *cgnslib_f.h*. @@ -140,7 +140,7 @@ Character Name of Typedefs ^^^^^^^^^^^^^^^^^^^^^^^^^^ The CGNS library defines character arrays which map the typedefs above to character strings. These are global arrays dimensioned to the size of each list of typedefs. -To retrieve a character string representation of a typedef, use the typedef value as an index to the appropiate character array. +To retrieve a character string representation of a typedef, use the typedef value as an index to the appropriate character array. For example, to retrieve the string ``"Meter"`` for the ``LengthUnits_t Meter`` typedef, use ``LengthUnitsName[Meter]``. Functions are available to retrieve these names without the need for direct global data access. These functions also do bounds checking on the input, and if out of range, will return the string ``""``. diff --git a/CGNS-ReST-site/source/standard/MLL/midlevel/fileops.html b/CGNS-ReST-site/source/standard/MLL/midlevel/fileops.html index a208008b..9b00aa71 100644 --- a/CGNS-ReST-site/source/standard/MLL/midlevel/fileops.html +++ b/CGNS-ReST-site/source/standard/MLL/midlevel/fileops.html @@ -513,7 +513,7 @@

Interfacing with CGIO

CGNS file index number. cgio_num - CGIO indentifier for the CGNS file. + CGIO identifier for the CGNS file. rootid Root node identifier for the CGNS file. diff --git a/CGNS-ReST-site/source/standard/MLL/midlevel/grid.html b/CGNS-ReST-site/source/standard/MLL/midlevel/grid.html index bf96afba..5204d69c 100644 --- a/CGNS-ReST-site/source/standard/MLL/midlevel/grid.html +++ b/CGNS-ReST-site/source/standard/MLL/midlevel/grid.html @@ -766,7 +766,7 @@

Element Connectivity

connectivity array Elements. The cg_section_partial_write function will create the element section data for the range start to end with the element data -intialized to 0. cg_poly_section_write and cg_poly_section_partial_write +initialized to 0. cg_poly_section_write and cg_poly_section_partial_write have a comparable behavior for MIXED, NGON_n, and NFACE_n. To add elements to the section, use cg_elements_partial_write or cg_poly_elements_partial_write diff --git a/CGNS-ReST-site/source/standard/MLL/midlevel/pcgns_library.html b/CGNS-ReST-site/source/standard/MLL/midlevel/pcgns_library.html index 770e2a29..94910b0c 100644 --- a/CGNS-ReST-site/source/standard/MLL/midlevel/pcgns_library.html +++ b/CGNS-ReST-site/source/standard/MLL/midlevel/pcgns_library.html @@ -130,7 +130,7 @@

Miscellaneous Routines

The MPI communicator to be used by the CGNS library.     mode   - Parallel input/ouput mode. + Parallel input/output mode. use_queue enable or disables queued output. @@ -353,7 +353,7 @@

Grid Coordinate Data

The above functions are used to read and write grid coordinate data by multiple processes in a parallel fashion. To write the data in parallel, first call cgp_coord_write to create an empty -data node. This call is indentical to +data node. This call is identical to cg_coord_write with coord_array set to NULL (no data written). The actual data is then written to the node in parallel using either @@ -488,7 +488,7 @@

Element Connectivity Data

The above functions are used to read and write element connectivity data by multiple processes in a parallel fashion. To write the element data in parallel, first call cgp_section_write to create an empty -data node. This call is indentical to +data node. This call is identical to cg_section_write with Elements set to NULL (no data written). The actual element data is then written to the node in parallel using @@ -628,7 +628,7 @@

Solution Data

The above functions are used to read and write solution arrays by multiple processes in a parallel fashion. To write the data in parallel, first call cgp_field_write to create an empty -data node. This call is indentical to +data node. This call is identical to cg_field_write with solution_array set to NULL (no data written). The actual data is then written to the node in parallel using either diff --git a/CGNS-ReST-site/source/standard/MLL/midlevel/timedep.html b/CGNS-ReST-site/source/standard/MLL/midlevel/timedep.html index 43479b57..5e34b009 100644 --- a/CGNS-ReST-site/source/standard/MLL/midlevel/timedep.html +++ b/CGNS-ReST-site/source/standard/MLL/midlevel/timedep.html @@ -422,7 +422,7 @@

Zone Grid Connectivity

The functions cg_zconn_read and cg_zconn_write -will implicity set the current ZoneGridConnectivity_t +will implicitly set the current ZoneGridConnectivity_t node, while cg_zconn_set explicitly sets it. The functions cg_nzconns and cg_zconn_get do not change it. diff --git a/CGNS-ReST-site/source/standard/SIDS/CGNS_SIDS.rst b/CGNS-ReST-site/source/standard/SIDS/CGNS_SIDS.rst index 67454ef0..de64b762 100644 --- a/CGNS-ReST-site/source/standard/SIDS/CGNS_SIDS.rst +++ b/CGNS-ReST-site/source/standard/SIDS/CGNS_SIDS.rst @@ -10,7 +10,7 @@ CGNS/SIDS - Standard Interface Data Structures ============================================== -.. SIDS SECTION NUMERING +.. SIDS SECTION NUMBERING - numbering is not usual in HTML, so we have to force ReST to store sections numbers. You SHOULD NOT change order, or obviously numbers will change :| diff --git a/CGNS-ReST-site/source/standard/SIDS/boundary.rst b/CGNS-ReST-site/source/standard/SIDS/boundary.rst index e6a56bcf..09e6d4fa 100644 --- a/CGNS-ReST-site/source/standard/SIDS/boundary.rst +++ b/CGNS-ReST-site/source/standard/SIDS/boundary.rst @@ -107,7 +107,7 @@ If the boundary conditions contain dimensional data, :sidsref:`DimensionalUnits` If present, these three entities take precedence over all corresponding entities at higher levels of the hierarchy, following the standard :ref:`precedence rules `. Reference-state data is useful for situations where boundary-condition data is not provided, and flow solvers are free to enforce any appropriate boundary condition equations. -The presense of :sidsref:`ReferenceState` at this level or below specifies the appropriate flow conditions from which the flow solver should extract its boundary-condition data. +The presence of :sidsref:`ReferenceState` at this level or below specifies the appropriate flow conditions from which the flow solver should extract its boundary-condition data. For example, when computing an external flowfield around an airplane, an engine nozzle exit is often simulated by imposing a stagnation pressure boundary condition (or some other stagnation quantity) different from freestream. The nozzle-exit stagnation quantities could be specified in an instance of :sidskey:`ReferenceState` at this level or below in lieu of providing explicit Dirichlet or Neumann data. (See :ref:`Boundary Condition Specification Data. `) diff --git a/CGNS-ReST-site/source/standard/SIDS/convention.rst b/CGNS-ReST-site/source/standard/SIDS/convention.rst index 937d90c6..cd23898f 100644 --- a/CGNS-ReST-site/source/standard/SIDS/convention.rst +++ b/CGNS-ReST-site/source/standard/SIDS/convention.rst @@ -594,7 +594,7 @@ Quartic Elements Pyramid Elements """""""""""""""" -CGNS supports nine types of pyramid elements, PYRA_5, PYRA_13, PYRA_14, PYRA_21, PYRA_29, PYRA_30, PYRA_P4_29, PYRA_50, and PYRA_55. PYRA_5 elements are composed of five nodes located at the five geometric corners of the pyramid. In addition, PYRA_13 and PYRA_14 elements have a node at the middle of each of the eight edges; PYRA_14 adds a node at the middle of the quadrilateral face. The cubic forms of pyramid elements, PYRA_21, PYRA_29, and PYRA_30 contain two interior nodes along each edge, eight interior face nodes in the case of PYRA_29 and PYRA_30, and an additonal interior volume node for PYRA_30. The quartic forms of pyramid elements, PYRA_P4_29, PYRA_50, and PYRA_55 contain three interior nodes along each edge, 21 interior face nodes in the case of PYRA_50, and 21 interior face nodes and five additonal interior volume nodes for PYRA_55. +CGNS supports nine types of pyramid elements, PYRA_5, PYRA_13, PYRA_14, PYRA_21, PYRA_29, PYRA_30, PYRA_P4_29, PYRA_50, and PYRA_55. PYRA_5 elements are composed of five nodes located at the five geometric corners of the pyramid. In addition, PYRA_13 and PYRA_14 elements have a node at the middle of each of the eight edges; PYRA_14 adds a node at the middle of the quadrilateral face. The cubic forms of pyramid elements, PYRA_21, PYRA_29, and PYRA_30 contain two interior nodes along each edge, eight interior face nodes in the case of PYRA_29 and PYRA_30, and an additional interior volume node for PYRA_30. The quartic forms of pyramid elements, PYRA_P4_29, PYRA_50, and PYRA_55 contain three interior nodes along each edge, 21 interior face nodes in the case of PYRA_50, and 21 interior face nodes and five additional interior volume nodes for PYRA_55. Linear and Quadratic Elements +++++++++++++++++++++++++++++ @@ -699,7 +699,7 @@ Quartic Elements Pentahedral Elements """""""""""""""""""" -CGNS supports nine types of pentahedral elements, PENTA_6, PENTA_15, PENTA_18, PENTA_24, PENTA_38, PENTA_40, PENTA_33, PENTA_66, and PENTA_75. PENTA_6 elements are composed of six nodes located at the six geometric corners of the pentahedron. In addition, PENTA_15 and PENTA_18 elements have a node at the middle of each of the nine edges; PENTA_18 adds a node at the middle of each of the three quadrilateral faces. The cubic forms of the pentahedral elements, PENTA_24, PENTA_38, and PENTA_40 contain two interior nodes along each edge, fourteen interior face nodes in the case of PENTA_38 and PENTA_40, and an additonal two interior volume nodes for PENTA_40. The quartic forms of the pentahedral elements, PENTA_33, PENTA_66, and PENTA_75 contain three interior nodes along each edge, 33 interior face nodes in the case of PENTA_66, and 33 interior face nodes and an additonal nine interior volume nodes for PENTA_75. +CGNS supports nine types of pentahedral elements, PENTA_6, PENTA_15, PENTA_18, PENTA_24, PENTA_38, PENTA_40, PENTA_33, PENTA_66, and PENTA_75. PENTA_6 elements are composed of six nodes located at the six geometric corners of the pentahedron. In addition, PENTA_15 and PENTA_18 elements have a node at the middle of each of the nine edges; PENTA_18 adds a node at the middle of each of the three quadrilateral faces. The cubic forms of the pentahedral elements, PENTA_24, PENTA_38, and PENTA_40 contain two interior nodes along each edge, fourteen interior face nodes in the case of PENTA_38 and PENTA_40, and an additional two interior volume nodes for PENTA_40. The quartic forms of the pentahedral elements, PENTA_33, PENTA_66, and PENTA_75 contain three interior nodes along each edge, 33 interior face nodes in the case of PENTA_66, and 33 interior face nodes and an additional nine interior volume nodes for PENTA_75. Linear and Quadratic Elements +++++++++++++++++++++++++++++ @@ -806,7 +806,7 @@ Quartic Elements Hexahedral Elements """"""""""""""""""" -CGNS supports nine types of hexahedral elements, HEXA_8, HEXA_20, HEXA_27, HEXA_32, HEXA_56, HEXA_64, HEXA_44, HEXA_98, and HEXA_125. HEXA_8 elements are composed of eight nodes located at the eight geometric corners of the hexahedron. In addition, HEXA_20 and HEXA_27 elements have a node at the middle of each of the twelve edges; HEXA_27 adds a node at the middle of each of the six faces, and one at the cell center. The cubic forms of the hexahedral elements, HEXA_32, HEXA_56, and HEXA_64 contain two interior nodes along each edge, 24 interior face nodes in the case of HEXA_56 and HEXA_64, and an additonal eight interior volume nodes for HEXA_64. The quartic forms of the hexahedral elements, HEXA_44, HEXA_98, and HEXA_125 contain three interior nodes along each edge, 54 interior face nodes in the case of HEXA_98, and 54 interior face nodes and an additonal 27 interior volume nodes for HEXA_125. +CGNS supports nine types of hexahedral elements, HEXA_8, HEXA_20, HEXA_27, HEXA_32, HEXA_56, HEXA_64, HEXA_44, HEXA_98, and HEXA_125. HEXA_8 elements are composed of eight nodes located at the eight geometric corners of the hexahedron. In addition, HEXA_20 and HEXA_27 elements have a node at the middle of each of the twelve edges; HEXA_27 adds a node at the middle of each of the six faces, and one at the cell center. The cubic forms of the hexahedral elements, HEXA_32, HEXA_56, and HEXA_64 contain two interior nodes along each edge, 24 interior face nodes in the case of HEXA_56 and HEXA_64, and an additional eight interior volume nodes for HEXA_64. The quartic forms of the hexahedral elements, HEXA_44, HEXA_98, and HEXA_125 contain three interior nodes along each edge, 54 interior face nodes in the case of HEXA_98, and 54 interior face nodes and an additional 27 interior volume nodes for HEXA_125. Linear and Quadratic Elements +++++++++++++++++++++++++++++ diff --git a/CGNS-ReST-site/source/standard/SIDS/grid.rst b/CGNS-ReST-site/source/standard/SIDS/grid.rst index ef5f3f3a..91a02822 100644 --- a/CGNS-ReST-site/source/standard/SIDS/grid.rst +++ b/CGNS-ReST-site/source/standard/SIDS/grid.rst @@ -716,7 +716,7 @@ Flow Solution Structure Definition: :sidskey:`FlowSolution_t` The flow solution data is stored in the list of :sidsref:`DataArray_t` entities; each :sidskey:`DataArray_t` structure entity may contain a single component of the solution vector. Standardized data-name identifiers for the flow-solution quantities are described in the section :ref:`Conventions for Data-Name Identifiers`. The field :sidsref:`GridLocation` specifies the location of the solution data with respect to the grid; if absent, the data is assumed to coincide with grid vertices (i.e., :sidskey:`GridLocation = Vertex`). All data within a given instance of :sidskey:`FlowSolution_t` must reside at the same grid location. -For structured grids, the value of :sidskey:`GridLocation` alone specifies the location and indexing of the flow solution data. Vertices are explicity indexed. Cell centers and face centers are indexed using the minimum of the connecting vertex indices, as described in the section :ref:`Structured Grid Notation and Indexing Conventions `. +For structured grids, the value of :sidskey:`GridLocation` alone specifies the location and indexing of the flow solution data. Vertices are explicitly indexed. Cell centers and face centers are indexed using the minimum of the connecting vertex indices, as described in the section :ref:`Structured Grid Notation and Indexing Conventions `. For unstructured grids, the value of :sidskey:`GridLocation` alone specifies location and indexing of flow solution data only for vertex and cell-centered data. The reason for this is that element-based grid connectivity provided in the :sidsref:`Elements_t` data structures explicitly indexes only vertices and cells. For data stored at alternate grid locations (e.g., edges), additional connectivity information is needed. This is provided by the optional fields :sidskey:`PointRange` and :sidskey:`PointList`; these refer to vertices, edges, faces or cell centers, depending on the values of :sidskey:`CellDimension` and :sidskey:`GridLocation`. The following table shows these relations. The :sidskey:`NODE` element type should not be used in place of the vertex. A vertex :sidskey:`GridLocation` should use the :sidskey:`GridLocation = Vertex` pattern, which implies an indexing on the grid coordinates arrays and not a :sidskey:`NODE Elements_t` array. diff --git a/CGNS-ReST-site/source/standard/SIDS/hierarchy.rst b/CGNS-ReST-site/source/standard/SIDS/hierarchy.rst index 9c15a5ed..ca552d1b 100644 --- a/CGNS-ReST-site/source/standard/SIDS/hierarchy.rst +++ b/CGNS-ReST-site/source/standard/SIDS/hierarchy.rst @@ -18,7 +18,7 @@ Historically, the version number was used to describe the version of the :ref:`M CGNS Entry Level Structure Definition: ``CGNSBase_t`` ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The highest level structure in a CGNS database is :sidskey:`CGNSBase_t`. This top level entity is designed to be self-contained, a complete CFD computation can be archived and reproduced using the data defined in the CGNSBase. However a CGNS tree can contain more than one base, these can be related to the same CFD case or not. The behavior of a multi-base CGNS tree is application dependant, even if inter-base relationships are authorized in three cases: +The highest level structure in a CGNS database is :sidskey:`CGNSBase_t`. This top level entity is designed to be self-contained, a complete CFD computation can be archived and reproduced using the data defined in the CGNSBase. However a CGNS tree can contain more than one base, these can be related to the same CFD case or not. The behavior of a multi-base CGNS tree is application dependent, even if inter-base relationships are authorized in three cases: * A reference to another base's zone name (including its sub-nodes' names) as defined in the multi-zone connectivities (see :ref:`Multizone Interface Connectivity ` and time-dependant pointers :ref:`Time-Dependent Flow `); * A reference to another base's family name (see :ref:`Family Data Structure Definition `: :sidsref:`Family_t`) as as :sidskey:`FamilyName_t` data; diff --git a/CGNS-ReST-site/source/standard/SIDS/misc.rst b/CGNS-ReST-site/source/standard/SIDS/misc.rst index 66648e4b..041c926b 100644 --- a/CGNS-ReST-site/source/standard/SIDS/misc.rst +++ b/CGNS-ReST-site/source/standard/SIDS/misc.rst @@ -228,7 +228,7 @@ All data contained within this structure must be defined at the same grid locati The arrays of discrete data are stored in the list of :sidskey:`DataArray_t` entities. The field :sidskey:`GridLocation` specifies the location of the data with respect to the grid; if absent, the data is assumed to coincide with grid vertices (i.e., :sidskey:`GridLocation = Vertex`). All data within a given instance of :sidskey:`DiscreteData_t` must reside at the same grid location. -For structured grids, the value of :sidskey:`GridLocation` alone specifies the location and indexing of the discrete. Vertices are explicity indexed. Cell centers and face centers are indexed using the minimum of the connecting vertex indices, as described in the section :ref:`Structured Grid Notation and Indexing Conventions `. +For structured grids, the value of :sidskey:`GridLocation` alone specifies the location and indexing of the discrete. Vertices are explicitly indexed. Cell centers and face centers are indexed using the minimum of the connecting vertex indices, as described in the section :ref:`Structured Grid Notation and Indexing Conventions `. For unstructured grids, the value of :sidskey:`GridLocation` alone specifies location and indexing of discrete data only for vertex and cell-centered data. The reason for this is that element-based grid connectivity provided in the :sidskey:`Elements_t` data structures explicitly indexes only vertices and cells. For data stored at alternate grid locations (e.g., edges), additional connectivity information is needed. This is provided by the optional fields :sidskey:`PointRange` and :sidskey:`PointList`; these refer to vertices, edges, faces or cell centers, depending on the values of :sidskey:`CellDimension` and :sidskey:`GridLocation`. diff --git a/CGNS-ReST-site/source/standard/SIDS/time.rst b/CGNS-ReST-site/source/standard/SIDS/time.rst index 21de7024..fb915e56 100644 --- a/CGNS-ReST-site/source/standard/SIDS/time.rst +++ b/CGNS-ReST-site/source/standard/SIDS/time.rst @@ -4,7 +4,7 @@ Time-Dependent Flow =================== -This section describes structure types intended primarily for time-dependent flows. Data structures are presented for storing time-dependent or iterative data, and for recording rigid and arbitary grid motion. The section concludes with several examples. +This section describes structure types intended primarily for time-dependent flows. Data structures are presented for storing time-dependent or iterative data, and for recording rigid and arbitrary grid motion. The section concludes with several examples. Iterative Data Structure Definitions ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/CGNS-ReST-site/source/standard/hdf5.rst b/CGNS-ReST-site/source/standard/hdf5.rst index 55848b8f..ba80d53b 100644 --- a/CGNS-ReST-site/source/standard/hdf5.rst +++ b/CGNS-ReST-site/source/standard/hdf5.rst @@ -15,7 +15,7 @@ Implementation Summary The purpose of the current document is to describe the way in which CFD data is to be represented in an HDF5 data tree. To do this, it is necessary to first describe the HDF5 data structure itself in some detail. Therefore, a conceptual summary of HDF5 is given here in order to make the current document relatively independent, and to allow the reader to focus on those aspects of HDF5 which are essential to understanding the file mapping. -Any HDF5 file with a conformant mapping is *CGNS/HDF5* compliant. The mapping has been made using a per-node basis. Instead of having a new mapping dedicated to HDF5, we have made a mapping from the ADF nodes to a set of HDF5 groups. While this is not an optimal mapping, the use of such an HDF5 node allows us to re-use the ADF API without change. +Any HDF5 file with a conformant mapping is *CGNS/HDF5* compliant. The mapping has been made using a per-node basis. Instead of having a new mapping dedicated to HDF5, we have made a mapping from the ADF nodes to a set of HDF5 groups. While this is not an optimal mapping, the use of such an HDF5 node allows us to reuse the ADF API without change. The `HDF5 documentation `_ should be used as the authoritative references to resolve any issues not covered by this summary. @@ -32,11 +32,11 @@ Refer to the `HDF5 web site `_ for fur Dedicated HDF5 Structures ^^^^^^^^^^^^^^^^^^^^^^^^^ -The *CGNS node* is an HDF5 group. It contains attributes, an optional dataset and optional child groups. This structure is required and can be extended by other implementors as long as the following requirements are fullfilled. +The *CGNS node* is an HDF5 group. It contains attributes, an optional dataset and optional child groups. This structure is required and can be extended by other implementers as long as the following requirements are fulfilled. In a CGNS tree, most of the nodes are *normal* nodes. These nodes can optionally contain data and have other nodes as children. -There are special nodes, such as the root node and the nodes managing the links. These special link structures use the HDF5 mount system. It is not necessary for either the MLL or SLL users to understand the HDF5 mount system, but it should be understood by SLL implementors. +There are special nodes, such as the root node and the nodes managing the links. These special link structures use the HDF5 mount system. It is not necessary for either the MLL or SLL users to understand the HDF5 mount system, but it should be understood by SLL implementers. The CGNS Node Mapping ~~~~~~~~~~~~~~~~~~~~~ @@ -81,7 +81,7 @@ The name of the root node is ``[HDF5 MotherNode]``, its label is ``[Root Node of The node hosting the link entries is a special node named ``[ mount]`` without attributes nor data. This group should be a child of the root node, its absolute path is ``[/ mount]``. -The group ``[ mount]`` contains one group for each mounted file refered to by a link. +The group ``[ mount]`` contains one group for each mounted file referred to by a link. Each entry has the attributes described in the table below. The link node itself is a group with the special name ``[ link]``. This implementation is discussed further in the section describing the :ref:`link mechanism `. @@ -271,7 +271,7 @@ Although HDF5 provides a number of types, in CGNS the only types used are :code: The specification of data types within the File Mapping allows for the probability that files written under different circumstances may differ in precision. The issue is complicated by the ability of HDF5 to sense the capabilities of the platform on which it is running and interpret or record data accordingly. The general rule is that, although the user of HDF5 can specify the precision in which it is desired to read or write the data, HDF5 knows both the precision available at the source and the precision acceptable to the destination and will mitigate accordingly. -Thus to specify the precison of real data as :code:`R4`, for example, has no meaning unless both :code:`R4` and :code:`R8` are available. +Thus to specify the precision of real data as :code:`R4`, for example, has no meaning unless both :code:`R4` and :code:`R8` are available. Therefore, the generic specification ``"DataType"`` is used to allow for all possibilities. For all integer data specified by the SIDS, :code:`I4` provides sufficient precision. @@ -302,7 +302,7 @@ The Child Table is completely controlled by HDF5, and thus its role is exactly t In addition to the meaning of attributes of individual HDF5 nodes, the File Mapping specifies the relations between nodes in a CGNS database. Consequently, the File Mapping determines what kinds of nodes will lie in the child table. -It is important to reemphasize that HDF5 provides no notion of order among children. This means children can be identified only by their names, labels and system-provided node IDs. In particular, the order of a list of children returned by HDF5 has nothing to do with the order in which they were inserted in the file. However, the order returned is consistent from call to call provided the file has not been closed and the node structure has not been modifed. +It is important to reemphasize that HDF5 provides no notion of order among children. This means children can be identified only by their names, labels and system-provided node IDs. In particular, the order of a list of children returned by HDF5 has nothing to do with the order in which they were inserted in the file. However, the order returned is consistent from call to call provided the file has not been closed and the node structure has not been modified. .. _HDF5Cardinality: diff --git a/CGNS-ReST-site/source/standard/python.rst b/CGNS-ReST-site/source/standard/python.rst index b8361b3d..97a58362 100644 --- a/CGNS-ReST-site/source/standard/python.rst +++ b/CGNS-ReST-site/source/standard/python.rst @@ -6,11 +6,11 @@ CGNS/Python - A Python implementation ===================================== -The CGNS/Python mapping defines a tree structure composed of nodes implemented for the `Python programming langage `_. +The CGNS/Python mapping defines a tree structure composed of nodes implemented for the `Python programming language `_. A special links structure is also defined for a correct mapping of the management of files on the disk. -The mapping presented here is **not** a library, it is the lowest possible correspondance between a :ref:`CGNS/SIDS` structure and a Python representation. +The mapping presented here is **not** a library, it is the lowest possible correspondence between a :ref:`CGNS/SIDS` structure and a Python representation. This specification is public and can be used as the basis for Python based CGNS application interoperability. -Python is an interpreted langage and it has a textual representation of its objects, this representation can be used for CGNS/Python trees as well. +Python is an interpreted language and it has a textual representation of its objects, this representation can be used for CGNS/Python trees as well. The python documentation is not up-to-date (v3.1.2). diff --git a/CGNS-ReST-site/source/standard/reference.rst b/CGNS-ReST-site/source/standard/reference.rst index d58229a1..8b48ce89 100644 --- a/CGNS-ReST-site/source/standard/reference.rst +++ b/CGNS-ReST-site/source/standard/reference.rst @@ -6,7 +6,7 @@ Standardization bodies .. _AIAAPractice: -The AIAA recommanded practice +The AIAA recommended practice ----------------------------- As part of its role as a sub-committee of diff --git a/CGNSFiles.html b/CGNSFiles.html index 690f075d..d69d53a9 100644 --- a/CGNSFiles.html +++ b/CGNSFiles.html @@ -177,7 +177,7 @@

-Multiblock stuctured grids for a business jet, a wing/body, and a wing/body/nacelle/pylon +Multiblock structured grids for a business jet, a wing/body, and a wing/body/nacelle/pylon configuration are available from Stanford. Stanford CGNS test files (link to external site) diff --git a/CGNS_docs_current/adf/sampleFortran.html b/CGNS_docs_current/adf/sampleFortran.html index 8b42910a..d6f6e5ea 100644 --- a/CGNS_docs_current/adf/sampleFortran.html +++ b/CGNS_docs_current/adf/sampleFortran.html @@ -212,7 +212,7 @@

Sample Fortran Program

PRINT *,' DATA:' WRITE(*,200)(ID(I),I=1,6) C - C 4.) N13 THROUTH L2 + C 4.) N13 THROUGH L2 C CALL ADFGNID(RID,'N3/N11/L2',CID,IERR) CALL ADFGLB(CID,TSTLBL,IERR) diff --git a/CGNS_docs_current/adf/subs_misc.html b/CGNS_docs_current/adf/subs_misc.html index 6bb1d6f7..78145d8d 100644 --- a/CGNS_docs_current/adf/subs_misc.html +++ b/CGNS_docs_current/adf/subs_misc.html @@ -277,7 +277,7 @@

Set the Error State Flag

PRINT *,' *** ON ERROR CONTINUE' CALL ADFGNAM(CID3,NODNAM,IERR) CALL ADFERR(IERR,MESS) - PRINT *,' ADF ERROR OCURRED, MESSAGE: ',MESS + PRINT *,' ADF ERROR OCCURRED, MESSAGE: ',MESS PRINT *,' ' C C *** SET ABORT ON ERROR FLAG @@ -301,7 +301,7 @@

Set the Error State Flag

    DEFAULT ERROR STATE =            0
      *** ON ERROR CONTINUE
-         ADF ERROR OCURRED, MESSAGE:
+         ADF ERROR OCCURRED, MESSAGE:
    ADF 10: ADF file index out of legal range.
 
      *** ABORT ON ERROR SET
diff --git a/CGNS_docs_current/adf/summary.html b/CGNS_docs_current/adf/summary.html
index 1b9b9be2..63d525ea 100644
--- a/CGNS_docs_current/adf/summary.html
+++ b/CGNS_docs_current/adf/summary.html
@@ -301,7 +301,7 @@ 
The Child Table

 children returned by ADF has nothing to do with the order in which they
 were inserted in the file. However, the order returned is consistent
 from call to call provided the file has not been closed and the node
-structure has not been modifed.
+structure has not been modified.
 
 

 Note that there is no parent table; that is, a node has no direct
diff --git a/CGNS_docs_current/cgio/database.html b/CGNS_docs_current/cgio/database.html
index f34c9b92..a1632307 100644
--- a/CGNS_docs_current/cgio/database.html
+++ b/CGNS_docs_current/cgio/database.html
@@ -121,7 +121,7 @@ 
Database-Level Routines

        CGIO_MODE_MODIFY.
 
    cgio_num
-   Indentifier for the open database file.
+   Identifier for the open database file.
 
    rootid
    Node identifier for the root node of the database.
@@ -137,7 +137,7 @@ 
Function Descriptions

 
 
cgio_is_supported
 
Determines if the database type given by file_type is supported
-    by the library. Retuns 0 if supported, else CGIO_ERR_FILE_TYPE
+    by the library. Returns 0 if supported, else CGIO_ERR_FILE_TYPE
     if not. CGIO_FILE_ADF is always supported;
     CGIO_FILE_HDF5 is supported if the library was built with HDF5;
     and CGIO_FILE_ADF2 is supported when built in 32-bit mode.
@@ -153,7 +153,7 @@ 
Function Descriptions

 
 

 
 
cgio_open_file
-
Opens a database file of the specified type and mode. If successfull,
+
Opens a database file of the specified type and mode. If successful,
     returns 0, and the database identifier in cgio_num, otherwise
     returns an error code. The database identifier is used to access the
     database in subsequent function calls.
@@ -172,7 +172,7 @@ 
Function Descriptions

     type should be used, otherwise the specified database type will be opened.
     When opening in read or modify mode, CGIO_FILE_NONE indicates that
     any database type is acceptable, otherwise if the database type does
-    not match that given by file_type an error will be retuned.
+    not match that given by file_type an error will be returned.
 
 
 

 
@@ -184,7 +184,7 @@ 
Function Descriptions

 
 
cgio_get_file_type
 
Gets the type of the database given by cgio_num.
-    Returns 0 and the type in file_type if successfull,
+    Returns 0 and the type in file_type if successful,
     else an error code.
 
 
 

@@ -192,7 +192,7 @@ 
Function Descriptions

 
cgio_get_root_id
 
Gets the unique node identifier for the root node in the database given
     by cgio_num. Returns 0 and the identifier in rootid
-    if successfull, else an error code.
+    if successful, else an error code.
 
 
 
diff --git a/CGNS_docs_current/cgio/examples.html b/CGNS_docs_current/cgio/examples.html
index bc0319bd..c742318d 100644
--- a/CGNS_docs_current/cgio/examples.html
+++ b/CGNS_docs_current/cgio/examples.html
@@ -216,7 +216,7 @@ 
Fortran Example

       PRINT *,'   DATA:'
       WRITE(*,200)(ID(I),I=1,6)
 C
-C     4.) N13 THROUTH L2
+C     4.) N13 THROUGH L2
 C
       CALL CGIO_GET_NODE_ID_F(ICGIO,RID,'N3/N11/L2',CID,IERR)
       CALL CGIO_GET_LABEL_F(ICGIO,CID,TSTLBL,IERR)
diff --git a/CGNS_docs_current/cgio/library.html b/CGNS_docs_current/cgio/library.html
index 2e0a4a91..bfa97380 100644
--- a/CGNS_docs_current/cgio/library.html
+++ b/CGNS_docs_current/cgio/library.html
@@ -493,12 +493,12 @@ 
Conventions and Implementations

 
    return codes
    The CGIO routines return an integer code indicating whether they
-       were successfull or not. On success, 0 (CGIO_ERR_NONE) is
+       were successful or not. On success, 0 (CGIO_ERR_NONE) is
        returned. A non-zero return indicates an error. Return codes < 0
        indicate an error at the CGIO level; codes > 0 indicate an
        error in the database manager. See
        Error Messages for a list of
-       error codes and mesages.
+       error codes and messages.
 
 
 
diff --git a/CGNS_docs_current/cgio/links.html b/CGNS_docs_current/cgio/links.html
index a808d50e..85ea7e0f 100644
--- a/CGNS_docs_current/cgio/links.html
+++ b/CGNS_docs_current/cgio/links.html
@@ -92,7 +92,7 @@ 
Link Management Routines

 
+current file for CGNS compatibility.
diff --git a/CGNS_docs_current/cgnstools/tools.html b/CGNS_docs_current/cgnstools/tools.html
index 08141ab5..27316b1a 100644
--- a/CGNS_docs_current/cgnstools/tools.html
+++ b/CGNS_docs_current/cgnstools/tools.html
@@ -148,7 +148,7 @@ 
cgnscompress

 file is opened in modify mode and nodes deleted or rewritten. In previous
 versions of the library, the entire file was automatically rewritten
 in this case, thus unused space did not occur. In the current version
-this is no longer done since problems may occur when doing paralllel I/O.
+this is no longer done since problems may occur when doing parallel I/O.
 
Command Line

diff --git a/CGNS_docs_current/cgnstools/utilities/convert.html b/CGNS_docs_current/cgnstools/utilities/convert.html
index 1b427a3a..2fd8410e 100644
--- a/CGNS_docs_current/cgnstools/utilities/convert.html
+++ b/CGNS_docs_current/cgnstools/utilities/convert.html
@@ -6,7 +6,7 @@
 
-Data Conversion Utiltities
+Data Conversion Utilities
diff --git a/CGNS_docs_current/cgnstools/utilities/export.html b/CGNS_docs_current/cgnstools/utilities/export.html
index 6404871e..fed79b42 100644
--- a/CGNS_docs_current/cgnstools/utilities/export.html
+++ b/CGNS_docs_current/cgnstools/utilities/export.html
@@ -412,8 +412,8 @@ 
Command Line
The input CGNS file, CGNSfile, is required. If the VTK output
 directory, VTKdir, is given, the VTK files are written to that
 directory, otherwise the current directory is used. Each zone,
-and element set (if option -e is selected), whill be written
-to a seperate VTK file in that directory.
+and element set (if option -e is selected), will be written
+to a separate VTK file in that directory.
 The command line aptions are: 
 

 
diff --git a/CGNS_docs_current/cgnstools/utilities/import.html b/CGNS_docs_current/cgnstools/utilities/import.html
index f4060263..c412eb97 100644
--- a/CGNS_docs_current/cgnstools/utilities/import.html
+++ b/CGNS_docs_current/cgnstools/utilities/import.html
@@ -183,7 +183,7 @@ 
CGNSview Interface
This allows interactive selection of the input and output
 files and options. The Accept button will then construct
 the command line and run plot3d_to_cgns. If the
-import is successfull, CGNSview will read and display the CGNS
+import is successful, CGNSview will read and display the CGNS
 file.

@@ -249,7 +249,7 @@ 
CGNSview Interface
This allows interactive selection of the input and output
 files and options. The Accept button will then construct
 the command line and run tecplot_to_cgns. If the
-import is successfull, CGNSview will read and display the CGNS
+import is successful, CGNSview will read and display the CGNS
 file.

@@ -318,7 +318,7 @@ 
CGNSview Interface
This allows interactive selection of the input and output
 files and options. The Accept button will then construct
 the command line and run patran_to_cgns. If the
-import is successfull, CGNSview will read and display the CGNS
+import is successful, CGNSview will read and display the CGNS
 file.

@@ -326,7 +326,7 @@ 
CGNSview Interface
VGRID
Converts VGRID .cogsg, .mapbc, and .bc files to an unstructured CGNS file.
-An option, -c, is provided to combine patchs with the same name
+An option, -c, is provided to combine patches with the same name
 and boundary condition.
 
 
Command Line

@@ -351,7 +351,7 @@ 
Command Line

-        
+        

 
   
    cgio_num  
-   Indentifier for the open database file.
+   Identifier for the open database file.
 

    id
    Node identifier.
@@ -131,8 +131,8 @@ 
Function Descriptions

 
 
 
cgio_is_link
-
Determines if the node indentified by id in the database given by
-    cgio_num is a link or not. The function returns 0 if successfull,
+
Determines if the node identified by id in the database given by
+    cgio_num is a link or not. The function returns 0 if successful,
     else an error code. If this node is a link, then the total length of the
     linked-to file and node information in returned in link_len.
     If the node is not a link, link_len will be 0.
@@ -156,14 +156,14 @@ 
Function Descriptions

     the pathname to the linked-to node by name_in_file. If this is an
     internal link (link to a node in the same database), then filename
     should be defined as NULL or an empty string. The function
-    returns 0 and the indentifier of the new node in id on success,
+    returns 0 and the identifier of the new node in id on success,
     otherwise an error code is returned.
 
 
 

 
 
cgio_get_link
 
Gets the link information for the node identified by id in the
-    database given by cgio_num. If successfull, the function returns
+    database given by cgio_num. If successful, the function returns
     0 and the linked-to file name in filename and the node pathname
     in name_in_file. These strings are '0'-terminated, and thus
     should be dimensioned at least (file_len + 1) and
diff --git a/CGNS_docs_current/cgio/misc.html b/CGNS_docs_current/cgio/misc.html
index a77bc4b4..79132e55 100644
--- a/CGNS_docs_current/cgio/misc.html
+++ b/CGNS_docs_current/cgio/misc.html
@@ -110,7 +110,7 @@ 
Function Descriptions

 
 
cgio_flush_to_disk
 
Forces any buffered data in the database manager to be written
-    to disk. Returns 0 if successfull, else an error code.
+    to disk. Returns 0 if successful, else an error code.
 
 
 

 
@@ -120,7 +120,7 @@ 
Function Descriptions

     CGIO_MAX_VERSION_LENGTH (32). In C, version should
     be dimensioned at least 33 in the calling routine to allow for the
     terminating '0'.
-    The function returns 0 if successfull, else an error code.
+    The function returns 0 if successful, else an error code.
 
 
 

 
@@ -133,7 +133,7 @@ 
Function Descriptions

     which are of maximum length CGIO_MAX_DATE_LENGTH (32).
     In C, these should be dimensioned at least 33 in the calling routine
     to allow for the terminating '0'.
-    The function returns 0 if successfull, else an error code.
+    The function returns 0 if successful, else an error code.
 
 
 
diff --git a/CGNS_docs_current/cgio/node.html b/CGNS_docs_current/cgio/node.html
index 3454cd68..d8ca9ae6 100644
--- a/CGNS_docs_current/cgio/node.html
+++ b/CGNS_docs_current/cgio/node.html
@@ -165,7 +165,7 @@ 
Function Descriptions

     in the database given by cgio_num. if pathname starts
     with '/', then it is taken as an absolute path and is located based
     on the root id of the database, otherwise it is taken to be a relative
-    path from the parent node identifed by pid. The function returns
+    path from the parent node identified by pid. The function returns
     0 and the node identifier in id on success, else an error code.
 
 
 

@@ -180,7 +180,7 @@ 
Function Descriptions

 
 

 
 
cgio_set_name
-
Sets (renames) the node identied by id in the database given by
+
Sets (renames) the node identified by id in the database given by
     cgio_num to name. The parent node identifier is given
     by pid. There must not already exist a child node of pid
     with that name. The function return 0 on success, else an error code.
@@ -197,7 +197,7 @@ 
Function Descriptions

 
 

 
 
cgio_set_label
-
Sets the label of the node identied by id in the database given by
+
Sets the label of the node identified by id in the database given by
     cgio_num to label. The function return 0 on success,
     else an error code.
 
diff --git a/CGNS_docs_current/cgio/structure.html b/CGNS_docs_current/cgio/structure.html
index ffaaf677..6fd7cf59 100644
--- a/CGNS_docs_current/cgio/structure.html
+++ b/CGNS_docs_current/cgio/structure.html
@@ -237,7 +237,7 @@ 
Function Descriptions

 
 

 
 
cgio_move_node
-
Moves the node indentified by id below the parent node identified
+
Moves the node identified by id below the parent node identified
     by pid to below the new parent node identified by new_pid
     in the database given by cgio_num. A node by the same name as
     that that for id must not already exist under new_pid.
@@ -263,9 +263,9 @@ 
Function Descriptions

     The array child_names should be dimensioned at least
     (name_len * max_ret). Since node names are limited to a length
     of CGIO_MAX_NAME_LENGHT (32), name_len should be at
-    least 32 to ensure the returned names are mot truncated. In C, an
+    least 32 to ensure the returned names are not truncated. In C, an
     additional byte should be added to name_len allow for the
-    terminating '0' for each name. If successfull, the function returns 0;
+    terminating '0' for each name. If successful, the function returns 0;
     the actual number of returned names is given by num_ret,
     and the array of names in child_names. In C, the names are
     '0'-terminated within each name field. In Fortran, any unused space
@@ -280,7 +280,7 @@ 
Function Descriptions

     and the maximum ids to return by max_ret. Both start
     and max_ret should be between 1 and num_child, inclusively.
     The array child_ids should be dimensioned at least
-    (max_ret). If successfull, the function returns 0; the
+    (max_ret). If successful, the function returns 0; the
     actual number of returned ids is given by num_ret, and the
     array of identifiers in child_ids.
 
diff --git a/CGNS_docs_current/cgnstools/cgnsplot/perspective.html b/CGNS_docs_current/cgnstools/cgnsplot/perspective.html
index 102b0ce6..40d5ff78 100644
--- a/CGNS_docs_current/cgnstools/cgnsplot/perspective.html
+++ b/CGNS_docs_current/cgnstools/cgnsplot/perspective.html
@@ -11,7 +11,7 @@
 
 
Perspective Control

 
-
This controls the perspective transformation by defining a frustrum
+
This controls the perspective transformation by defining a frustum
 of a pyramid. The Field of View is the angle of the pyramid sides, and
 the Near and Far Clipping Planes define the apex and base of the pyramid,
 respectively. The clipping planes are specified as fractions of the distance
diff --git a/CGNS_docs_current/cgnstools/cgnsview/cgnsnodes.html b/CGNS_docs_current/cgnstools/cgnsview/cgnsnodes.html
index 0799f201..72e2a4c9 100644
--- a/CGNS_docs_current/cgnstools/cgnsview/cgnsnodes.html
+++ b/CGNS_docs_current/cgnstools/cgnsview/cgnsnodes.html
@@ -19,9 +19,9 @@ 

 
The left panel shows all the nodes, arranged in a tree structure as
 defined by the SIDS. Selecting a node will display the relevant information
 for that node. The SIDS definition for a BC node is presented above. If
-the documentation URL's and browser hav been setup (the Setup...
+the documentation URLs and browser have been setup (the Setup...
 button), then the MLL (Mid-Level Library) and SIDS documentation for the
-node may be accessed by clicking on the appropiate button.
+node may be accessed by clicking on the appropriate button.
 
The mouse bindings are the same as for the CGNSview Node
 Tree.
 
Clicking Mouse Button 1 on a node selects the node.
diff --git a/CGNS_docs_current/cgnstools/cgnsview/customize.html b/CGNS_docs_current/cgnstools/cgnsview/customize.html
index a5af5461..f2f2df30 100644
--- a/CGNS_docs_current/cgnstools/cgnsview/customize.html
+++ b/CGNS_docs_current/cgnstools/cgnsview/customize.html
@@ -138,7 +138,7 @@ 

 When the Accept button is selected,
 the import command will be executed as
 
import_my_file option1 option2 InputFile CGNSoutput

-If the command is successfull, then the CGNSview will read and display
+If the command is successful, then the CGNSview will read and display
 the CGNS file.
 
 

diff --git a/CGNS_docs_current/cgnstools/cgnsview/nodedesc.html b/CGNS_docs_current/cgnstools/cgnsview/nodedesc.html
index 8c3c9c67..6527decb 100644
--- a/CGNS_docs_current/cgnstools/cgnsview/nodedesc.html
+++ b/CGNS_docs_current/cgnstools/cgnsview/nodedesc.html
@@ -40,7 +40,7 @@ 
Node Description

         node using the Create or Modify
         buttons. The button to the right invokes a drop-down
         list containing a list of CGNS nodes. Selecting a node
-        from this list, will also fill in appropiate values for
+        from this list, will also fill in appropriate values for
         the Node Label and Data Description panel.

     
 

diff --git a/CGNS_docs_current/cgnstools/cgnsview/toolbar.html b/CGNS_docs_current/cgnstools/cgnsview/toolbar.html
index a1ddaa41..dbaee826 100644
--- a/CGNS_docs_current/cgnstools/cgnsview/toolbar.html
+++ b/CGNS_docs_current/cgnstools/cgnsview/toolbar.html
@@ -160,7 +160,7 @@ 

 
 
If CGNScheck is installed,
 this will invoke a panel to check the
-current file for CGNS compatability.
 

 
 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

     

         -cCombine patchs where possibleCombine patches where possible
     

 

 
@@ -367,7 +367,7 @@ 
CGNSview Interface

 
This allows interactive selection of the input and output
 files and options. The Accept button will then construct
 the command line and run vgrid_to_cgns. If the
-import is successfull, CGNSview will read and display the CGNS
+import is successful, CGNSview will read and display the CGNS
 file.

 
 

@@ -440,7 +440,7 @@ 
CGNSview Interface

 
This allows interactive selection of the input and output
 files and options. The Accept button will then construct
 the command line and run aflr3_to_cgns. If the
-import is successfull, CGNSview will read and display the CGNS
+import is successful, CGNSview will read and display the CGNS
 file.

 
 

@@ -517,7 +517,7 @@ 
CGNSview Interface

 
This allows interactive selection of the input and output
 files and options. The Accept button will then construct
 the command line and run fast_to_cgns. If the
-import is successfull, CGNSview will read and display the CGNS
+import is successful, CGNSview will read and display the CGNS
 file.

 
 

@@ -535,7 +535,7 @@ 
Command Line

 
 
where TetGenfile is the TetGen file. If the file extension
 is .node, .face, or .ele, the additional files to be read will be
-constructed from the base file name and appropiate extensions.
+constructed from the base file name and appropriate extensions.
 If CGNSfile is given, then the
 output will be written to that file, otherwise the CGNS file name
 is constructed from the TetGen file name by replacing the file extension
@@ -553,7 +553,7 @@ 
CGNSview Interface

 
This allows interactive selection of the input and output
 files. The Accept button will then construct
 the command line and run tetgen_to_cgns. If the
-import is successfull, CGNSview will read and display the CGNS
+import is successful, CGNSview will read and display the CGNS
 file.

 
 

diff --git a/CGNS_docs_current/cgnstools/utilities/subset.html b/CGNS_docs_current/cgnstools/utilities/subset.html
index 66ec41eb..74e277d5 100644
--- a/CGNS_docs_current/cgnstools/utilities/subset.html
+++ b/CGNS_docs_current/cgnstools/utilities/subset.html
@@ -207,7 +207,7 @@ 
Command Line

     
     
         -i iter
-        set the max number of Newton interations to iter
+        set the max number of Newton iterations to iter
         (default 20)
     
     
diff --git a/CGNS_docs_current/changes.html b/CGNS_docs_current/changes.html
index 7a6a81d0..11dc8887 100644
--- a/CGNS_docs_current/changes.html
+++ b/CGNS_docs_current/changes.html
@@ -1489,7 +1489,7 @@ 
SIDS File Mapping Manual

     2.3.1
     2.3
     2 Jun 2004
-    Removed some wording inadvertantly left in when the
+    Removed some wording inadvertently left in when the
         documentation was updated with the release of CGNS Version 2.3.
 
     2.4
diff --git a/CGNS_docs_current/charter/license.html b/CGNS_docs_current/charter/license.html
index c0b4aef2..4db5f1fb 100644
--- a/CGNS_docs_current/charter/license.html
+++ b/CGNS_docs_current/charter/license.html
@@ -67,7 +67,7 @@ 
CGNS License

 This license is borrowed from the
 zlib/libpng
 License external link, and
-supercedes the GNU Lesser General Public License (LGPL) which previously
+supersedes the GNU Lesser General Public License (LGPL) which previously
 governed the use and distribution of the software.
 
 

diff --git a/CGNS_docs_current/filemap/general.html b/CGNS_docs_current/filemap/general.html
index 68785ca3..9d6f6421 100644
--- a/CGNS_docs_current/filemap/general.html
+++ b/CGNS_docs_current/filemap/general.html
@@ -366,7 +366,7 @@ 
The Child Table

 anything to do with the order in which they
 were inserted in the file. However, the order returned is consistent
 from call to call provided the file has not been closed and the node
-structure has not been modifed.
+structure has not been modified.
 
 

 Note that there is no parent table; that is, a node has no direct
diff --git a/CGNS_docs_current/hdf5/general.html b/CGNS_docs_current/hdf5/general.html
index 57ad38ad..fb94897a 100644
--- a/CGNS_docs_current/hdf5/general.html
+++ b/CGNS_docs_current/hdf5/general.html
@@ -180,7 +180,7 @@ 
The Data Type

 HDF5 can specify the precision in which it is desired to read or write
 the data, HDF5 knows both the precision available at the source and the
 precision acceptable to the destination and will mitigate accordingly.
-Thus to specify the precison of real data as R4, for example, has
+Thus to specify the precision of real data as R4, for example, has
 no meaning unless both R4 and R8 are available. Therefore,
 the generic specification "DataType" is used to allow for all
 possibilities.
@@ -256,7 +256,7 @@ 
The Child Table

 of a list of children returned by HDF5 has nothing to do with the order
 in which they were inserted in the file. However, the order returned is
 consistent from call to call provided the file has not been closed and
-the node structure has not been modifed.
+the node structure has not been modified.
 
 
 
Cardinality

diff --git a/CGNS_docs_current/hdf5/summary.html b/CGNS_docs_current/hdf5/summary.html
index 689b4e33..57a93c3e 100644
--- a/CGNS_docs_current/hdf5/summary.html
+++ b/CGNS_docs_current/hdf5/summary.html
@@ -55,7 +55,7 @@ 
Implementation Summary

 Instead of having a new mapping dedicated to HDF5, we have made a
 mapping from the ADF nodes to a set of HDF5 groups.
 While this is not an optimal mapping, the use of such an HDF5 node
-allows us to re-use the ADF API without change.
+allows us to reuse the ADF API without change.
 
 

 The HDF5 documentation
@@ -93,8 +93,8 @@ 
Dedicated HDF5 Structures

 

 The CGNS node is an HDF5 group.
 It contains attributes, an optional dataset and optional child groups.
-This structure is required and can be extended by other implementors as
-long as the following requirements are fullfilled.
+This structure is required and can be extended by other implementers as
+long as the following requirements are fulfilled.
 
 

 In a CGNS tree, most of the nodes are normal nodes.
@@ -106,7 +106,7 @@ 
Dedicated HDF5 Structures

 the links.
 These special link structures use the HDF5 mount system.
 It is not necessary for either the MLL or SLL users to understand the
-HDF5 mount system, but it should be understood by SLL implementors.
+HDF5 mount system, but it should be understood by SLL implementers.
 
 
 
The CGNS Node Mapping

@@ -200,7 +200,7 @@ 
The CGNS Node Mapping

 This group should be a child of the root node, its absolute path is
 [/ mount].
 The group [ mount] contains one group for each mounted
-file refered to by a link.
+file referred to by a link.
 Each entry has the attributes described in the table below. 
 The link node itself is a group with the special name
 [ link].
diff --git a/CGNS_docs_current/midlevel/fileops.html b/CGNS_docs_current/midlevel/fileops.html
index 8238a7aa..0bb9bae7 100644
--- a/CGNS_docs_current/midlevel/fileops.html
+++ b/CGNS_docs_current/midlevel/fileops.html
@@ -554,7 +554,7 @@ 
Interfacing with CGIO

    CGNS file index number.
 
    cgio_num
-   CGIO indentifier for the CGNS file.
+   CGIO identifier for the CGNS file.
 
    rootid
    Root node identifier for the CGNS file.
diff --git a/CGNS_docs_current/midlevel/general.html b/CGNS_docs_current/midlevel/general.html
index f2e5a08a..cff3cc45 100644
--- a/CGNS_docs_current/midlevel/general.html
+++ b/CGNS_docs_current/midlevel/general.html
@@ -156,7 +156,7 @@ 
Error Status

 status.
 All Fortran functions have an additional parameter, ier,
 which contains the value of the error status.
-An error status different from zero implies that an error occured.
+An error status different from zero implies that an error occurred.
 The error message can be printed using the error
 handling functions of the CGNS library.
 The error codes are coded in the C and Fortran include files
@@ -389,7 +389,7 @@ 
Character Names For Typedefs

 These are global arrays dimensioned to the size of each list of
 typedefs.
 To retrieve a character string representation of a typedef, use the
-typedef value as an index to the appropiate character array.
+typedef value as an index to the appropriate character array.
 For example, to retrieve the string "Meter"
 for the LengthUnits_t Meter typedef, use
 LengthUnitsName[Meter].
@@ -582,7 +582,7 @@ 
64-bit Fortran Portability

 
 
 

-DISCLAMER: The following section's practice is not recommend! 
+DISCLAIMER: The following section's practice is not recommend! 
 
 

 If you have explicitly defined your default integers which are passed to the CGNS library as INTEGER*8, or used a compiler option to promote implicit integers to INTEGER*8, then you MUST compile the CGNS library with the same compiler option in order to promote implicit integers to INTEGER*8. If you really must promote all integers to INTEGER*8 in your code, and you are not able to compile the CGNS library with the same compilar options,  then it is recommended that all arguments in the CGNS Fortran APIs should be declared as INTEGER(C_INT) if the corresponding argument in the C API is declared as an int.
diff --git a/CGNS_docs_current/midlevel/grid.html b/CGNS_docs_current/midlevel/grid.html
index ccd8ac0b..8942fe0c 100644
--- a/CGNS_docs_current/midlevel/grid.html
+++ b/CGNS_docs_current/midlevel/grid.html
@@ -807,7 +807,7 @@ 
Element Connectivity

 connectivity array Elements.
 The cg_section_partial_write function will create the element section
 data for the range start to end with the element data
-intialized to 0. cg_poly_section_write and cg_poly_section_partial_write
+initialized to 0. cg_poly_section_write and cg_poly_section_partial_write
  have a comparable behavior for MIXED, NGON_n, and NFACE_n. 
 To add elements to the section, use cg_elements_partial_write
 or cg_poly_elements_partial_write
diff --git a/CGNS_docs_current/midlevel/timedep.html b/CGNS_docs_current/midlevel/timedep.html
index 70387aff..f772e444 100644
--- a/CGNS_docs_current/midlevel/timedep.html
+++ b/CGNS_docs_current/midlevel/timedep.html
@@ -463,7 +463,7 @@ 
Zone Grid Connectivity

 
 

 The functions cg_zconn_read and cg_zconn_write
-will implicity set the current ZoneGridConnectivity_t
+will implicitly set the current ZoneGridConnectivity_t
 node, while cg_zconn_set explicitly sets it. The functions
 cg_nzconns and cg_zconn_get do not change it.
 
diff --git a/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.1.html b/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.1.html
index 9360a0fa..ce237a3c 100644
--- a/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.1.html
+++ b/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.1.html
@@ -119,7 +119,7 @@ 
AP209 Edition 2

 A high-level planning diagram that provides an overview of the contents
 of AP209E2 is shown in Figure 2. The SC4 community has gone to a
 modular approach to developing Application Protocols (APs) to promote
-integration and ease of re-use. Due the modularization of existing
+integration and ease of reuse. Due the modularization of existing
 AP209 capabilities it is now possible to take advantage of this new SC4
 Modular Architecture by embedding the second edition of AP203 and get
 all the new shape, presentation, and GD&T capabilities.
diff --git a/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.2.html b/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.2.html
index bce8d0b9..0e3db0db 100644
--- a/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.2.html
+++ b/CGNS_docs_current/minutes/attachments/AP209Edition2OverviewRev1.2.html
@@ -122,7 +122,7 @@ 
AP209 Edition 2

 A high-level planning diagram that provides an overview of the contents
 of AP209E2 is shown in Figure 2. The SC4 community has gone to a
 modular approach to developing Application Protocols (APs) to promote
-integration and ease of re-use. Due the modularization of existing
+integration and ease of reuse. Due the modularization of existing
 AP209 capabilities it is now possible to take advantage of this new SC4
 Modular Architecture by embedding the second edition of AP203 and get
 all the new shape, presentation, and GD&T capabilities.
diff --git a/CGNS_docs_current/minutes/attachments/jan01_ISO.html b/CGNS_docs_current/minutes/attachments/jan01_ISO.html
index 705a4171..6de15eef 100644
--- a/CGNS_docs_current/minutes/attachments/jan01_ISO.html
+++ b/CGNS_docs_current/minutes/attachments/jan01_ISO.html
@@ -31,7 +31,7 @@ 
What Is STEP?

 
    
 
  •  STEP is an acronym
      
      
-     
    •  STandard for the Exchange of Product model data
+     
    •  STandard for the Exchange of Pproduct model data
      
    
 
  •  Formal name is ISO 10303
      
      
@@ -105,10 +105,10 @@ 
      Differences between ISO-STEP and CGNS
      
      
        
      
      •  Record of all data sources, persistent links if possible
      
      
-
    •  Commonality and re-use of existing data structures to maximum      
+
    •  Commonality and reuse of existing data structures to maximum      
      extent possible                                                         
      
        
-     
      •  E.g., re-use data structures from AP203 (geometry), AP209
+     
      •  E.g., reuse data structures from AP203 (geometry), AP209
           (finite element analysis), and AP232 (technical data exchange)
      
      
 
    •  ASCII data exchange 
@@ -156,7 +156,7 @@ 
      ISO Organization
      
 
      
 
      
 Chart showing ISO heirarchy related to CGNS
 
      
 
diff --git a/CGNS_docs_current/minutes/attachments/jan01_survey.html b/CGNS_docs_current/minutes/attachments/jan01_survey.html
index 447a70f7..ad488fae 100644
--- a/CGNS_docs_current/minutes/attachments/jan01_survey.html
+++ b/CGNS_docs_current/minutes/attachments/jan01_survey.html
@@ -88,7 +88,7 @@ 
      Other Observations
      
      
    •  Complaints about "heaviness of CGNS"
      
    •  Problems with complexity and structure of documentation
      
    •  Some link problems under Windows & LINUX
-     
    •  Poor implementation of BC's and unstructured data tyoes
+     
    •  Poor implementation of BC's and unstructured data types
      
    
 

 
diff --git a/CGNS_docs_current/minutes/attachments/jan02_ISO.html b/CGNS_docs_current/minutes/attachments/jan02_ISO.html
index 17e74beb..f1cf436a 100644
--- a/CGNS_docs_current/minutes/attachments/jan02_ISO.html
+++ b/CGNS_docs_current/minutes/attachments/jan02_ISO.html
@@ -37,7 +37,7 @@ 
What Is STEP?

 
    
 
  •  STEP is an acronym
      
      
-     
    •  STandard for the Exchange of Product model data
+     
    •  STandard for the Exchange of Pproduct model data
      
    
 
  •  Formal name is ISO 10303
      
      
@@ -88,10 +88,10 @@ 
      Differences between ISO-STEP and CGNS
      
      
        
      
      •  Record of all data sources, persistent links if possible
      
      
-
    •  Commonality and re-use of existing data structures to maximum      
+
    •  Commonality and reuse of existing data structures to maximum      
      extent possible                                                         
      
        
-     
      •  E.g., re-use data structures from AP203 (geometry), AP209
+     
      •  E.g., reuse data structures from AP203 (geometry), AP209
           (finite element analysis), and AP232 (technical data exchange)
      
      •  As we create new data structures, attempt to anticipate future
           use of those data structures by other disciplines
@@ -108,7 +108,7 @@ 
        ISO Organization
        
 
        
 
        
 Chart showing ISO heirarchy related to CGNS
 
        
 
diff --git a/CGNS_docs_current/minutes/meeting_jan00.html b/CGNS_docs_current/minutes/meeting_jan00.html
index 8ac152f2..07b5a4da 100644
--- a/CGNS_docs_current/minutes/meeting_jan00.html
+++ b/CGNS_docs_current/minutes/meeting_jan00.html
@@ -404,7 +404,7 @@ 
        2.2 Verification
        
 Users are questioning the performance of CGNS, and what they can expect
 in comparison to their existing I/O systems. Preliminary performance
 tests have shown that it takes more CPU time to create a new CGNS file,
-or to read an existing one, then to write or read a typical sequencial
+or to read an existing one, then to write or read a typical sequential
 file.  However, once the database is created, interrogating a CGNS file
 shows much better performance.  This is due to the fact that CGNS not
 only writes long list of data, but also creates an organized database.
diff --git a/CGNS_docs_current/minutes/meeting_jan01.html b/CGNS_docs_current/minutes/meeting_jan01.html
index 9408dd64..1df0acf7 100644
--- a/CGNS_docs_current/minutes/meeting_jan01.html
+++ b/CGNS_docs_current/minutes/meeting_jan01.html
@@ -50,7 +50,7 @@ 
        Meeting Minutes
        
      seconded. Each of the proposed new members briefly introduced
      themselves and their organizations. Aerospatiale Matra Airbus -
      Alexandre Corjon; AEDC - Greg Power; Pointwise - John Chawner. The
-     motion passed by concensus.
+     motion passed by consensus.
 

        
 
      •  Logo - John Chawner presented revised logo recommendations
      designed by the DPC Group. The DPC Group has offered their design
@@ -58,7 +58,7 @@ 
        Meeting Minutes
        
      site. There was some discussion of the designs, and John agreed to
      take minor suggestions back to the design group and have the logo
      revised.  The proposed designs are included
-     below.  Concensus seemed to form around number 1, dropping 'the'
+     below.  Consensus seemed to form around number 1, dropping 'the'
      and increasing the size of the 'CFD Data Standard' tag line to be
      the full width of the CGNS text.
 

        
diff --git a/CGNS_docs_current/minutes/meeting_jan08.html b/CGNS_docs_current/minutes/meeting_jan08.html
index f786cf7c..f90678cd 100644
--- a/CGNS_docs_current/minutes/meeting_jan08.html
+++ b/CGNS_docs_current/minutes/meeting_jan08.html
@@ -215,7 +215,7 @@ 
        Meeting Minutes
        
           dependent.  We may need to define our own datatype to allow
           for greater than 2 Gig signed limit.  This item has also been
           added as an "Open Item."
-     
      •  Need to change Celcius to Celsius (cgnsKeywords.h,
+     
      •  Need to change Celsius to Celsius (cgnsKeywords.h,
           cgnslib.c, cgnslib.h, cgnslib_f.h) (Lecointe
           12/5/07
           CGNSTalk). Fixed in CVS version 2.5.  Will be in V2.5.3
diff --git a/CGNS_docs_current/minutes/meeting_jun00.html b/CGNS_docs_current/minutes/meeting_jun00.html
index 48c62d30..e75718a0 100644
--- a/CGNS_docs_current/minutes/meeting_jun00.html
+++ b/CGNS_docs_current/minutes/meeting_jun00.html
@@ -37,7 +37,7 @@ 
        Meeting Minutes
        
 
        
 The meeting was called to order at 7:30pm.
 There were 12 attendees, listed below.
-In additon, Armen Darian, Ray Cosner, Michel Delanaye and John Chawner
+In addition, Armen Darian, Ray Cosner, Michel Delanaye and John Chawner
 indicated that they would not be able to attend the meeting and sent
 information to the Chair or an alternate.
 
diff --git a/CGNS_docs_current/minutes/telecon_aug00.html b/CGNS_docs_current/minutes/telecon_aug00.html
index 296283be..595e7d9c 100644
--- a/CGNS_docs_current/minutes/telecon_aug00.html
+++ b/CGNS_docs_current/minutes/telecon_aug00.html
@@ -142,7 +142,7 @@ 
        Telecon Minutes
        
      file. This also raises the possibility of a 'validator' which
      checks for some set of minimal information required to make the
      file 'compliant'. Francis Enomoto has looked at XML, which might be
-     useable as a CGNS browser since XML structures are similar to CGNS
+     usable as a CGNS browser since XML structures are similar to CGNS
      structures. He will try to map the SIDS into an XML format.
 
      
 
diff --git a/CGNS_docs_current/minutes/telecon_dec02.html b/CGNS_docs_current/minutes/telecon_dec02.html
index d0840792..286808c1 100644
--- a/CGNS_docs_current/minutes/telecon_dec02.html
+++ b/CGNS_docs_current/minutes/telecon_dec02.html
@@ -48,7 +48,7 @@ 
      Telecon Minutes
      
 Potential items for the agenda were suggested, including:
 
        
 
      •  Announcing the release of V2.2 of the libraries
-
      •  Discuss the interest in a new demo of inter-operability using CGNS
+
      •  Discuss the interest in a new demo of interoperability using CGNS
      and the new utilities
 
      •  Discuss what the next thrust should be
 
      •  Discuss funding strategies
diff --git a/CGNS_docs_current/minutes/telecon_jun10.htm b/CGNS_docs_current/minutes/telecon_jun10.htm
index 6f762cf7..aa891dba 100644
--- a/CGNS_docs_current/minutes/telecon_jun10.htm
+++ b/CGNS_docs_current/minutes/telecon_jun10.htm
@@ -952,7 +952,7 @@
 and (CG_)UserDefined macros from the file completely which would force users to
 move to the correct values on upgrade to Version 3. Rumsey indicated the
 removal of these generic values may cause backwards compatibility problems and
-further problems for users who specifiy their own types.
        
+further problems for users who specify their own types.
        
 
 
        Hann will send a
 description of how the  documentation for
diff --git a/CGNS_docs_current/minutes/telecon_mar00.html b/CGNS_docs_current/minutes/telecon_mar00.html
index c04f6fed..32248f56 100644
--- a/CGNS_docs_current/minutes/telecon_mar00.html
+++ b/CGNS_docs_current/minutes/telecon_mar00.html
@@ -297,7 +297,7 @@ 
        Report from NUMECA
        
 I mentioned some problems regarding speed. Further investigation on
 our side has highlighted some bad usage which has been corrected
 since. I also mentioned our wish to be able to store quantities on
-block boundaries. The Boeing proposal will most propably meet our
+block boundaries. The Boeing proposal will most probably meet our
 expectations. The last comment was about the ability to store our
 hierarchal hexahedral unstructured grids. On this matter, I am going to
 investigate different possibilities and probably contact Diane with some
diff --git a/CGNS_docs_current/minutes/telecon_mar04.html b/CGNS_docs_current/minutes/telecon_mar04.html
index 1f7e3f8f..0556aa59 100644
--- a/CGNS_docs_current/minutes/telecon_mar04.html
+++ b/CGNS_docs_current/minutes/telecon_mar04.html
@@ -145,7 +145,7 @@ 
        Telecon Minutes
        
                be better in the long run to go with Wedan's suggestion
                (number 2).  Wedan could make the API automatically fix
                files doing it the old way (transparent to the user), so
-               backward compatability will not be a problem.
+               backward compatibility will not be a problem.
           
      •  It was finally decided to go with Wedan's suggestion, but
                only when the next major release occurs.  This way, there
                is plenty of time to make changes in the beta releases
diff --git a/CGNS_docs_current/minutes/telecon_mar05.html b/CGNS_docs_current/minutes/telecon_mar05.html
index 76162458..20824999 100644
--- a/CGNS_docs_current/minutes/telecon_mar05.html
+++ b/CGNS_docs_current/minutes/telecon_mar05.html
@@ -91,7 +91,7 @@ 
        Telecon Minutes
        
           unstructured, and will contact Rumsey about it.
           
          
           
        •  Done. The change is easy to do, but it is a problem
-               because it causes loss of backward compatability.
+               because it causes loss of backward compatibility.
                Discussion below.
           
        
      
      •  Michal will write a first draft proposal to handle polyhedral
@@ -194,12 +194,12 @@ 
        Telecon Minutes
        
           to Towne.
      
      •  UIUC proposal to modify Rind data for use with unstructured
           data was discussed. The software change is relatively simple,
-          but the change is not forward compatable: if put into V2.4,
+          but the change is not forward compatible: if put into V2.4,
           then earlier versions of the software would not be able to
           read the V2.4 file.  Several options were discussed:
           
          
           
        •  hold off on change until Version 3.0 (major releases do
-               not have to be forward compatable)
+               not have to be forward compatible)
           
        •  put in, and provide data stripper
           
        •  create a new URind node 
           
        
diff --git a/CGNS_docs_current/minutes/telecon_mar06.html b/CGNS_docs_current/minutes/telecon_mar06.html
index 5dd52bc2..2bec0f65 100644
--- a/CGNS_docs_current/minutes/telecon_mar06.html
+++ b/CGNS_docs_current/minutes/telecon_mar06.html
@@ -251,10 +251,10 @@ 
        Telecon Minutes
        
      
      •  Version numbering discussion
           
          
           
        •  generally, we consider e.g. 2.0 → 3.0 a major new
-               release, with possible loss of some compatability - it is
+               release, with possible loss of some compatibility - it is
                formally announced
           
        •  2.3 → 2.4 a fairly significant new release, with
-               compatability maintained - it is also formally announced
+               compatibility maintained - it is also formally announced
           
        •  when there are fairly minor changes, like bug fixes or
                small enhancements that do not affect most users, they
                sometimes come out unannounced (e.g., 2.4.2 → 2.4.3)
diff --git a/CGNS_docs_current/minutes/telecon_mar07.html b/CGNS_docs_current/minutes/telecon_mar07.html
index a9a9e992..d1f7a5c4 100644
--- a/CGNS_docs_current/minutes/telecon_mar07.html
+++ b/CGNS_docs_current/minutes/telecon_mar07.html
@@ -221,7 +221,7 @@ 
          Telecon Minutes
          
                the scope and find out whether it is related to ADFH or
                to HDF5. I suspect the (mis-?)use of HDF5 attributes
                through an HDF5 group.
-          
        •  I am very confident in acheiving this by summer 2007,
+          
        •  I am very confident in achieving this by summer 2007,
                so that we could run tons of tests for a Reno 2008
                release. Note that such a release is related to the
                public release of HDF5 with external links feature.
diff --git a/CGNS_docs_current/minutes/telecon_may05.html b/CGNS_docs_current/minutes/telecon_may05.html
index 633dacdf..a61c637d 100644
--- a/CGNS_docs_current/minutes/telecon_may05.html
+++ b/CGNS_docs_current/minutes/telecon_may05.html
@@ -151,10 +151,10 @@ 
          Telecon Minutes
          
           
            
           
          •  Done.  Bruce can implement the additional PYRA element,
                but apparently there is a problem with forward
-               compatability (if try to read 2.4 file with older version
+               compatibility (if try to read 2.4 file with older version
                of CGNS, will have error).  For now, Bruce will comment
                out, but this is an item that needs to be implemented
-               when we are willing to lose forward compatability. This
+               when we are willing to lose forward compatibility. This
                item added to "open item" list.
           
          
      
        •  Wedan will change the MLL to return element list instead of
@@ -190,11 +190,11 @@ 
          Telecon Minutes
          
           will be correct in official V2.4 when it comes on line.
      
        •  Further discussion on modifying Rind to allow for unstructured
           grids (Norris and others are interested.) Wedan has a fix,
-          but CGNS loses forward compatability with it.  For now, these
+          but CGNS loses forward compatibility with it.  For now, these
           fixes are commented out. Norris will try to work with the
           fixes and see if they meet his needs.  Also, this item will be
           added to "open items" list and will be officially implemented
-          when we are willing to lose forward compatability.
+          when we are willing to lose forward compatibility.
      
        •  Hann reported on his idea to decouple the MLL from ADF
           and HDF5.  He wants to be able to use ADF and HDF5
           interchangeably. Hann will send his proposed changes to
diff --git a/CGNS_docs_current/minutes/telecon_may07.html b/CGNS_docs_current/minutes/telecon_may07.html
index 24024eb2..0fbe7d20 100644
--- a/CGNS_docs_current/minutes/telecon_may07.html
+++ b/CGNS_docs_current/minutes/telecon_may07.html
@@ -208,7 +208,7 @@ 
          Telecon Minutes
          
      
        •  Face-based storage proposal - ongoing (Allmaras has action item)
      
        •  Regions proposal - will be put to e-mail committee vote
           (Rumsey action item)
-     
        •  Generalized Conectivity - will be put to e-mail committee
+     
        •  Generalized Connectivity - will be put to e-mail committee
           vote (Rumsey action item)
      
 
          
diff --git a/CGNS_docs_current/minutes/telecon_nov03.html b/CGNS_docs_current/minutes/telecon_nov03.html
index f604a2b8..984871d2 100644
--- a/CGNS_docs_current/minutes/telecon_nov03.html
+++ b/CGNS_docs_current/minutes/telecon_nov03.html
@@ -201,7 +201,7 @@ 
          Telecon Minutes
          
      
            
      
          1.  Poinot will further investigate possible problem between V2.2
           and V2.3 related to ADF children IDs when using HDF-5 package.
-     
          2.  Wedan will add Poinot and Power's HDF-5 implemetation package
+     
          3.  Wedan will add Poinot and Power's HDF-5 implementation package
           to SourceForge.
      
          4.  Alonso and Van derWeide will experiment with various record
           lengths to see what types of speed-up can be achieved.
diff --git a/CGNS_docs_current/minutes/telecon_nov07.html b/CGNS_docs_current/minutes/telecon_nov07.html
index 97757e32..524c01a0 100644
--- a/CGNS_docs_current/minutes/telecon_nov07.html
+++ b/CGNS_docs_current/minutes/telecon_nov07.html
@@ -427,7 +427,7 @@ 
            Report on CGNS/HDF5 with external links from Marc Poinot (Onera)
            
 I can take parts of [2], [4] and [6]. Maybe Bruce can handle [1] and
 take a look at the code. All CGNS users can re-link the MLL and test
 their applications to fulfill [3] (including ONERA). We could have
-a test matrix saying if the user has tested his nown use of MLL on
+a test matrix saying if the user has tested his known use of MLL on
 read/write/modify, with/without links, pre/post ADF/HDF files with
 adf2hdf ...
 
diff --git a/CGNS_docs_current/minutes/telecon_oct00.html b/CGNS_docs_current/minutes/telecon_oct00.html
index 5615718f..93519232 100644
--- a/CGNS_docs_current/minutes/telecon_oct00.html
+++ b/CGNS_docs_current/minutes/telecon_oct00.html
@@ -138,7 +138,7 @@ 
            Telecon Minutes
            
           make assumptions about the file and avoid messy checks for
           data availability. There is a need for a classification system
           (e.g. solution with conservation variables, non-dimensional
-          structured grid, heirarchical structures with at most 2
+          structured grid, hierarchical structures with at most 2
           children,?). There were no volunteers to develop this system,
           but it was agreed that we should continue to pursue the idea,
           the classification system and the utilities.
@@ -183,7 +183,7 @@ 
            Telecon Minutes
            
 
        
 
 
        
-The January meeting is tenatively scheduled for Monday night at Reno.
+The January meeting is tentatively scheduled for Monday night at Reno.
 
 
 
        Attendees
        
diff --git a/CGNS_docs_current/minutes/telecon_oct05.html b/CGNS_docs_current/minutes/telecon_oct05.html
index 094d8cad..c89052d2 100644
--- a/CGNS_docs_current/minutes/telecon_oct05.html
+++ b/CGNS_docs_current/minutes/telecon_oct05.html
@@ -170,7 +170,7 @@ 
        Telecon Minutes
        
           Rumsey will review the HDF-5 "to do" list and revise if
           necessary
      
      •  Regarding the issue of resolving differences between SIDS and
-          ISO/STEP, this is still tabled for the forseeable future
+          ISO/STEP, this is still tabled for the foreseeable future
      
      •  Regarding certification process:
           (a) adfviewer
           has a compliance checker that is continually undergoing
diff --git a/CGNS_docs_current/minutes/telecon_oct06.html b/CGNS_docs_current/minutes/telecon_oct06.html
index 407a7c48..e97f5b56 100644
--- a/CGNS_docs_current/minutes/telecon_oct06.html
+++ b/CGNS_docs_current/minutes/telecon_oct06.html
@@ -434,7 +434,7 @@ 
        Minutes of Mini-telecon concerning Face-based storage proposal
        
 
        
 Thus, for the current proposal, there will be not only some
 documentation changes, but also some (minor) coding changes required to
-implement this proposal, in order to accomodate the new flag.  It was
+implement this proposal, in order to accommodate the new flag.  It was
 also mentioned that one of the CGNS "checkers" may need to be modified,
 because cell size in Zone_t will no longer match up with number
 of elements when they are face-based.
diff --git a/CGNS_docs_current/minutes/telecon_sep04.html b/CGNS_docs_current/minutes/telecon_sep04.html
index 63c37ad3..0a97b248 100644
--- a/CGNS_docs_current/minutes/telecon_sep04.html
+++ b/CGNS_docs_current/minutes/telecon_sep04.html
@@ -160,7 +160,7 @@ 
        Telecon Minutes
        
      
      •  Rumsey asked about hitting "reply" when answering a CGNSTalk
           e-mail.  By default the reply goes to sender only and not
           CGNSTalk. Towne will check to see if the settings can be
-          changed so replys automatically go to CGNSTalk.
+          changed so replies automatically go to CGNSTalk.
      
 
        
 
      •  Software status/discussion (Wedan):
@@ -292,7 +292,7 @@ 
        Telecon Minutes
        
      
      •  Rumsey will e-mail Bussoletti to ask him for definitions of
           SoundIntensityDB, etc.
      
      •  Towne will check to see if the settings in CGNSTalk can be
-          changed so replys automatically go to CGNSTalk.
+          changed so replies automatically go to CGNSTalk.
      
      •  Van der Weide will try out the HDF-5 version of CGNS on his
           test case, using links, and will report back.
      
      •  Wedan will make another 2.3.x release and will announce it
diff --git a/CGNS_docs_current/minutes/telecon_sep08.html b/CGNS_docs_current/minutes/telecon_sep08.html
index cbc560b0..a6107a84 100644
--- a/CGNS_docs_current/minutes/telecon_sep08.html
+++ b/CGNS_docs_current/minutes/telecon_sep08.html
@@ -58,7 +58,7 @@ 
        Telecon Minutes
        
      
      •  Poinot to try Version 3 fix for HDF-5 indexing problem, and
           make sure it works for his applications.
      
      •  There was also discussion about whether to put the fix in
-          Version 2.x.  If we do, we lose forward compatability (if
+          Version 2.x.  If we do, we lose forward compatibility (if
           try to open new file with older software, it will fail).
           Consensus: to NOT put fix in Version 2.x.  This means that
           Version 2.x and earlier will have this known problem: HDF-5
diff --git a/CGNS_docs_current/overview/elements.html b/CGNS_docs_current/overview/elements.html
index 953792c4..7998bac3 100644
--- a/CGNS_docs_current/overview/elements.html
+++ b/CGNS_docs_current/overview/elements.html
@@ -115,7 +115,7 @@ 
        Structure of a CGNS Database
        
 In this section, the conceptual structure of a CGNS database, and the
 nodes from which it is built, are discussed. This describes the way
 in which the CGNS software "sees" the database, not necessarily the way
-in which it is implementated. The details of the implementation are
+in which it is implemented. The details of the implementation are
 left to the underlying database manager.
 
 
        
@@ -218,7 +218,7 @@ 
        High-Level Organization of the CGNS Database
        
 the "Name" field of the CGNSBase_t node.
 Current CGNS conventions require that the CGNSBase_t node be
 located directly below a "root node" in the database file
-indentified by the name "/".
+identified by the name "/".
 
 
        
 A database file may contain multiple CGNS databases, and thus
diff --git a/CGNS_docs_current/papers/aiaa00-0681.html b/CGNS_docs_current/papers/aiaa00-0681.html
index ca72f7d5..64051bd5 100644
--- a/CGNS_docs_current/papers/aiaa00-0681.html
+++ b/CGNS_docs_current/papers/aiaa00-0681.html
@@ -780,7 +780,7 @@ 
        2.5 Iterative and Time-Accurate Data
        
 contains information relative to each time step or iteration stored.
 
 
        
-It is proposed that the interative and time-accurate _data structure
+It is proposed that the interactive and time-accurate _data structure
 be recorded independently for each zone of the CGNS base. Therefore it
 would be added under each zone data structure (Zone_t). There
 may be zero to several IterativeOrTemporalData_t nodes under a
diff --git a/CGNS_docs_current/papers/aiaa02-0752.html b/CGNS_docs_current/papers/aiaa02-0752.html
index 99ff5a09..c2d29697 100644
--- a/CGNS_docs_current/papers/aiaa02-0752.html
+++ b/CGNS_docs_current/papers/aiaa02-0752.html
@@ -744,7 +744,7 @@ 
        4. Status of the ISO standards effort
        
 present, no ISO standards initiatives are in progress in other related
 areas that would utilize CFD data, for example, thermodynamics data,
 electromagnetics data, etc. If and when standards initiatives are
-launched in these areas, we expect they will be able to re-use Parts 52
+launched in these areas, we expect they will be able to reuse Parts 52
 and 53.
 
 
        
diff --git a/CGNS_docs_current/papers/aiaa05-1381.html b/CGNS_docs_current/papers/aiaa05-1381.html
index 239767bc..020df8f8 100644
--- a/CGNS_docs_current/papers/aiaa05-1381.html
+++ b/CGNS_docs_current/papers/aiaa05-1381.html
@@ -145,14 +145,14 @@ 
        B. Parallel Implementation
        
 important change is the breakup of the writing of data arrays into two
 steps. In the serial implementation "GridCoordinates" are written in
 one function all "cg_coord_write". Since creating structural nodes in
-HDF5 and therefor CGNS require collective operations, an additional
+HDF5 and therefore CGNS require collective operations, an additional
 step "cgp_coord_create" which has the same syntax as the serial write
 but does not write any data and returns a coordinate index number. The
 only difference is that an empty data set is created collectively. This
 data set is then filled with the actual data using another call
 "cgp_coord_write" using the coordinate index number from the creation
 subroutine call. This write is done independently for each processor and
-therefor allows for independent parallel I/O.
+therefore allows for independent parallel I/O.
 
 
        III. Performance Benchmarks
        
 
diff --git a/CGNS_docs_current/papers/aiaa08-0479/fig2.html b/CGNS_docs_current/papers/aiaa08-0479/fig2.html
index 4797ae12..cb2a344c 100644
--- a/CGNS_docs_current/papers/aiaa08-0479/fig2.html
+++ b/CGNS_docs_current/papers/aiaa08-0479/fig2.html
@@ -27,7 +27,7 @@
 For a total of 108 points, the file size is about 0.4
 gigabyte.
 The plot scale is such that relative differences can't be distinguished
-fot the three smaller cases, but for all three the file size is less
+for the three smaller cases, but for all three the file size is less
 than 0.1 gigabyte.
 
 
        
diff --git a/CGNS_docs_current/pcgns/library.html b/CGNS_docs_current/pcgns/library.html
index aeace385..c5a092c5 100644
--- a/CGNS_docs_current/pcgns/library.html
+++ b/CGNS_docs_current/pcgns/library.html
@@ -158,7 +158,7 @@ 
        Miscellaneous Routines
        
    The MPI communicator to be used by the CGNS library.
    
    mode  
-   Parallel input/ouput mode.
+   Parallel input/output mode.
 
    use_queue
    enable or disables queued output.
@@ -381,7 +381,7 @@ 
        Grid Coordinate Data
        
 The above functions are used to read and write grid coordinate data
 by multiple processes in a parallel fashion. To write the data in
 parallel, first call cgp_coord_write to create an empty
-data node. This call is indentical to
+data node. This call is identical to
 cg_coord_write
 with coord_array set to NULL (no data written). The
 actual data is then written to the node in parallel using either
@@ -516,7 +516,7 @@ 
        Element Connectivity Data
        
 The above functions are used to read and write element connectivity data
 by multiple processes in a parallel fashion. To write the element data in
 parallel, first call cgp_section_write to create an empty
-data node. This call is indentical to
+data node. This call is identical to
 cg_section_write
 with Elements set to NULL (no data written). The
 actual element data is then written to the node in parallel using
@@ -656,7 +656,7 @@ 
        Solution Data
        
 The above functions are used to read and write solution arrays
 by multiple processes in a parallel fashion. To write the data in
 parallel, first call cgp_field_write to create an empty
-data node. This call is indentical to
+data node. This call is identical to
 cg_field_write
 with solution_array set to NULL (no data written). The
 actual data is then written to the node in parallel using either
diff --git a/CGNS_docs_current/sids/bc.html b/CGNS_docs_current/sids/bc.html
index 843938bf..774efb8c 100644
--- a/CGNS_docs_current/sids/bc.html
+++ b/CGNS_docs_current/sids/bc.html
@@ -334,7 +334,7 @@ 
        9.2 Zonal Boundary Condition Structure Definition: ZoneBC_t
        
 Reference-state data is useful for situations where boundary-condition
 data is not provided, and flow solvers are free to enforce any
 appropriate boundary condition equations.
-The presense of ReferenceState
+The presence of ReferenceState
 at this level or below specifies the appropriate flow conditions from
 which the flow solver should extract its boundary-condition data.
 For example, when computing an external flowfield around an airplane, an
diff --git a/CGNS_docs_current/sids/cgnsbase.html b/CGNS_docs_current/sids/cgnsbase.html
index 3cd0e9dd..cff0fff8 100644
--- a/CGNS_docs_current/sids/cgnsbase.html
+++ b/CGNS_docs_current/sids/cgnsbase.html
@@ -107,7 +107,7 @@ 
        6.2 CGNS Entry Level Structure Definition: CGNSBase_t
        
 a complete CFD computation can be archived and reproduced using the data
 defined in the CGNSBase. However a CGNS tree can contain more than one base,
 these can be related to the same CFD case or not. The behavior of a multi-base
-CGNS tree is application dependant, even if inter-base relationships are
+CGNS tree is application dependent, even if inter-base relationships are
 authorized in three cases:
 
          
  
        •  A reference to another base's zone name (including its sub-nodes' names)
diff --git a/CGNS_docs_current/sids/conv.html b/CGNS_docs_current/sids/conv.html
index ed452e0e..96dfaada 100644
--- a/CGNS_docs_current/sids/conv.html
+++ b/CGNS_docs_current/sids/conv.html
@@ -1602,11 +1602,11 @@ 
          3.3.3.2 Pyramid Elements
          
 The cubic forms of pyramid elements, PYRA_21,
 PYRA_29, and PYRA_30
 contain two interior nodes along each edge, eight interior face nodes
-in the case of PYRA_29 and PYRA_30, and an additonal
+in the case of PYRA_29 and PYRA_30, and an additional
 interior volume node for PYRA_30.
 The quartic forms of pyramid elements, PYRA_P4_29, PYRA_50, and PYRA_55
 contain three interior nodes along each edge, 21 interior face nodes
-in the case of PYRA_50, and 21 interior face nodes and five additonal
+in the case of PYRA_50, and 21 interior face nodes and five additional
 interior volume nodes for PYRA_55.
 
 
          Linear and Quadratic Elements
          
@@ -2046,12 +2046,12 @@ 
          3.3.3.3 Pentahedral Elements
          
 The cubic forms of the pentahedral elements, PENTA_24,
 PENTA_38, and PENTA_40
 contain two interior nodes along each edge, fourteen interior face nodes
-in the case of PENTA_38 and PENTA_40, and an additonal
+in the case of PENTA_38 and PENTA_40, and an additional
 two interior volume nodes for PENTA_40.
 The quartic forms of the pentahedral elements, 
 PENTA_33, PENTA_66, and PENTA_75
 contain three interior nodes along each edge, 33 interior face nodes
-in the case of PENTA_66, and 33 interior face nodes and an additonal
+in the case of PENTA_66, and 33 interior face nodes and an additional
 nine interior volume nodes for PENTA_75.
 
 
          Linear and Quadratic Elements
          
@@ -2501,12 +2501,12 @@ 
          3.3.3.4 Hexahedral Elements
          
 The cubic forms of the hexahedral elements, HEXA_32,
 HEXA_56, and HEXA_64
 contain two interior nodes along each edge, 24 interior face nodes
-in the case of HEXA_56 and HEXA_64, and an additonal
+in the case of HEXA_56 and HEXA_64, and an additional
 eight interior volume nodes for HEXA_64.
 The quartic forms of the hexahedral elements,
 HEXA_44, HEXA_98, and HEXA_125
 contain three interior nodes along each edge, 54 interior face nodes
-in the case of HEXA_98, and 54 interior face nodes and an additonal
+in the case of HEXA_98, and 54 interior face nodes and an additional
 27 interior volume nodes for HEXA_125.
 
 
          Linear and Quadratic Elements
          
diff --git a/CGNS_docs_current/sids/gridflow.html b/CGNS_docs_current/sids/gridflow.html
index 1280531c..6cc98f56 100644
--- a/CGNS_docs_current/sids/gridflow.html
+++ b/CGNS_docs_current/sids/gridflow.html
@@ -715,7 +715,7 @@ 
          7.3 Elements Structure Definition: Elements_t

-For face elements in 3-D, or bar element in 2-D, additonal data may be provided +For face elements in 3-D, or bar element in 2-D, additional data may be provided for each element in ParentElements and ParentElementsPosition. The element numbers of the two adjacent cells for each face are given in ParentElements. The corresponding canonical positions of the face in the @@ -1212,7 +1212,7 @@

7.7 Flow Solution Structure Definition: FlowSolution_t

For structured grids, the value of GridLocation alone specifies the -location and indexing of the flow solution data. Vertices are explicity indexed. +location and indexing of the flow solution data. Vertices are explicitly indexed. Cell centers and face centers are indexed using the minimum of the connecting vertex indices, as described in the section Structured Grid Notation and Indexing Conventions. @@ -1502,7 +1502,7 @@

Example - Flow Solution

rather than attaching the appropriate DataClass and DimensionalUnits to each DataArray_t entity. -It could possibly be at even higher levels in the heirarchy. +It could possibly be at even higher levels in the hierarchy. The contents of DataConversion are in each case the denominator of the normalization; this is ρ∞ diff --git a/CGNS_docs_current/sids/misc.html b/CGNS_docs_current/sids/misc.html index f6fca132..58caf666 100644 --- a/CGNS_docs_current/sids/misc.html +++ b/CGNS_docs_current/sids/misc.html @@ -468,7 +468,7 @@

12.4 Discrete Data Structure Definition: DiscreteData_t

For structured grids, the value of GridLocation alone specifies the -location and indexing of the discrete. Vertices are explicity indexed. +location and indexing of the discrete. Vertices are explicitly indexed. Cell centers and face centers are indexed using the minimum of the connecting vertex indices, as described in the section Structured Grid Notation and Indexing Conventions. diff --git a/CGNS_docs_current/sids/timedep.html b/CGNS_docs_current/sids/timedep.html index 896a3d74..1f059772 100644 --- a/CGNS_docs_current/sids/timedep.html +++ b/CGNS_docs_current/sids/timedep.html @@ -58,7 +58,7 @@

11 Time-Dependent Flow

This section describes structure types intended primarily for time-dependent flows. Data structures are presented for storing time-dependent or iterative -data, and for recording rigid and arbitary grid motion. +data, and for recording rigid and arbitrary grid motion. The section concludes with several examples. diff --git a/CGNS_docs_current/slides/POINOT_tutorial.html b/CGNS_docs_current/slides/POINOT_tutorial.html index 2eabe46d..6e3791f0 100644 --- a/CGNS_docs_current/slides/POINOT_tutorial.html +++ b/CGNS_docs_current/slides/POINOT_tutorial.html @@ -401,7 +401,7 @@

Workflow pre/post processing

  • Relax-NG, BNF, ... -
  • In-Memory data structre can be used for... +
  • In-Memory data structure can be used for...
    • Perform tree verification
    • Operate tree as ADT diff --git a/CGNS_docs_current/slides/VANDERWEIDE_tutorial.html b/CGNS_docs_current/slides/VANDERWEIDE_tutorial.html index 999961fd..8cc2065c 100644 --- a/CGNS_docs_current/slides/VANDERWEIDE_tutorial.html +++ b/CGNS_docs_current/slides/VANDERWEIDE_tutorial.html @@ -233,7 +233,7 @@

      Example - CGNS Code (4)

      /* Read the connectivity. Again, the node numbering of the */ /* connectivities start at 1. If internally a starting index */ - /* of 0 is used (typical for C-codes) 1 must be substracted */ + /* of 0 is used (typical for C-codes) 1 must be subtracted */ /* from the connectivities read. */ if(cg_elements_read(fileInd, base, zone, sec, conn, NULL) != CG_OK) diff --git a/CGNS_docs_current/slides/WEDAN_tutorial/fig9.html b/CGNS_docs_current/slides/WEDAN_tutorial/fig9.html index 076912b5..38a160ce 100644 --- a/CGNS_docs_current/slides/WEDAN_tutorial/fig9.html +++ b/CGNS_docs_current/slides/WEDAN_tutorial/fig9.html @@ -15,7 +15,7 @@

      This is an image of the ADFviewer main window illustrating the use of -cylindrical coordinates instead of Cartesion coordinates. +cylindrical coordinates instead of Cartesian coordinates. It shows the same node tree as described in previous figures, but with cylindrical coordinates used in the Cylinder zone. diff --git a/CGNS_docs_current/slides/cgns_8isgg.html b/CGNS_docs_current/slides/cgns_8isgg.html index c967684e..3ed80617 100644 --- a/CGNS_docs_current/slides/cgns_8isgg.html +++ b/CGNS_docs_current/slides/cgns_8isgg.html @@ -139,7 +139,7 @@

      ISO STEP Requirements

      • Record of all data sources, persistent links
      -
    • Re-Use existing data structures to full extent +
    • reuse existing data structures to full extent
      • AP203 - geometry
      • AP209 - finite element analysis diff --git a/CGNS_docs_current/whatsnew.html b/CGNS_docs_current/whatsnew.html index 8d14b02e..8c45b689 100644 --- a/CGNS_docs_current/whatsnew.html +++ b/CGNS_docs_current/whatsnew.html @@ -1633,7 +1633,7 @@

        CGNS Documentation

      • In the list of CGNS-related conference papers, added R. Magnan as an author for AIAA Paper 2005-0334. - Apologies for inadvertantly omitting him in the original update. + Apologies for inadvertently omitting him in the original update.
      19 Jan 2005 @@ -1730,7 +1730,7 @@

      CGNS Documentation

    • Removed the wording "in the same manner as grid connectivity" in the description of the BC_t node in the SIDS-to-ADF File Mapping Manual, that - was inadvertantly left in when the documentation was updated + was inadvertently left in when the documentation was updated with the release of CGNS Version 2.3.
    diff --git a/FAQs.html b/FAQs.html index 38cb4923..6cc3e716 100644 --- a/FAQs.html +++ b/FAQs.html @@ -128,7 +128,7 @@

    range of flow physics applications. However, if you find an application that is not covered, you are encouraged to utilize the "UserDefined" construct as needed. In fact, the UserDefined node can be used to create -an entire tree consisting of multilpe levels of UserDefined children nodes, +an entire tree consisting of multiple levels of UserDefined children nodes, so you can create an entire "pattern" for storing particular information. Furthermore, if you feel that a change or addition is needed to the SIDS, or if you feel that a particular "pattern" you have created @@ -325,7 +325,7 @@

    (2) Installation of CGNS from source.

    53 -

    • General product data management information for numerical analysis -results. This document will be refereced from AP 237 and Part 1xx.  +results. This document will be referenced from AP 237 and Part 1xx. 

    Integrated resource:  Numerical analysis 
    Part_53_CD_030721.pdf
      diff --git a/Proposals.html b/Proposals.html index eb91ab12..d800b5b0 100644 --- a/Proposals.html +++ b/Proposals.html @@ -91,7 +91,7 @@

    regarding changes or additions to the CGNS standard can be found in the CGNS Steering Committee Charter. -

    The CPEX should include the following informaion: +

    The CPEX should include the following information:

    • Name(s) and organization(s) of proposer(s)
    • E-mail contact information
      • @@ -698,7 +698,7 @@

      * For CPEX #0031, it should be noted that some aspects require significant modifications on the part of the MLL. For example, the improvement replaces the use of ElementRange and ElementList with PointRange and PointList. The methodology for accomplishing this while -maintaining compatability with existing CGNS files and CGNS codes must be carefully +maintaining compatibility with existing CGNS files and CGNS codes must be carefully considered prior to implementation. I.e., either the MLL must still be able to recognize, read, and translate ElementRange etc, or else ElementRange etc must still be allowed as an option (in the documentation). Therefore, this CPEX will not be added to the SIDS or Filemap documents diff --git a/ProposedExtensions/UserDefinedDataArrays2.html b/ProposedExtensions/UserDefinedDataArrays2.html index d8253f84..e177f30d 100644 --- a/ProposedExtensions/UserDefinedDataArrays2.html +++ b/ProposedExtensions/UserDefinedDataArrays2.html @@ -96,7 +96,7 @@

    • This construct easily gives a huge amount of flexibility to the user, for allowing code-specific -data to be put in the CGNS file (which is what we desparately need).
      • +data to be put in the CGNS file (which is what we desperately need).

    diff --git a/README.md b/README.md index 1fd96e6a..2e3c5e87 100644 --- a/README.md +++ b/README.md @@ -2,9 +2,9 @@ https://github.com/CGNS/cgns.github.io is new location for CGNS documentation -## Documenation Development +## Documentation Development -The CGNS documenation uses the branching/release model as summarized at: +The CGNS documentation uses the branching/release model as summarized at: http://nvie.com/posts/a-successful-git-branching-model/ diff --git a/WhatIsCGNS.html b/WhatIsCGNS.html index 2d71701b..755872ec 100644 --- a/WhatIsCGNS.html +++ b/WhatIsCGNS.html @@ -169,7 +169,7 @@

    This license is borrowed from the zlib/libpng License, -and supercedes the GNU Lesser +and supersedes the GNU Lesser General Public License (LGPL) which previously governed the use and distribution of the software.

    diff --git a/news.html b/news.html index 128cadb9..8072c785 100644 --- a/news.html +++ b/news.html @@ -88,13 +88,13 @@

  • Added CPEX43 Family hierarchy as a tree (CGNS-180).
    -

    Febuary, 2020: Version 4.0.0 of the CGNS Software is released. +

    February, 2020: Version 4.0.0 of the CGNS Software is released.

    • Added CPEX 41 NGON modification proposal (CGNS-121).
    -

    Febuary, 2020: Version 3.4.1 (patch) of the CGNS Software is released. +

    February, 2020: Version 3.4.1 (patch) of the CGNS Software is released.

    • Removed CPEX 41 NGON modification proposal (CGNS-121). @@ -129,7 +129,7 @@

      If both FFLAGS (which predates FCFLAGS) and FCFLAGS are set then FCFLAGS is ignored.
    • Replaced the hid_t to double (and vice-versa) utilities to_HDF_ID and to_ADF_ID from a type cast to a function which uses memcpy for the conversion. This is needed - for the upcomming release of HDF5 1.10 where hid_t was changed from a 32 bit integer + for the upcoming release of HDF5 1.10 where hid_t was changed from a 32 bit integer to a 64 bit integer. Should be transparent to user.
    • Implemented CPEX0039 : To enable with CGNS_ENABLE_BASE_SCOPE
    • Implemented CPEX0038 : Quadratic Elements for High Order @@ -236,7 +236,7 @@

      (suggestion from Marc Poinet), adds HTMLHelp interface to cmake scripts, fixes a compiler complaint about comparison between int and enum, and fixes Fortran detection and MPI path problems in the CMake scripts. -Compatability with version 2.5 (file type CG_FILE_ADF2) is also +Compatibility with version 2.5 (file type CG_FILE_ADF2) is also fixed for both CG_MODE_WRITE and CG_MODE_MODIFY. The CGNStools documentation has been removed from the source distribution, and is now accessed from the NASA Glenn server or a local copy (as with Version 3.2). @@ -254,7 +254,7 @@

      Multiple families (CPEX 0034), and Cubic elements (CPEX 0036). Compression (rewriting) of modified CGNS files is no longer automatically done, since this may interfere with parallel I/O. This -may be reenabled within an application with the cg_set_compress +may be re-enabled within an application with the cg_set_compress function, or done later through the CGNSview GUI or with the cgnscompress program in the tools subdirectory. Conversion programs to and from AFLR3, FAST, and TetGen have also @@ -340,7 +340,7 @@

      currently reloaded into memory to do the operations.

      March 11, 2007: Version 2.5.3 released. This version changes -the mispelled Celcius to Celsius, fixes handling of soft links when rewriting the +the misspelled Celsius to Celsius, fixes handling of soft links when rewriting the CGNS file, and fixes a number of gcc compiler warnings.

      September 11, 2007: A new instructor-led AIAA short course is being offered starting @@ -385,7 +385,7 @@

      current color scheme rather than a "Windows" type color scheme. Fixes some minor bugs and adds some improvement to the cgnscheck program. Allows reading of both HDF5 and ADF - based CGNS files (requires the adf2hdf and -hdf2adf convertor programs). +hdf2adf converter programs).

      Spring, 2006: There are two special CGNS "events" planned for the American Institute of @@ -395,7 +395,7 @@

      "CGNS Practical Applications in CFD". This will occur during the regular AIAA sessions at the conference. The second is a "CGNS Tutorial Session", currently -scheduled for Wednsday, 7 June 2006 in the evening. This +scheduled for Wednesday, 7 June 2006 in the evening. This session will be conducted in two parts: (1) Basic usage of CGNS (including examples for structured and unstructured grids), and (2) Advanced topics (tentatively including