Differences

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

--- doc:user:conditions:displacements [2015/01/08 11:52] – [Activation/Deactivation of boundary conditions] boman
+++ doc:user:conditions:displacements [2015/01/08 16:18] – boman
@@ Line 12: / Line 12: @@
 with
 |< 100% 8em - - >|
-|''target''          | ''GObject''  | meshed geometric entity where the displacement is imposed |
+|''target''          | ''GObject''  | meshed geometric entity where the displacement is prescribed |
-|''field''           | ''Field1D''  | variable to be fixed  |
+|''field''           | ''Field1D''  | variable to be prescribed              |
-|''ampl''            | ''float''    | amplitude |
+|''ampl''            | ''float''    | amplitude                              |
 |''fct''             | ''[[doc:user:general:fonctions|Function]]'' | function for time dependence |
 |''fctMulti'' {{:doc:user:ico-advanced.png?18|Advanced}}        | ''[[doc:user:general:fonctions|Function]]'' | (spatiotemporal dependency) |
@@ Line 21: / Line 21: @@
 The displacement is then given by
-  * INCREMENTAL_LOAD:  ''u(t1) = u(t0) + ampl * (fct(t1)-fct(t0))''
+  * ''INCREMENTAL_LOAD'':  ''u(t1) = u(t0) + ampl * (fct(t1)-fct(t0))''
-  * TOTAL_LOAD:        ''u(t) = ampl * fct(t)''
+  * ''TOTAL_LOAD'':        ''u(t) = ampl * fct(t)''
@@ Line 43: / Line 43: @@
   stages = metafor.getStageManager()
-Example : definition of a load on curve #4 and deactivation during stage #1 (corresponding to the second stage since numbers starts with 0):
+==== Example ====
-  load1 = loadingset.define(curveset(4), Field1D(TY,RE),  1.0, fct2)
+Definition of a prescribed displacement on ''Curve'' #4 and deactivation during stage #1 (corresponding to the second stage since numbering starts with 0):
+  load1 = loadingset.define(curveset(4), Field1D(TY,RE), 1.0, fct2)
   load1.deactivate(stages[1])
-Definition of a load on curve #1, deactivated during stage #1 and activated for the next ones:
+Definition of a load on ''Curve'' #1, deactivated during stage #1 and activated for the next ones:
-  load2 = loadingset.define(curveset(1), Field1D(TY,RE),  -0.1, fct1)
+  load2 = loadingset.define(curveset(1), Field1D(TY,RE), -0.1, fct1)
   load2.deactivate(stages[0])
   load2.activate(stages[1])
-These two loads are represented schematically as :
+These two loads are represented schematically as:
 |          ^  load1  ^  load2  ^
-^ phase #0 |  ACTIVE    |  INACTIVE |
+^ stage #0 |  ACTIVE    |  INACTIVE  |
-^ phase #1 |  INACTIVE  |  ACTIVE   |
+^ stage #1 |  INACTIVE  |  ACTIVE    |
-^ phase #2 |  INACTIVE  |  ACTIVE   |
+^ stage #2 |  INACTIVE  |  ACTIVE    |
-:!: Order of operations :
+<note important>Order of operations: Activation surpasses deactivation: A node can indeed be part of two entities, one activated, one deactivated. But the operation of deactivation will be done first, then the activation, so such a node will be activated.</note>
-      "Activation surpasses deactivation"
-A node can indeed be part of two entities, one activated, one deactivated. But the operation of deactivation will be done first, then the activation, so such a node will be activated.