Differences

This shows you the differences between two versions of the page.

--- commit:2020:01_07 [2020/01/06 15:41] – created laruelle
+++ commit:2020:01_07 [2020/03/10 09:25] – [Description] laruelle
@@ Line 1: / Line 1: @@
-====== Commit 2019-01-06 ======
+====== Commit 2019-01-07 ======
 ===== Description =====
 **Bug Fix in the additiveManager routine:**
@@ Line 8: / Line 8: @@
 ) They are given to pointAdditiveManager via pointAdditiveManager.addBoundaryCondition(BC)
 ) They are not on the edge of the geometry in the "to be activated" area.
@@ Line 16: / Line 17: @@
 **Creation of lagamine mesh importer (only for BLZ2T lagamine elements with CONRA lagamine BCs)**
-I created a Lagamine mesh importer, although it only works for 2 specific types of Lagamine elements at the moment. The importer is situated in toolbox\lag2py.py . The importer reads the "testName.lag" source file and translates it into a metafor input file "testName_lag.py".
+I created a Lagamine geometry importer, although it only works for 2 specific types of Lagamine elements at the moment. The importer is situated in toolbox\lag2py.py . The importer reads the "testName.lag" source file and translates the geometry in a metafor input file "testName_lag.py".
 More specifically:
-  *  The nodes are all created respecting their numbering in the lagamine file. The Thermal initial condition is also set.
+  *  The geometry (points/lines/quads) is created. The point numbering is the same as in the lagamine file. The initial temperature is also set at each point.
-  * The nodes are all sorted into metafor groups, 1 group per lagamine material law respecting the lagamine material law number.
+  * The points are all sorted into metafor groups, 1 group per lagamine material law respecting the lagamine material law number. This allows to push this group in a FieldApplicator to created all elements.
-  * For each of the CONRA boundary condition, a list of metafor groups is created, 1 group = 1 element.
+  * For each of the CONRA boundary conditions, a list of metafor groups is created, 1 group = 2 points connecting a CONRA element. This allows to push those groups in a LoadingInteraction to create boundary condition elements.
 For an example of use, check additiveM\withAm\tests\HashemiAndJardin\jardin.py