zhyang-dev/OpenFOAM-6
1
0
Fork 0
mirror of https://github.com/OpenFOAM/OpenFOAM-6.git synced 2025-12-08 06:57:46 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Corrected spelling and typo's in comments

Browse Source 
Resolves bug report https://bugs.openfoam.org/view.php?id=2845
This commit is contained in:
Henry Weller
2018-03-05 20:14:28 +00:00
parent e08128781e
commit 1073607cb0
152 changed files with 344 additions and 343 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
applications/utilities/postProcessing/graphics/PVReaders/vtkPVblockMesh/vtkPVblockMesh.C
View File

@ -2,7 +2,7 @@
========= |
\\ / F ield | OpenFOAM: The Open Source CFD Toolbox
\\ / O peration |
\\ / A nd | Copyright (C) 2011-2017 OpenFOAM Foundation
\\ / A nd | Copyright (C) 2011-2018 OpenFOAM Foundation
\\/ M anipulation |
-------------------------------------------------------------------------------
License
@ -410,7 +410,7 @@ void Foam::vtkPVblockMesh::Update
updateFoamMesh();
reader_->UpdateProgress(0.5);
// Convert mesh elemente
// Convert mesh element
int blockNo = 0;
convertMeshCorners(output, blockNo);

2
applications/utilities/postProcessing/graphics/ensightFoamReader/README
View File

@ -902,7 +902,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
For unstructured parts, you can read them from your file if

2
applications/utilities/postProcessing/graphics/ensightFoamReader/README7
View File

@ -902,7 +902,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
For unstructured parts, you can read them from your file if

20
applications/utilities/postProcessing/graphics/ensightFoamReader/README_1.0_to_2.0
View File

@ -7,7 +7,7 @@ Note that you do not have to update your (1.0 API) user defined reader if it
is already working fine for you.
You should consider it if:
- efficieny gains are needed or
- efficiency gains are needed or
- you need access to complex variables or
- you need access to tensor variables or
- you need multiple timeset capability or
@ -120,7 +120,7 @@ coordinate array. The connectivity of the elements do not reference the nodes
according to node ids. Node ids (and element ids for that matter) are purely
labels for screen display and for query operations within EnSight. This
eliminates the need for node id hashing as a model is read.
The 2.0 API has been created for those needing more efficiency - both in terms
of memory use and speed. The increased efficiency is possible because data is
requested in a manner which more closely represents the way that EnSight
@ -132,7 +132,7 @@ temporary memory (and allocation time) that is needed in the old
API. Depending on what you must do to get your data into the form required,
the memory savings and the speed improvement when loading models can be quite
significant!!
Additionally, the ability to handle tensor and complex variables has been
added to the new API, and support for multiple timesets is provided.
------------------------------------------------
@ -176,7 +176,7 @@ A) Changes related to imaginary flag for complex data
=====================================================
If you don't deal with complex variables, simply add
this flag to your argument list and ignore its value.
-----------------------------------------------------
-----------------------------------------------------
API 1.0 API 2.0
------- -------
@ -222,7 +222,7 @@ B) Changes related to complex data info, and constant type
The argument var_timeset needs to be added, and set
appropriately.
---------------------------------------------------------
---------------------------------------------------------
API 1.0 API 2.0
------- -------
@ -297,7 +297,7 @@ USERD_set_time_step USERD_set_time_set_and_step
E) Changes related to global_extern.h
======================================================
Be sure to include the updated global_extern.h file that comes
Be sure to include the updated global_extern.h file that comes
with the EnSight 7.2 release (not the one from previous releases).
@ -323,9 +323,9 @@ API 1.0 API 2.0
These routines: replaced by the single routine:
--------------------------- -------------------------------
USERD_get_block_scalar_values USERD_get_var_by_component
USERD_get_block_vector_values_by_component
USERD_get_scalar_values
USERD_get_vector_values
USERD_get_block_vector_values_by_component
USERD_get_scalar_values
USERD_get_vector_values
These global coordinate routines: replaced by part coord routines:
--------------------------------- --------------------------------
@ -345,7 +345,7 @@ USERD_get_element_ids_for_part USERD_get_part_element_ids_by_type
(Can be a dummy) -> USERD_get_model_extents
(Required) -> USERD_get_reader_version
multiple timeset releated:
multiple timeset related:
(Required) -> USERD_get_number_timesets
(Required) -> USERD_get_timeset_description
(Required) -> USERD_get_geom_timeset_number

4
applications/utilities/postProcessing/graphics/ensightFoamReader/README_2.01_to_2.03
View File

@ -74,7 +74,7 @@ called is given.
USERD_get_number_of_materials
USERD_get_matf_var_info
For each elment type of each part containing material ids, calls:
For each element type of each part containing material ids, calls:
USERD_size_matf_data
USERD_load_matf_data
@ -1344,7 +1344,7 @@ USERD_get_gold_part_build_info
1 2 3 (I planes)
And note that if you were partioning this block for
And note that if you were partitioning this block for
EnSight's Server of Servers, you would only have one part,
instead of two. Each SOS server would return its appropriate
ranges in the last 6 slots. The first 3 slots would remain constant.

2
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_1.0
View File

@ -1063,7 +1063,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
For unstructured parts, you can read them from your file if

2
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.0
View File

@ -987,7 +987,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
For unstructured parts, you can read them from your file if

2
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.01
View File

@ -1056,7 +1056,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
* Prior to API 2.01:

6
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.03
View File

@ -470,7 +470,7 @@ called is given.
USERD_get_number_of_materials
USERD_get_matf_var_info
For each elment type of each part containing material ids, calls:
For each element type of each part containing material ids, calls:
USERD_size_matf_data
USERD_load_matf_data
@ -1081,7 +1081,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
* Prior to API 2.01:
@ -1430,7 +1430,7 @@ USERD_get_gold_part_build_info
1 2 3 (I planes)
And note that if you were partioning this block for
And note that if you were partitioning this block for
EnSight's Server of Servers, you would only have one part,
instead of two. Each SOS server would return its appropriate
ranges in the last 6 slots. The first 3 slots would remain constant.

4
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.03_CHANGES
View File

@ -74,7 +74,7 @@ called is given.
USERD_get_number_of_materials
USERD_get_matf_var_info
For each elment type of each part containing material ids, calls:
For each element type of each part containing material ids, calls:
USERD_size_matf_data
USERD_load_matf_data
@ -1344,7 +1344,7 @@ USERD_get_gold_part_build_info
1 2 3 (I planes)
And note that if you were partioning this block for
And note that if you were partitioning this block for
EnSight's Server of Servers, you would only have one part,
instead of two. Each SOS server would return its appropriate
ranges in the last 6 slots. The first 3 slots would remain constant.

6
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.05
View File

@ -580,7 +580,7 @@ called is given.
USERD_get_number_of_materials
USERD_get_matf_var_info
For each elment type of each part containing material ids, calls:
For each element type of each part containing material ids, calls:
USERD_size_matf_data
USERD_load_matf_data
@ -1198,7 +1198,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
* Prior to API 2.01:
@ -1547,7 +1547,7 @@ USERD_get_gold_part_build_info
1 2 3 (I planes)
And note that if you were partioning this block for
And note that if you were partitioning this block for
EnSight's Server of Servers, you would only have one part,
instead of two. Each SOS server would return its appropriate
ranges in the last 6 slots. The first 3 slots would remain constant.

6
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.06
View File

@ -550,7 +550,7 @@ called is given.
USERD_get_number_of_materials
USERD_get_matf_var_info
For each elment type of each part containing material ids, calls:
For each element type of each part containing material ids, calls:
USERD_size_matf_data
USERD_load_matf_data
@ -1168,7 +1168,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
* Prior to API 2.01:
@ -1517,7 +1517,7 @@ USERD_get_gold_part_build_info
1 2 3 (I planes)
And note that if you were partioning this block for
And note that if you were partitioning this block for
EnSight's Server of Servers, you would only have one part,
instead of two. Each SOS server would return its appropriate
ranges in the last 6 slots. The first 3 slots would remain constant.

6
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.07
View File

@ -564,7 +564,7 @@ called is given.
USERD_get_number_of_materials
USERD_get_matf_var_info
For each elment type of each part containing material ids, calls:
For each element type of each part containing material ids, calls:
USERD_size_matf_data
USERD_load_matf_data
@ -1182,7 +1182,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
* Prior to API 2.01:
@ -1531,7 +1531,7 @@ USERD_get_gold_part_build_info
1 2 3 (I planes)
And note that if you were partioning this block for
And note that if you were partitioning this block for
EnSight's Server of Servers, you would only have one part,
instead of two. Each SOS server would return its appropriate
ranges in the last 6 slots. The first 3 slots would remain constant.

6
applications/utilities/postProcessing/graphics/ensightFoamReader/README_USERD_2.08
View File

@ -568,7 +568,7 @@ called is given.
USERD_get_number_of_materials
USERD_get_matf_var_info
For each elment type of each part containing material ids, calls:
For each element type of each part containing material ids, calls:
USERD_size_matf_data
USERD_load_matf_data
@ -1186,7 +1186,7 @@ USERD_get_element_label_status
Notes:
-----
* element lables are needed in order to do any element querying, or
* element labels are needed in order to do any element querying, or
element labeling on-screen within EnSight.
* Prior to API 2.01:
@ -1535,7 +1535,7 @@ USERD_get_gold_part_build_info
1 2 3 (I planes)
And note that if you were partioning this block for
And note that if you were partitioning this block for
EnSight's Server of Servers, you would only have one part,
instead of two. Each SOS server would return its appropriate
ranges in the last 6 slots. The first 3 slots would remain constant.