Metafor

ULiege - Aerospace & Mechanical Engineering

User Tools

Site Tools

You are here: metafor.ltas.ulg.ac.be » doc » Documentation » results » Saving history curves to disk
Trace:
doc:user:results:courbes_res

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
doc:user:results:courbes_res [2017/12/01 21:41] – [Extracting values on a TransferRegion] boemerdoc:user:results:courbes_res [2022/05/02 17:04] – [Extracting values at integration points] papeleux
Line 34: Line 34:
   valuesmanager.setOnFile(False)                      # Keep curves in memory instead of writing    valuesmanager.setOnFile(False)                      # Keep curves in memory instead of writing 
                                                       # .v and .ascii files                                                       # .v and .ascii files
 +                                                      
 where  where 
  
Line 47: Line 48:
 \\ \\
  
 +
 +
 +===== FacValuesManager =====
 +
 +The ''FacValuesManager'' manages the extraction of data at each time a "bfac" file is written. It is exactly the same object as the ''ValuesManager'', but called at different times of the time integration.
 +
 +To access the ''FacValuesManager'', just get it from metafor. The rest of the syntax is the same.
 +
 +  facValuesManager = metafor.getFacValuesManager()
 +  
 +<note important>Be carefull that ThermoDynamics Fields (TdFieldValueExtractor) will give false values, as they accumulate values from each time step !!! Metafor will not prohibit the use of them (it is up to you to NOT define them).</note>
 +
 +===== StageValuesManager =====
 +
 +The ''StageValuesManager'' manages the extraction of data at the end of each stage. It is exactly the same object as the ''ValuesManager'', but called at different times of the time integration. 
 +
 +To access the ''StageValuesManager'', just get it from metafor. The rest of the syntax is the same. 
 +
 +    stageValuesManager = metafor.getStageValuesManager()
 +
 +<note important>Be carefull that ThermoDynamics Fields (TdFieldValueExtractor) will give false values, as they accumulate values from each time step !!! Metafor will not prohibit the use of them (it is up to you to NOT define them).</note>
  
 ===== ValueExtractor ===== ===== ValueExtractor =====
Line 242: Line 264:
 |              | 3D : Topological volume | |              | 3D : Topological volume |
 | ''ifield''   | [[doc:user:general:ifields|internal field]] of the element extrapolated to the node |  | ''ifield''   | [[doc:user:general:ifields|internal field]] of the element extrapolated to the node | 
-|              | ''TX'' : X coordinate|  
-|              | ''TY'' : Y coordinate| 
-|              | ''TZ'' : Z coordinate| 
- 
 :!: works, but :!::!::!: :!: works, but :!::!::!:
  
Line 261: Line 279:
 |              | 2D : Topological face |  |              | 2D : Topological face | 
 |              | 3D : Topological volume | |              | 3D : Topological volume |
-| ''ifield''   | [[doc:user:general:ifields|internal field]] of the element extrapolated to the node | +| ''ifield''   | [[doc:user:general:ifields|internal field]] of the element averaged over the element | 
  
 :!: works, but :!::!::!: :!: works, but :!::!::!:
Line 276: Line 294:
 |          | ''EXT_T''  : time | |          | ''EXT_T''  : time |
 |          | ''EXT_DT'' : time step | |          | ''EXT_DT'' : time step |
-|          | ''EXT_NT'' : number of time step | +|          | ''EXT_NT'' : time step number | 
-|          | ''EXT_ITE'' : number of mechanical iterations over a time steps | +|          | ''EXT_ITE'' : number of mechanical iterations over a time step | 
-|          | ''EXT_ITE_TH'' : number of thermal iterations over a time steps | +|          | ''EXT_ITE_TOT'' : total number of mechanical iterations (included failed steps !)| 
-|          | ''EXT_ITE_AR'' : number of iterations with updates of tangent stiffness matrix | +|          | ''EXT_ITE_TH'' : number of thermal iterations over a time step | 
-|          | ''EXT_ITE_SR'' : number of iterations with updates of tangent stiffness matrix | +|          | ''EXT_ITE_TH_TOT'' : total number of thermal iterations (included failed steps !) | 
-|          | ''EXT_ITE_LS'' : number of line-search iterations | +|          | ''EXT_ITE_AR'' : number of mechanical iterations with update of tangent stiffness matrix over a time step| 
-|          | ''EXT_ITE_ALM'' : number of augmentations | +|          | ''EXT_ITE_SR'' : number of mechanical iterations without update of tangent stiffness matrix over a time step| 
-|          | ''EXT_ITE_ALM_TOT'' : number of total augmentations (included failed steps !)| +|          | ''EXT_ITE_AR_TOT'' : total number of mechanical iterations with update of tangent stiffness matrix  (included failed steps !)| 
-|          | ''EXT_ITE_TOT'' : number of total iterations (included failed steps !)|+|          | ''EXT_ITE_SR_TOT'' : total number of mechanical iterations without update of tangent stiffness matrix  (included failed steps !)| 
 +|          | ''EXT_ITE_TH_AR'' : number of thermal iterations with update of tangent stiffness matrix over a time step | 
 +|          | ''EXT_ITE_TH_SR'' : number of thermal iterations without update of tangent stiffness matrix over a time step| 
 +|          | ''EXT_ITE_TH_AR_TOT'' : total number of thermal iterations with update of tangent stiffness matrix  (included failed steps !)| 
 +|          | ''EXT_ITE_TH_SR_TOT'' : total number of thermal iterations without update of tangent stiffness matrix  (included failed steps !)| 
 +|          | ''EXT_ITE_LS'' : number of mechanical line-search iterations over a time step | 
 +|          | ''EXT_ITE_LS_TOT'' : total number of mechanical line-search iterations (included failed steps !)| 
 +|          | ''EXT_ITE_TH_LS'' : number of thermal line-search iterations over a time step | 
 +|          | ''EXT_ITE_TH_LS_TOT'' : total number of thermal line-search iterations (included failed steps !)| 
 +|          | ''EXT_ITE_ALM'' : number of augmentations over a time step| 
 +|          | ''EXT_ITE_ALM_TOT'' : total number of augmentations (included failed steps !)|
 |          | ''EXT_RCOND'' : reciprocal condition number of the mechanical tangent stiffness matrix | |          | ''EXT_RCOND'' : reciprocal condition number of the mechanical tangent stiffness matrix |
 |          | ''EXT_VM....'' : Extractors of virtual memory (see table below) | |          | ''EXT_VM....'' : Extractors of virtual memory (see table below) |
Line 330: Line 358:
 |              | ''GEN_DIAG_MASS_FORC'' : Generalized inertial forces (diagonalized mass matrix) | |              | ''GEN_DIAG_MASS_FORC'' : Generalized inertial forces (diagonalized mass matrix) |
 |              | ''GEN_DIS_FORC'' : Generalized dissipation forces | |              | ''GEN_DIS_FORC'' : Generalized dissipation forces |
 +
 +=== InteractionGravityCenterAndMassValueExtractor ===
 +
 +Extract the time evolution of the position of the center of gravity and mass of an interaction. At each archiving step the extractor fills a four columns text file, where columns 1-3 contain x, y, and z coordinates of the center of gravity respectively, and column 4 contains the value of the mass.
 +
 +  valueExtractor = InteractionGravityCenterAndMassValueExtractor (interaction)
 +
 +where
 +  
 +''interaction'' --> Reference of an interaction.
  
 ==== Extracting values on a contact interaction ==== ==== Extracting values on a contact interaction ====
Line 411: Line 449:
 ^ Status          ^ Extracted value ^ ^ Status          ^ Extracted value ^
 | Inactive contact | 0.0 | | Inactive contact | 0.0 |
-| Active contact | normal gap (signed value) |+| Active contact | normal gap (signed value, **positive if overlap???**) |
  
 The maximal normal gap is easily deduced: The maximal normal gap is easily deduced:
Line 495: Line 533:
 == PressureContactValueExtractor == == PressureContactValueExtractor ==
  
-Extract the contact pressure in each slave node:+Extract the contact pressure (**negative or positive, if bodies are pushed against each other ???**) in each slave node:
  
   valueExtractor = PressureContactValueExtractor(contInt, sOp=None, maxV=-1)   valueExtractor = PressureContactValueExtractor(contInt, sOp=None, maxV=-1)
Line 737: Line 775:
 The transfer error is defined as: The transfer error is defined as:
  
-$\frac{\int f^{old}-f^{new}}{\int f^{new} }$+$$\frac{\int f^{old}-f^{new}}{\int f^{new} }$$
  
  
Line 800: Line 838:
   * ''None'': no operator (all component,s by default)   * ''None'': no operator (all component,s by default)
   * ''MaxOperator'': maximal value   * ''MaxOperator'': maximal value
-  * ''MinOperator'': minimale value+  * ''MinOperator'': minimal value
   * ''AbsMaxOperator'': compute the value whose absolute value is maximal (but keeps its sign)   * ''AbsMaxOperator'': compute the value whose absolute value is maximal (but keeps its sign)
   * ''AbsMinOperator'': compute the value whose absolute value is minimal (but keeps its sign)   * ''AbsMinOperator'': compute the value whose absolute value is minimal (but keeps its sign)
   * ''MaxAbsOperator'': compute the maximal value of the vector containing absolute values (always positive)   * ''MaxAbsOperator'': compute the maximal value of the vector containing absolute values (always positive)
   * ''MinAbsOperator'': compute the minimal value of the vector containing absolute values (always positive)   * ''MinAbsOperator'': compute the minimal value of the vector containing absolute values (always positive)
 +  * ''MaxOfNonZeroOperator'': maximal value excluding zero values
 +  * ''MinOfNonZeroOperator'': minimal value excluding zero values
 +  * ''AbsMaxNonZeroOperator'': compute the value whose absolute value is maximal (but keeps its sign), excluding zero values
 +  * ''AbsMinNonZeroOperator'': compute the value whose absolute value is minimal (but keeps its sign), excluding zero values
 +  * ''MaxAbsNonZeroOperator'': compute the maximal value of the vector containing absolute values (always positive), excluding zero values
 +  * ''MinAbsNonZeroOperator'': compute the minimal value of the vector containing absolute values (always positive), excluding zero values
   * ''MeanOperator'': compute the average value   * ''MeanOperator'': compute the average value
   * ''SumOperator'': compute the sum (used toe extract the resultant force exercised on a given geometric entity)   * ''SumOperator'': compute the sum (used toe extract the resultant force exercised on a given geometric entity)
doc/user/results/courbes_res.txt · Last modified: 2023/05/25 11:28 by papeleux
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki