Chef/Mesh Partitioning - Revision history

Prte0550: /* Documentation */

2023-02-03T20:37:34Z

‎Documentation

Prte0550: /* Documentation */

2023-02-03T20:35:56Z

‎Documentation

Prte0550: Added link to documentation

2023-02-03T19:11:01Z

Added link to documentation

Jrwrigh: Jrwrigh moved page Chef: Mesh Partitioning to Chef/Mesh Partitioning: Move to a subpage organization

2022-09-18T18:04:44Z

Jrwrigh moved page Chef: Mesh Partitioning to Chef/Mesh Partitioning: Move to a subpage organization

Jrwrigh at 22:02, 13 July 2020

2020-07-13T22:02:18Z

Jopa6460 at 02:28, 6 November 2019

2019-11-06T02:28:32Z

Jopa6460 at 02:27, 6 November 2019

2019-11-06T02:27:56Z

Jopa6460: Changed axissymmetry flag to axisymmetry in adapt.inp

2018-11-06T23:35:38Z

Changed axissymmetry flag to axisymmetry in adapt.inp

Mrasquin: /* Updated Chef version (2015/05/29 and 2016/04/05) */

2016-04-05T21:23:01Z

‎Updated Chef version (2015/05/29 and 2016/04/05)

Mrasquin: /* Updated Chef version (2015/05/29 and 2016/04/05) */

2016-04-05T21:17:00Z

‎Updated Chef version (2015/05/29 and 2016/04/05)

@@ Line 18: / Line 18: @@
 = Documentation =
-General documentation of Chef that may be used in supplement to this page is available [https://github.com/SCOREC/core/wiki/chef-partition-control|here]
+General documentation of Chef that may be used in supplement to this page is available [https://github.com/SCOREC/core/wiki/chef-partition-control here]
 = Initial tutorial =

@@ Line 18: / Line 18: @@
 = Documentation =
-General documentation of Chef that may be used in supplement to this page is available [[https://github.com/SCOREC/core/wiki/chef-partition-control|here]]
+General documentation of Chef that may be used in supplement to this page is available [https://github.com/SCOREC/core/wiki/chef-partition-control|here]
 = Initial tutorial =

@@ Line 16: / Line 16: @@
 The testcase to demonstrate the workflow is the familiar 3-way subchannel flow. The root path of this test case is	/sgidata2/mrasquin/Models/subchannel. The parasolid model is located in /sgidata2/mrasquin/Models/subchannel/convertParasolid2ParasolidNative/geomFromSimmodeler_nat.xmt_txt.
 The workflow that describes how to use Chef is now explained in the next sections.
 = Initial tutorial =

← Older revision		Revision as of 22:02, 13 July 2020
Line 313:		Line 313:
	= Words of caution=		= Words of caution=
	When working with large meshes occasionally the executable will crash by no fault of the user. This has happened in the past when (adapt.inp set parameter: ensa_ndof)*(number of nodes in the mesh)>(maximum value of the 4-byte integer 2^31). This was debugged by using the addr2line command. Information about this command can be found at https://fluid.colorado.edu/wiki/index.php/Debugging.		When working with large meshes occasionally the executable will crash by no fault of the user. This has happened in the past when (adapt.inp set parameter: ensa_ndof)*(number of nodes in the mesh)>(maximum value of the 4-byte integer 2^31). This was debugged by using the addr2line command. Information about this command can be found at https://fluid.colorado.edu/wiki/index.php/Debugging.
		+
		+	[[Category:Chef]]

@@ Line 311: / Line 311: @@
 * '''axisymmetry''': When enabled, this parameter supports axisymmetric periodic mesh and attributes for instance for an annular flow.
-== Words of caution==
+= Words of caution=
 When working with large meshes occasionally the executable will crash by no fault of the user. This has happened in the past when (adapt.inp set parameter: ensa_ndof)*(number of nodes in the mesh)>(maximum value of the 4-byte integer 2^31). This was debugged by using the addr2line command. Information about this command can be found at https://fluid.colorado.edu/wiki/index.php/Debugging.

← Older revision	Revision as of 18:04, 18 September 2022
(No difference)

← Older revision		Revision as of 02:27, 6 November 2019
Line 310:		Line 310:

	* '''axisymmetry''': When enabled, this parameter supports axisymmetric periodic mesh and attributes for instance for an annular flow.		* '''axisymmetry''': When enabled, this parameter supports axisymmetric periodic mesh and attributes for instance for an annular flow.
		+
		+	== Words of caution==
		+	When working with large meshes occasionally the executable will crash by no fault of the user. This has happened in the past when (adapt.inp set parameter: ensa_ndof)*(number of nodes in the mesh)>(maximum value of the 4-byte integer 2^31). This was debugged by using the addr2line command. Information about this command can be found at https://fluid.colorado.edu/wiki/index.php/Debugging.

← Older revision		Revision as of 23:35, 6 November 2018
Line 309:		Line 309:
	* '''filterMatches''': If set to 0, the matching between periodic entities are imposed from the mesh file regardless of the periodic faces defined in the attributes that could potentially differ. When enabled, this code derives the period associations between all model entities based on the "periodic slave" attribute set in the attribute file. Note that the mesh must be periodic to support this feature. This can be useful for instance for a three-way periodic channel mesh that can support both 1-way and 3-way periodic attributes without the need to build two distinct meshes for that purpose.		* '''filterMatches''': If set to 0, the matching between periodic entities are imposed from the mesh file regardless of the periodic faces defined in the attributes that could potentially differ. When enabled, this code derives the period associations between all model entities based on the "periodic slave" attribute set in the attribute file. Note that the mesh must be periodic to support this feature. This can be useful for instance for a three-way periodic channel mesh that can support both 1-way and 3-way periodic attributes without the need to build two distinct meshes for that purpose.

−	* '''~~axissymmetry~~''': When enabled, this parameter supports axisymmetric periodic mesh and attributes for instance for an annular flow.	+	* '''axisymmetry''': When enabled, this parameter supports axisymmetric periodic mesh and attributes for instance for an annular flow.

@@ Line 291: / Line 291: @@
 * '''Tetrahedronize''': tetrahedronize a mixed mesh if set to 1. Note that if both AdaptFlag and Tetrahedronize are set to 1, adaptation of the input mixed mesh will take place before tetrahedronization. In all cases, partitioning is always the last mesh operation. But again, an all tet mesh cannot be further refined so tetrahedronization should not take place too early in the partitioning workflow in order to get enough aggregated memory for potential future adaptation.
-* '''partitionMethod''':  Currently, the GRAPH method for local partitioning is hard coded in one of the Chef routine.
+* '''partitionMethod''':  graph or zrib (for Zoltan Recursive Inertia Bisection) are both available options so far. Graph should be preferred choice for now.
 * '''ParmaPtn''': If set to 1, the load balance in terms of both elements and vertices per part is improved further after the partitioning with Parma. It is strongly suggested to keep ParmaPtn set to 1.
 * '''dwalMigration''': This parameter is useful in case the distance to the wall for a turbulence model such as RANS or DDES has already been computed by phasta. In this case, it is possible to migrate also this field along with the solution field. SolutionMigration must therefore be set to 1 for that purpose, since the dwal field cannot be migrated alone without the solution field.

@@ Line 271: / Line 271: @@
 * '''restartFileName''': this gives the path to the restart files that needs to be read in when solution migration is activated. In this case, the path should look for instance like "../4-procs_case/restart". The phasta reader will then add the time step stamp to the name of this restartFileName variable, as well as the file #. When there is no solution migration like in this example, this parameter can be commented out for the sake of clarity.
-* '''adaptFlag''': if 0, no mesh adaptation will take place. But if set to 1 and if AdaptStrategy is set to 7, then the mesh will be uniformly refined. Note that adaptation only works with a mixed mesh (with wedges in the BL) and not with an all-tet mesh. Tetrahedronization should therefore take place after uniform refinement. Right now, the mixed mesh gets uniformly refined everywhere including the BL but it is possible to refine uniformly outside the BL only with some light modifications of the code. In the future, we hope to have other adaptation strategies in place in Chef based on local error indicator. If interested in these strategy, then phParAdapt-Simmetrix must be used. If adaptFlags is set to 1, note also that solutionMigration must be also set to 1 (see below for this parameter) and the path to the restart files specified.
+* '''adaptFlag''': if 0, no mesh adaptation will take place. But if set to 1 and if AdaptStrategy is set to 7, then the mesh will be uniformly refined.  Now, mixed mesh can be refined uniformly either everywhere including the BL, or only outside the BL (see parameter splitAllLayerEdges below). Other adaptation strategies based on local error indicators are being developed in Chef and will be complimentary to the existing strategies available in phParAdapt-Simmetrix. If adaptFlags is set to 1, note also that solutionMigration must be also set to 1 (see below for this parameter) and the path to the restart files specified.
-* '''AdaptStrategy''': This parameter is read if adaptFlat is 1. When set up to 7, uniform refinement of a mixed mesh can take place. This is currently the only strategy tested in Chef. If interested in other more sophisticated adaptation strategies, phParAdapt-Simmetrix must be used for now.
+* '''AdaptStrategy''': This parameter is read if adaptFlat is 1. When set up to 7, uniform refinement of a mixed mesh can take place. This is currently the only strategy tested and validated in Chef.
 * '''RecursiveUR''': if AdaptStrategy is set to 7, Chef offers the possibility to do recursive uniform refinement within the same job. Beware of the memory consumption if you set this value to more than 1, since the mesh can grow quickly.