Corrected typos in comments
Resolves bug-report https://bugs.openfoam.org/view.php?id=3017
This commit is contained in:
Henry Weller
@ -30,7 +30,7 @@ Description
|
||||
|
||||
Combusting RANS code using the b-Xi two-equation model.
|
||||
Xi may be obtained by either the solution of the Xi transport
|
||||
equation or from an algebraic exression. Both approaches are
|
||||
equation or from an algebraic expression. Both approaches are
|
||||
based on Gulder's flame speed correlation which has been shown
|
||||
to be appropriate by comparison with the results from the
|
||||
spectral model.
|
||||
|
||||
@ -30,7 +30,7 @@ Description
|
||||
|
||||
Combusting RANS code using the b-Xi two-equation model.
|
||||
Xi may be obtained by either the solution of the Xi transport
|
||||
equation or from an algebraic exression. Both approaches are
|
||||
equation or from an algebraic expression. Both approaches are
|
||||
based on Gulder's flame speed correlation which has been shown
|
||||
to be appropriate by comparison with the results from the
|
||||
spectral model.
|
||||
|
||||
@ -135,7 +135,7 @@ public:
|
||||
|
||||
// Member Functions
|
||||
|
||||
//- Return the flame-wrinking genration rate
|
||||
//- Return the flame-wrinking generation rate
|
||||
virtual tmp<volScalarField> G() const = 0;
|
||||
|
||||
//- Return the flame diffusivity
|
||||
|
||||
@ -29,7 +29,7 @@ Description
|
||||
|
||||
Combusting RANS code using the b-Xi two-equation model.
|
||||
Xi may be obtained by either the solution of the Xi transport
|
||||
equation or from an algebraic exression. Both approaches are
|
||||
equation or from an algebraic expression. Both approaches are
|
||||
based on Gulder's flame speed correlation which has been shown
|
||||
to be appropriate by comparison with the results from the
|
||||
spectral model.
|
||||
|
||||
@ -30,7 +30,7 @@ Description
|
||||
|
||||
Combusting RANS code using the b-Xi two-equation model.
|
||||
Xi may be obtained by either the solution of the Xi transport
|
||||
equation or from an algebraic exression. Both approaches are
|
||||
equation or from an algebraic expression. Both approaches are
|
||||
based on Gulder's flame speed correlation which has been shown
|
||||
to be appropriate by comparison with the results from the
|
||||
spectral model.
|
||||
|
||||
@ -47,7 +47,7 @@ Description
|
||||
v_i | Volume of mother bubble i [m]
|
||||
\epsilon_c | Turbulent dissipation rate of continuous phase [m2/s3]
|
||||
\mu_c | Molecular dynamic viscosity of liquid phase [Pa s]
|
||||
\rho_c | Density of continous phase [kg/m3]
|
||||
\rho_c | Density of continuous phase [kg/m3]
|
||||
\rho_d | Density of disperse phase [kg/m3]
|
||||
\endvartable
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ Description
|
||||
\epsilon_c | Turbulent dissipation rate of continuous phase [m2/s3]
|
||||
\alpha_d | Total void fraction of disperse phase [-]
|
||||
\mu_c | Molecular dynamic viscosity of liquid phase [Pa s]
|
||||
\rho_c | Density of continous phase [kg/m3]
|
||||
\rho_c | Density of continuous phase [kg/m3]
|
||||
\endvartable
|
||||
|
||||
References:
|
||||
|
||||
@ -88,7 +88,7 @@ Description
|
||||
\theta_{ij}^{LS} | Laminar shear collision rate [m3/s]
|
||||
\lambda_{ij} | Coalescence efficiency [-]
|
||||
r_{ij} | Equivalent radius [m]
|
||||
\rho_c | Density of continous phase [kg/m3]
|
||||
\rho_c | Density of continuous phase [kg/m3]
|
||||
\sigma | Surface tension [N/m]
|
||||
h_0 | Initial film thickness [m]
|
||||
h_f | Critical film thickness [m]
|
||||
|
||||
@ -185,7 +185,7 @@ class CV2D
|
||||
//- Keep track of the boundary conform point-pairs
|
||||
// stored after the insertion of the surface point-pairs in case
|
||||
// the boundary conform function is called more than once without
|
||||
// removing and insertin the surface point-pairs
|
||||
// removing and inserting the surface point-pairs
|
||||
label startOfBoundaryConformPointPairs_;
|
||||
|
||||
//- Store the feature points
|
||||
@ -311,7 +311,7 @@ class CV2D
|
||||
|
||||
void markNearBoundaryPoints();
|
||||
|
||||
//- Restore the Delaunay contraint
|
||||
//- Restore the Delaunay constraint
|
||||
void fast_restore_Delaunay(Vertex_handle vh);
|
||||
|
||||
// Flip operations used by fast_restore_Delaunay
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,361 +0,0 @@
|
||||
README_1.0_to_2.0
|
||||
=================
|
||||
This document exists to help those who already have a working user defined
|
||||
reader (using the 1.0 API) to change it into the 2.0 API format - if desired.
|
||||
|
||||
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:
|
||||
- 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
|
||||
- you want to provide your own "border" elements (as opposed to EnSight's
|
||||
computation of them)
|
||||
|
||||
As an indication of the differences that might be realized in efficiency,
|
||||
consider the following comparison on an unstructured model consisting of:
|
||||
|
||||
1,639,058 nodes
|
||||
7,079,211 elements 240530 tria3
|
||||
3984 quad4
|
||||
5927663 tetra4
|
||||
653 pyramid5
|
||||
906381 penta6
|
||||
|
||||
12 parts
|
||||
|
||||
The same model was represented in EnSight6 and EnSight Gold format.
|
||||
|
||||
|
||||
EnSight6 format into: EnSight Gold format into:
|
||||
------------------------------------ -------------------------
|
||||
EnSight7.1 |Ensight7.2 |Ensight 7.1 |EnSight7.2 |Ensight7.2
|
||||
internal |internal |userd reader |internal |userd reader
|
||||
reader |reader |(API 1.0) |reader |(API 2.0)
|
||||
| | | |
|
||||
Time | Mem |Time | Mem |Time | Mem |Time | Mem |Time | Mem
|
||||
(sec)| (Mb) |(sec)| (Mb) |(sec)| (Mb) |(sec)| (Mb) |(sec)| (Mb)
|
||||
----------- |----------- |----------- |----------- |-----------
|
||||
@ part 4.3 27.6 | 3.5 28.4 | 4.0 27.6 | 3.3 8.8 | 3.3 8.9
|
||||
loader | | | |
|
||||
| | | |
|
||||
after 14.0 243.4 |12.8 244.3 |49.8 475.8 | 6.0 211.5 | 6.2 211.6
|
||||
loading all | | | |
|
||||
12 parts | | | |
|
||||
(non-visual) | | | |
|
||||
| | | |
|
||||
after 16.8 263.2 |16.0 264.2 |52.8 490.7 | 9.1 236.2 | 9.5 236.2
|
||||
activate of | | | |
|
||||
a vector. | | | |
|
||||
^ ^
|
||||
/|\ /|\
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
Compare these two!
|
||||
|
||||
|
||||
Significant is the inefficiency of the 1.0 API, and the fact that the
|
||||
2.0 API has the same improved efficiency (both in speed and memory) as
|
||||
the gold internal reader!
|
||||
|
||||
Note: Structured data will not show much difference between the two API's,
|
||||
but it was more efficient initially.
|
||||
|
||||
|
||||
=========================================================
|
||||
A note on philosophical differences between the two API's:
|
||||
=========================================================
|
||||
|
||||
API 1.0 deals with:
|
||||
-------------------
|
||||
-> global coordinate array & corresponding
|
||||
-> global node id array
|
||||
-> global nodal variables
|
||||
|
||||
-> for each part:
|
||||
-> local element connectivities (grouped by type) & corresponding
|
||||
-> local element ids
|
||||
-> local elemental variables
|
||||
|
||||
|
||||
The element connectivities, within parts, reference the global coordinate
|
||||
array. If node ids are provided, the element connectivities have to be in
|
||||
terms of the node ids. If node ids are not provided, the connectivities are in
|
||||
terms of the (one-based) index number of each node in the global coordinate
|
||||
array. Thus, node ids are more than labels - they are a part of the
|
||||
connectivity referencing scheme. Element ids are purely labels.
|
||||
|
||||
This API was originally setup to try to make the interface to other codes as
|
||||
straightforward as possible. Efficiency was not the major consideration.
|
||||
|
||||
EnSight must do a fair amount of work to get data provided in the manner
|
||||
described above into the form that it uses internally. There is mapping that
|
||||
has to be setup and maintained between the global arrays and the local part
|
||||
arrays so that updating over time can be accomplished efficiently. There is
|
||||
hashing that is required in order to deal efficiently with node ids.
|
||||
|
||||
All of this leads to a considerable amount of temporary memory and processing,
|
||||
in order to get a model read into EnSight.
|
||||
|
||||
|
||||
API 2.0 deals with:
|
||||
-------------------
|
||||
-> for each part:
|
||||
-> part coordinates & corresponding
|
||||
-> part node ids
|
||||
-> part nodal variables
|
||||
|
||||
-> part element connectivities (grouped by type) & corresponding
|
||||
-> part element ids
|
||||
-> part elemental variables
|
||||
|
||||
API 2.0 requires that the coordinates and corresponding nodal variables be
|
||||
provided per part. This eliminates the global to local mapping with all its
|
||||
associated temporary memory and processing time. The connectivity of the
|
||||
elements in each part reference the node indices of its own (one-based) part
|
||||
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
|
||||
stores and manipulates information internally. The new API requests size
|
||||
information and allocates the actual internal structures and arrays
|
||||
accordingly. Pointers to these arrays are passed directly to you in the
|
||||
routines which gather data, thus eliminating a considerable amount of
|
||||
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.
|
||||
------------------------------------------------
|
||||
|
||||
|
||||
So, with that said, if you determine that you want to convert your existing
|
||||
reader to the new API format, The following may be helpful.
|
||||
|
||||
====================
|
||||
First the Good News! The following routines are identical in both API's!!
|
||||
==================== ----------------------------------------------------
|
||||
USERD_bkup
|
||||
USERD_get_block_coords_by_component
|
||||
USERD_get_block_iblanking
|
||||
USERD_get_changing_geometry_status
|
||||
USERD_get_dataset_query_file_info
|
||||
USERD_get_element_label_status
|
||||
USERD_get_name_of_reader
|
||||
USERD_get_node_label_status
|
||||
USERD_get_number_of_files_in_dataset
|
||||
USERD_get_number_of_model_parts
|
||||
USERD_get_number_of_variables
|
||||
USERD_set_filenames
|
||||
USERD_stop_part_building
|
||||
|
||||
|
||||
|
||||
========================
|
||||
Second, pretty Good News! The following routines have minor changes,
|
||||
======================== namely a slight name change and the addition
|
||||
of arguments related to complex data, constant
|
||||
(Note, the name changes type, or self contained parts vs global coords.
|
||||
are needed so both
|
||||
API's can exist together) The arguments must be added, but depending on
|
||||
your situation, many might simply be place
|
||||
holders.
|
||||
-------------------------------------------------------------------------------
|
||||
|
||||
-----------------------------------------------------
|
||||
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
|
||||
------- -------
|
||||
USERD_get_constant_value USERD_get_constant_val
|
||||
( (
|
||||
int which var int which_var,
|
||||
int imag_data
|
||||
) )
|
||||
|
||||
USERD_get_description_lines USERD_get_descrip_lines
|
||||
( (
|
||||
int which_type, int which_type,
|
||||
int which_var, int which_var,
|
||||
int imag_data,
|
||||
char line1[Z_BUFL], char line1[Z_BUFL],
|
||||
char line2[Z_BUFL] char line2[Z_BUFL]
|
||||
) )
|
||||
|
||||
USERD_get_variable_value_at_specific USERD_get_var_value_at_specific
|
||||
( (
|
||||
int which_var, int which_var,
|
||||
int which_node_or_elem, int which_node_or_elem,
|
||||
int which_part, int which_part,
|
||||
int which_elem_type, int which_elem_type,
|
||||
int time_step, int time_step,
|
||||
float values[3] float values[3],
|
||||
int imag_data
|
||||
) )
|
||||
|
||||
|
||||
---------------------------------------------------------
|
||||
B) Changes related to complex data info, and constant type
|
||||
(and some of the multiple timeset support)
|
||||
=========================================================
|
||||
If you don't deal with complex variables, simply add the
|
||||
arguments for var_complex, var_ifilename, and var_freq
|
||||
and assign var_complex to be FALSE.
|
||||
|
||||
The argument var_contran needs to be added, and set
|
||||
appropriately if you have constant variables, to indicate
|
||||
if the constant variable is fixed for all time or varies
|
||||
over time.
|
||||
|
||||
The argument var_timeset needs to be added, and set
|
||||
appropriately.
|
||||
---------------------------------------------------------
|
||||
|
||||
API 1.0 API 2.0
|
||||
------- -------
|
||||
USERD_get_variable_info USERD_get_gold_variable_info
|
||||
( (
|
||||
char **var_description, char **var_description,
|
||||
char **var_filename, char **var_filename,
|
||||
int *var_type, int *var_type,
|
||||
int *var_classify int *var_classify,
|
||||
int *var_complex,
|
||||
char **var_ifilename,
|
||||
float *var_freq,
|
||||
int *var_contran,
|
||||
int *var_timeset
|
||||
) )
|
||||
|
||||
|
||||
------------------------------------------------------
|
||||
C) Changes related to self contained part coordinates
|
||||
======================================================
|
||||
The number_of_nodes argument needs to be added and
|
||||
set for each part. This one is critical for you to do.
|
||||
------------------------------------------------------
|
||||
|
||||
API 1.0 API 2.0
|
||||
------- -------
|
||||
USERD_get_part_build_info USERD_get_gold_part_build_info
|
||||
( (
|
||||
int *part_numbers, int *part_types,
|
||||
int *part_types, int *part_types,
|
||||
char *part_description[Z_BUFL], char *part_description[Z_BUFL],
|
||||
int *number_of_nodes,
|
||||
int *number_of_elements[Z_MAXTYPE], int *number_of_elements[Z_MAXTYPE],
|
||||
int *ijk_dimensions[3], int *ijk_dimensions[3],
|
||||
int *iblanking_options[6] int *iblanking_options[6]
|
||||
) )
|
||||
|
||||
|
||||
------------------------------------------------------
|
||||
D) Changes related to multiple timeset support
|
||||
======================================================
|
||||
The timeset_number argument needs to be added for the
|
||||
following three routines.
|
||||
|
||||
The multiple timeset support also includes the change
|
||||
in B) above for USERD_get_gold_variable_info and the
|
||||
last three new routines in the third section of this
|
||||
readme file.
|
||||
------------------------------------------------------
|
||||
|
||||
API 1.0 API 2.0
|
||||
------- -------
|
||||
USERD_get_number_of_time_steps USERD_get_num_of_time_steps
|
||||
( (
|
||||
void int timeset_number
|
||||
) )
|
||||
|
||||
USERD_get_solution_times USERD_get_sol_times
|
||||
( (
|
||||
int timeset_number,
|
||||
float *solution_times float *solution_times
|
||||
) )
|
||||
|
||||
USERD_set_time_step USERD_set_time_set_and_step
|
||||
( (
|
||||
int timeset_number,
|
||||
int time_step int time_step
|
||||
) )
|
||||
|
||||
|
||||
------------------------------------------------------
|
||||
E) Changes related to global_extern.h
|
||||
======================================================
|
||||
|
||||
Be sure to include the updated global_extern.h file that comes
|
||||
with the EnSight 7.2 release (not the one from previous releases).
|
||||
|
||||
|
||||
|
||||
|
||||
=================================================================
|
||||
Third, deleted and new routines. (Here is where the work lies)
|
||||
|
||||
Several old routines are gone. You will have to create the new
|
||||
routines that replace them. I think you will find in most cases
|
||||
that your old routines will form the basis of the new routines,
|
||||
and that it isn't too difficult to provide the information in
|
||||
the new way.
|
||||
|
||||
The detailed specifications for these new routines can be found
|
||||
in README_USERD_2.0 (or the headers in libuserd.c of the
|
||||
dummy_gold or ensight_gold readers).
|
||||
=================================================================
|
||||
|
||||
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
|
||||
|
||||
These global coordinate routines: replaced by part coord routines:
|
||||
--------------------------------- --------------------------------
|
||||
USERD_get_global_coords USERD_get_part_coords
|
||||
USERD_get_global_node_ids USERD_get_part_node_ids
|
||||
USERD_get_number_of_global_nodes
|
||||
|
||||
These part connectivity routines: replaced by part by type routines:
|
||||
--------------------------------- ----------------------------------
|
||||
USERD_get_element_connectivities_for_part USERD_get_part_elements_by_type
|
||||
USERD_get_element_ids_for_part USERD_get_part_element_ids_by_type
|
||||
|
||||
|
||||
These are New Routines
|
||||
----------------------
|
||||
(Can be a dummy) -> USERD_exit_routine
|
||||
(Can be a dummy) -> USERD_get_model_extents
|
||||
(Required) -> USERD_get_reader_version
|
||||
|
||||
multiple timeset related:
|
||||
(Required) -> USERD_get_number_timesets
|
||||
(Required) -> USERD_get_timeset_description
|
||||
(Required) -> USERD_get_geom_timeset_number
|
||||
|
||||
border provided by the reader option:
|
||||
(Required) -> USERD_get_border_availability
|
||||
(Can be a dummy) -> USERD_get_border_elements_by_type
|
||||
|
||||
transient model allocation efficiency:
|
||||
(Can be a dummy) -> USERD_get_maxsize_info
|
||||
|
||||
Possible use with Server-of-Servers:
|
||||
(Can be a dummy) -> USERD_set_server_number
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -7,7 +7,7 @@ int USERD_get_number_of_files_in_dataset(void)
|
||||
Info<< "Entering: USERD_get_number_of_files_in_dataset" << endl << flush;
|
||||
#endif
|
||||
|
||||
// use 1 insted of 0 which gives an un-necessary warning.
|
||||
// use 1 instead of 0 which gives an un-necessary warning.
|
||||
Num_dataset_files = 1;
|
||||
return Num_dataset_files;
|
||||
}
|
||||
|
||||
@ -120,7 +120,7 @@ label collapseEdge(triSurface& surf, const scalar minLen)
|
||||
pointMap[v1] = v;
|
||||
newPoints[v] = 0.5*(localPoints[v1] + localPoints[v]);
|
||||
|
||||
// Pout<< "Collapsing triange " << facei
|
||||
// Pout<< "Collapsing triangle " << facei
|
||||
// << " to edge mid " << newPoints[v] << endl;
|
||||
|
||||
nCollapsed++;
|
||||
|
||||
@ -444,7 +444,7 @@ checkBanner()
|
||||
done
|
||||
)
|
||||
|
||||
dieOnBadFiles "Fix banner formating before pushing"
|
||||
dieOnBadFiles "Fix banner formatting before pushing"
|
||||
}
|
||||
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@
|
||||
# - illegal code, e.g. <TAB>
|
||||
# - columns greater than 80 for *.[CH] files
|
||||
# - non-standard code patterns
|
||||
# - missmatched header #ifndef/#define names
|
||||
# - mismatched header #ifndef/#define names
|
||||
# - incorrect copyright statements
|
||||
#
|
||||
# Note
|
||||
|
||||
@ -40,8 +40,8 @@ Description
|
||||
Springer-Verlag, Berlin.
|
||||
\endverbatim
|
||||
|
||||
This method embedds the 4-th order integration step into the 5-th order step
|
||||
and allows to perform an adapdive step-size control using these two order
|
||||
This method embeds the 4-th order integration step into the 5-th order step
|
||||
and allows to perform an adaptive step-size control using these two order
|
||||
without the need of re-evaluation.
|
||||
|
||||
SourceFiles
|
||||
|
||||
@ -189,7 +189,7 @@ void Foam::Pstream::combineScatter
|
||||
// Get my communication order
|
||||
const UPstream::commsStruct& myComm = comms[UPstream::myProcNo(comm)];
|
||||
|
||||
// Reveive from up
|
||||
// Receive from up
|
||||
if (myComm.above() != -1)
|
||||
{
|
||||
if (contiguous<T>())
|
||||
@ -438,7 +438,7 @@ void Foam::Pstream::listCombineScatter
|
||||
// Get my communication order
|
||||
const UPstream::commsStruct& myComm = comms[UPstream::myProcNo(comm)];
|
||||
|
||||
// Reveive from up
|
||||
// Receive from up
|
||||
if (myComm.above() != -1)
|
||||
{
|
||||
if (contiguous<T>())
|
||||
@ -672,7 +672,7 @@ void Foam::Pstream::mapCombineScatter
|
||||
// Get my communication order
|
||||
const UPstream::commsStruct& myComm = comms[UPstream::myProcNo(comm)];
|
||||
|
||||
// Reveive from up
|
||||
// Receive from up
|
||||
if (myComm.above() != -1)
|
||||
{
|
||||
IPstream fromAbove
|
||||
|
||||
@ -156,7 +156,7 @@ void Pstream::scatter
|
||||
// Get my communication order
|
||||
const commsStruct& myComm = comms[UPstream::myProcNo(comm)];
|
||||
|
||||
// Reveive from up
|
||||
// Receive from up
|
||||
if (myComm.above() != -1)
|
||||
{
|
||||
if (contiguous<T>())
|
||||
|
||||
@ -230,7 +230,7 @@ void Pstream::scatterList
|
||||
// Get my communication order
|
||||
const commsStruct& myComm = comms[UPstream::myProcNo(comm)];
|
||||
|
||||
// Reveive from up
|
||||
// Receive from up
|
||||
if (myComm.above() != -1)
|
||||
{
|
||||
const labelList& notBelowLeaves = myComm.allNotBelow();
|
||||
|
||||
@ -2138,7 +2138,7 @@ bool Foam::fileOperations::masterUncollatedFileOperation::read
|
||||
const Pstream::commsStruct& myComm =
|
||||
comms[Pstream::myProcNo(Pstream::worldComm)];
|
||||
|
||||
// Reveive from up
|
||||
// Receive from up
|
||||
if (myComm.above() != -1)
|
||||
{
|
||||
IPstream fromAbove
|
||||
|
||||
@ -642,7 +642,7 @@ bool Foam::fileOperations::uncollatedFileOperation::read
|
||||
);
|
||||
const Pstream::commsStruct& myComm = comms[Pstream::myProcNo()];
|
||||
|
||||
// Reveive from up
|
||||
// Receive from up
|
||||
if (myComm.above() != -1)
|
||||
{
|
||||
IPstream fromAbove
|
||||
|
||||
@ -127,7 +127,7 @@ void Foam::GAMGSolver::agglomerateMatrix
|
||||
const boolList& faceFlipMap =
|
||||
agglomeration_.faceFlipMap(fineLevelIndex);
|
||||
|
||||
// Check if matrix is asymetric and if so agglomerate both upper
|
||||
// Check if matrix is asymmetric and if so agglomerate both upper
|
||||
// and lower coefficients ...
|
||||
if (fineMatrix.hasLower())
|
||||
{
|
||||
|
||||
@ -25,7 +25,7 @@ Class
|
||||
Foam::smoothSolver
|
||||
|
||||
Description
|
||||
Iterative solver for symmetric and asymetric matrices which uses a
|
||||
Iterative solver for symmetric and asymmetric matrices which uses a
|
||||
run-time selected smoother e.g. GaussSeidel to converge the solution to
|
||||
the required tolerance.
|
||||
|
||||
|
||||
@ -280,7 +280,7 @@ bool Foam::polyMesh::checkEdgeAlignment
|
||||
// Check 1D/2Dness of edges. Gets passed the non-empty directions and
|
||||
// checks all edges in the mesh whether they:
|
||||
// - have no component in a non-empty direction or
|
||||
// - are only in a singe non-empty direction.
|
||||
// - are only in a single non-empty direction.
|
||||
// Empty direction info is passed in as a vector of labels (synchronised)
|
||||
// which are 1 if the direction is non-empty, 0 if it is.
|
||||
|
||||
|
||||
@ -87,7 +87,7 @@ public:
|
||||
inline labelRange();
|
||||
|
||||
//- Construct a range
|
||||
// A negative size is autmatically changed to zero.
|
||||
// A negative size is automatically changed to zero.
|
||||
inline labelRange(const label start, const label size);
|
||||
|
||||
//- Construct from Istream.
|
||||
|
||||
@ -25,7 +25,7 @@ Class
|
||||
Foam::compressible::alphatWallFunctionFvPatchScalarField
|
||||
|
||||
Description
|
||||
This boundary condition provides a turbulent thermal diffusivity conditon
|
||||
This boundary condition provides a turbulent thermal diffusivity condition
|
||||
when using wall functions
|
||||
- replicates OpenFOAM v1.5 (and earlier) behaviour
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ Class
|
||||
|
||||
Description
|
||||
This boundary condition provides a turbulent kinematic viscosity for
|
||||
atmospheric velocity profiles. It is desinged to be used in conjunction
|
||||
atmospheric velocity profiles. It is designed to be used in conjunction
|
||||
with the atmBoundaryLayerInletVelocity boundary condition. The values
|
||||
are calculated using:
|
||||
|
||||
|
||||
@ -137,7 +137,7 @@ public:
|
||||
|
||||
// Constructors
|
||||
|
||||
//- Create a writer obejct
|
||||
//- Create a writer object
|
||||
meshWriter
|
||||
(
|
||||
const polyMesh&,
|
||||
|
||||
@ -427,7 +427,7 @@ void Foam::attachDetach::setRefinement(polyTopoChange& ref) const
|
||||
else
|
||||
{
|
||||
FatalErrorInFunction
|
||||
<< "Requested attach/detach event and currect state "
|
||||
<< "Requested attach/detach event and current state "
|
||||
<< "is not known."
|
||||
<< abort(FatalError);
|
||||
}
|
||||
|
||||
@ -2017,7 +2017,7 @@ bool Foam::cellCuts::validLoop
|
||||
|
||||
if (meshFacei == -1)
|
||||
{
|
||||
// Can't find face. Ilegal.
|
||||
// Can't find face. Illegal.
|
||||
return false;
|
||||
}
|
||||
}
|
||||
|
||||
@ -324,7 +324,7 @@ public:
|
||||
// edges that need to be collapsed in order to remove these faces.
|
||||
// Also returns a map of new locations for points that will move
|
||||
// as a result of the collapse.
|
||||
// Use in conjuctions with edgeCollapser to synchronise the
|
||||
// Use in conjunctions with edgeCollapser to synchronise the
|
||||
// collapses and modify the mesh
|
||||
labelPair markSmallSliverFaces
|
||||
(
|
||||
|
||||
@ -29,7 +29,7 @@ Description
|
||||
condition as a base.
|
||||
|
||||
The jump is specified as a \c Function1 type, to enable the use of, e.g.
|
||||
contant, polynomial, table values.
|
||||
constant, polynomial, table values.
|
||||
|
||||
Usage
|
||||
\table
|
||||
|
||||
@ -25,7 +25,7 @@ Class
|
||||
Foam::outletMappedUniformInletFvPatchField
|
||||
|
||||
Description
|
||||
This boundary conditon averages the field over the "outlet" patch specified
|
||||
This boundary condition averages the field over the "outlet" patch specified
|
||||
by name "outletPatch" and applies this as the uniform value of the field
|
||||
over this patch.
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ Class
|
||||
Foam::fv::cellSetOption
|
||||
|
||||
Description
|
||||
Cell-set options abtract base class. Provides a base set of controls,
|
||||
Cell-set options abstract base class. Provides a base set of controls,
|
||||
e.g.:
|
||||
\verbatim
|
||||
type scalarExplicitSource // Source type
|
||||
|
||||
@ -66,7 +66,7 @@ Foam::scalar Foam::seriesProfile::evaluateLift
|
||||
forAll(values, i)
|
||||
{
|
||||
// note: first contribution always zero since sin(0) = 0, but
|
||||
// keep zero base to be consitent with drag coeffs
|
||||
// keep zero base to be consistent with drag coeffs
|
||||
result += values[i]*sin(i*xIn);
|
||||
}
|
||||
|
||||
|
||||
@ -361,7 +361,7 @@ public:
|
||||
"celli tetFacei tetPti facei stepFraction origProc origId"
|
||||
);
|
||||
|
||||
//- Cumulative particle counter - used to provode unique ID
|
||||
//- Cumulative particle counter - used to provide unique ID
|
||||
static label particleCount_;
|
||||
|
||||
|
||||
|
||||
@ -652,7 +652,7 @@ void Foam::KinematicCloud<CloudType>::scaleSources()
|
||||
template<class CloudType>
|
||||
void Foam::KinematicCloud<CloudType>::preEvolve()
|
||||
{
|
||||
// force calculaion of mesh dimensions - needed for parallel runs
|
||||
// force calculation of mesh dimensions - needed for parallel runs
|
||||
// with topology change due to lazy evaluation of valid mesh dimensions
|
||||
label nGeometricD = mesh_.nGeometricD();
|
||||
|
||||
|
||||
@ -132,7 +132,7 @@ public:
|
||||
//- Return const access to the reset on write flag
|
||||
inline const Switch& resetOnWrite() const;
|
||||
|
||||
//- Rerurn the table of number of times a particle has hit a face
|
||||
//- Return the table of number of times a particle has hit a face
|
||||
inline const hitTableType& faceHitCounter() const;
|
||||
|
||||
//- Return const access to the cloud
|
||||
|
||||
@ -2183,7 +2183,7 @@ void Foam::medialAxisMeshMover::movePoints(const pointField& p)
|
||||
// Update motionSmoother for new geometry
|
||||
meshMover_.movePoints();
|
||||
|
||||
// Assume corrent mesh location is correct
|
||||
// Assume current mesh location is correct
|
||||
meshMover_.correct();
|
||||
}
|
||||
|
||||
|
||||
@ -2903,7 +2903,7 @@ Foam::surfaceLocation Foam::triSurfaceTools::trackToEdge
|
||||
// Start point is inside triangle. Trivial cases already handled
|
||||
// above.
|
||||
|
||||
// end point is on edge or point so cross currrent triangle to
|
||||
// end point is on edge or point so cross current triangle to
|
||||
// see which edge is cut.
|
||||
|
||||
nearest = cutEdge
|
||||
|
||||
@ -75,14 +75,14 @@ public:
|
||||
|
||||
// Selectors
|
||||
|
||||
//- Read (optionallly from absolute path) & register on mesh
|
||||
//- Read (optionally from absolute path) & register on mesh
|
||||
static const decompositionModel& New
|
||||
(
|
||||
const polyMesh& mesh,
|
||||
const fileName& decompDictFile = ""
|
||||
);
|
||||
|
||||
//- Read (optionallly from supplied dictionary) & register on mesh
|
||||
//- Read (optionally from supplied dictionary) & register on mesh
|
||||
static const decompositionModel& New
|
||||
(
|
||||
const polyMesh& mesh,
|
||||
|
||||
@ -210,7 +210,7 @@ private:
|
||||
|
||||
// Surface redistribution
|
||||
|
||||
//- Finds new bounds based on an indepedent decomposition.
|
||||
//- Finds new bounds based on an independent decomposition.
|
||||
List<List<treeBoundBox>> independentlyDistributedBbs
|
||||
(
|
||||
const triSurface&
|
||||
|
||||
@ -29,7 +29,7 @@ Description
|
||||
Temperature dependent contact angle force with a stochastic perturbation
|
||||
|
||||
The contact angle in degrees is specified as a Foam::Function1 type, to
|
||||
enable the use of, e.g. contant, polynomial, table values and the
|
||||
enable the use of, e.g. constant, polynomial, table values and the
|
||||
stochastic perturbation obtained from a
|
||||
Foam::distributionModels::distributionModel
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ Description
|
||||
Temperature dependent contact angle force
|
||||
|
||||
The contact angle in degrees is specified as a Foam::Function1 type, to
|
||||
enable the use of, e.g. contant, polynomial, table values.
|
||||
enable the use of, e.g. constant, polynomial, table values.
|
||||
|
||||
See also
|
||||
Foam::regionModels::surfaceFilmModels::contactAngleForce
|
||||
|
||||
@ -626,7 +626,7 @@ Foam::meshToMesh::mapTgtToSrc
|
||||
|
||||
PtrList<fvPatchField<Type>> srcPatchFields(srcBm.size());
|
||||
|
||||
// constuct src boundary patch types as copy of 'field' boundary types
|
||||
// construct src boundary patch types as copy of 'field' boundary types
|
||||
// note: this will provide place holders for fields with additional
|
||||
// entries, but these values will need to be reset
|
||||
forAll(srcPatchID_, i)
|
||||
|
||||
@ -297,7 +297,7 @@ Foam::chemistryTabulationMethods::ISAT<CompType, ThermoType>::cleanAndBalance()
|
||||
bool treeModified(false);
|
||||
|
||||
// Check all chemPoints to see if we need to delete some of the chemPoints
|
||||
// according to the ellapsed time and number of growths
|
||||
// according to the elapsed time and number of growths
|
||||
chemPointISAT<CompType, ThermoType>* x = chemisTree_.treeMin();
|
||||
while(x != nullptr)
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user