PhParAdapt/Simmetrix - Revision history

Jrwrigh: Jrwrigh moved page PhParAdapt-Simmetrix to PhParAdapt/Simmetrix: Move to a subpage organization

2022-09-18T18:26:31Z

Jrwrigh moved page PhParAdapt-Simmetrix to PhParAdapt/Simmetrix: Move to a subpage organization

Jopo9795: /* Creating Initial Restart and Error Files */

2021-11-09T17:55:40Z

‎Creating Initial Restart and Error Files

Jopo9795: /* Creating Initial Restart and Error Files */

2021-07-14T16:10:40Z

‎Creating Initial Restart and Error Files

Jopo9795: /* Initial Notes to User */

2021-04-28T22:50:55Z

‎Initial Notes to User

Jopo9795: /* Creating Initial Restart and Error Files */

2021-04-28T20:20:52Z

‎Creating Initial Restart and Error Files

Jopo9795: /* Initial Notes to User */

2021-04-28T20:19:36Z

‎Initial Notes to User

Jopo9795: /* Initial Notes to User */

2021-04-28T20:18:04Z

‎Initial Notes to User

Jopo9795: /* Initial Notes to User */

2021-04-28T20:17:41Z

‎Initial Notes to User

Jopo9795: /* Generate Restart File for Refined Mesh */

2021-04-28T20:17:10Z

‎Generate Restart File for Refined Mesh

Jopo9795: /* Performing the Adaptation Step */

2021-04-28T20:08:29Z

‎Performing the Adaptation Step

@@ Line 28: / Line 28: @@
 <code>mpirun -np 1 /projects/tools/Simmetrix.develop_19/phParAdapt-Sim/phParAdapt-Sim19/bin/x86_64_linux/phParAdapt-parasolid-openmpi-O 2>&1 | tee phParAdapt.log</code>
-If the above step fails, review the 'MeshSim.#.log' file that is produced to identify the error. One error related to analysis attributes has been experienced. Removing all attributes other than an initial temperature attribute in Simmodeler and then recreating the soft links in the above step fixed this issue.
+If the above step fails, review the 'MeshSim.#.log' file that is produced to identify the error. One error related to analysis attributes has been experienced. The issue was found to be that under the 'Analysis attributes' section, on the 'problem definition' line the name must be set to 'geom'.
 After completion, the 1-procs_case and mesh_parts.sms directories should now be present. If a solution has already been generated for a different mesh on the same geometry, it can now be interpolated onto the new restart.<#>.1 file that was generated. If no solution exists, run Phasta using this restart file until the desired solution state has been achieved. Be sure to set <code>Print Error Indicators: True</code> in the solver.inp file so the error fields are saved in the final restart file. Note, error fields are not printed in intermediate restart files. Before proceeding, check that the error fields exist using <code>grep -a " : <" restart.<#>.1</code>

← Older revision		Revision as of 16:10, 14 July 2021
Line 28:		Line 28:
	<code>mpirun -np 1 /projects/tools/Simmetrix.develop_19/phParAdapt-Sim/phParAdapt-Sim19/bin/x86_64_linux/phParAdapt-parasolid-openmpi-O 2>&1 \| tee phParAdapt.log</code>		<code>mpirun -np 1 /projects/tools/Simmetrix.develop_19/phParAdapt-Sim/phParAdapt-Sim19/bin/x86_64_linux/phParAdapt-parasolid-openmpi-O 2>&1 \| tee phParAdapt.log</code>

		+	If the above step fails, review the 'MeshSim.#.log' file that is produced to identify the error. One error related to analysis attributes has been experienced. Removing all attributes other than an initial temperature attribute in Simmodeler and then recreating the soft links in the above step fixed this issue.

	After completion, the 1-procs_case and mesh_parts.sms directories should now be present. If a solution has already been generated for a different mesh on the same geometry, it can now be interpolated onto the new restart.<#>.1 file that was generated. If no solution exists, run Phasta using this restart file until the desired solution state has been achieved. Be sure to set <code>Print Error Indicators: True</code> in the solver.inp file so the error fields are saved in the final restart file. Note, error fields are not printed in intermediate restart files. Before proceeding, check that the error fields exist using <code>grep -a " : <" restart.<#>.1</code>		After completion, the 1-procs_case and mesh_parts.sms directories should now be present. If a solution has already been generated for a different mesh on the same geometry, it can now be interpolated onto the new restart.<#>.1 file that was generated. If no solution exists, run Phasta using this restart file until the desired solution state has been achieved. Be sure to set <code>Print Error Indicators: True</code> in the solver.inp file so the error fields are saved in the final restart file. Note, error fields are not printed in intermediate restart files. Before proceeding, check that the error fields exist using <code>grep -a " : <" restart.<#>.1</code>

@@ Line 7: / Line 7: @@
 *** Extruded element types apparently can be used but require removal of any extrusion constraints in the mesh. Below are some incomplete details regarding that process for reference. See  [[#Removal_of_Extrusion_Constraint |Removal of Extrusion Constraint]].
 ** Serial case
-** Geometries created using SimModeler7.0-190626
+** Geometries created using SimModeler7.0-190604
 ** The version of phParAdapt noted here uses only the 6th entry of the error field for identifying regions for adaptation

@@ Line 22: / Line 22: @@
 ln -s ../../geom_nat.x_t </nowiki>
-Create an <code> adapt.inp </code> using the template [[#Adapt.inp_(non-adaptation_step) | Adapt.inp (non-adaptation step)]]. Keep <code>adaptFlag</code> set to zero as the purpose of running phParAdapt here is to create restart.<timeStepNumber>.1 file associated with a new mesh format that can be used for adaptation.
+Create an <code>adapt.inp</code> file using the template [[#Adapt.inp_(non-adaptation_step) | Adapt.inp (non-adaptation step)]]. Keep <code>adaptFlag</code> set to zero as the purpose of running phParAdapt here is to create restart.<timeStepNumber>.1 file associated with a new mesh format that can be used for adaptation.
 Run phParAdapt in this directory, which for this specific example was:

@@ Line 8: / Line 8: @@
 ** Serial case
 ** Geometries created using SimModeler7.0-190626
-** Adaptation using 6th entry of the error field
+** The version of phParAdapt noted here uses only the 6th entry of the error field for identifying regions for adaptation
 == Adaptation Process ==

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

@@ Line 2: / Line 2: @@
 == Initial Notes to User ==
-* The solution migration feature is currently broken and thus requires other means for transferring the solution to new meshes that are created from PhParAdapt (e.g. solution interpolation in Paraview)
+* The solution migration feature is currently broken and thus requires other means for transferring the solution to new meshes that are created from phParAdapt (e.g. solution interpolation in Paraview)
 * To date, the steps described herein have only been tried with the following restrictions:
 ** Tetrahedral elements

@@ Line 58: / Line 58: @@
 cp ../../../adapt.inp .</nowiki>
-Note that in the above, the adapt.inp file from the non-adaptation step was copied into the current directory.
+In the above list of commands, the adapt.inp file from the non-adaptation step was copied into the current directory. Run phParAdapt using the same mpirun command as above to generate the 1-procs_case folder and the new restart file with the refined mesh. Again, since the solution migration feature is not working, the restart file will contain the initial solution and no error fields. A previously obtained solution can now be interpolated to the newly created one or PHASTA can be run in this directory to obtain a solution on the new mesh.
 == File Examples ==

@@ Line 46: / Line 46: @@
 Create an adapt.inp file using [[#Adapt.inp_(adaptation step) |Adapt.inp_(adaptation step)]] as a template. Change the <code>timeStepNumber</code> parameter to correspond to the restart file that was linked into the current directory. Make sure the <code>adaptFlag</code> parameter is set to one and change additional threshold flags to control the result of the refinement.
-Run phParAdapt with the following command,
+Run phParAdapt using the mpirun command from the previous section. A directory corresponding to the <code>timeStepNumber</code> parameter should have been created with a mesh_parts.sms folder inside upon successful completion.
 === Generate Restart File for Refined Mesh ===