Metafor

ULiege - Aerospace & Mechanical Engineering

User Tools

Site Tools


doc:user:integration:general:stopcriterion

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
doc:user:integration:general:stopcriterion [2019/06/13 19:03] – [ValueExtractorStopCriterion] boemerdoc:user:integration:general:stopcriterion [2019/06/17 14:13] (current) papeleux
Line 5: Line 5:
 The stop criterion allows to stop a computation when a given criterion becomes greater than a given value. The stop criterion allows to stop a computation when a given criterion becomes greater than a given value.
  
-It is useful to avoid consuming CPU when a computation has no meaning anymore, or to chain operations (remeshing, chained operation based on a criterion, ...)+It is useful to avoid consuming CPU time when a computation has no meaning anymore, or to chain operations (remeshing, chained operation based on a criterion, ...)
  
 While stopping cleanly the computation, a fac is written at the stop time, the ValuesManager is properly closed and the ascii export is done. While stopping cleanly the computation, a fac is written at the stop time, the ValuesManager is properly closed and the ascii export is done.
Line 16: Line 16:
   * ''setRunObjFuncSet(bool)'' : force (remove) the computation/writing of ObjectiveFunctions (not required, if remeshing) (default : True)   * ''setRunObjFuncSet(bool)'' : force (remove) the computation/writing of ObjectiveFunctions (not required, if remeshing) (default : True)
   * ''setStopAtNextFac(bool)'' : compute the criterion at each timeStep, but stop the computation only after the next fac writing (default : False)   * ''setStopAtNextFac(bool)'' : compute the criterion at each timeStep, but stop the computation only after the next fac writing (default : False)
-  * ''checkAtFac(bool)''    : compute the criterion at fac writing time (default : False)+  * ''setCheckAtFac(bool)''    : compute the criterion at fac writing time (default : False)
  
 The criterion is finally added in the Metafor object :  The criterion is finally added in the Metafor object : 
Line 25: Line 25:
         crit.setRunObjFuncSet(True) # (default : True)         crit.setRunObjFuncSet(True) # (default : True)
         crit.setStopAtNextFac(True) # (default : False)         crit.setStopAtNextFac(True) # (default : False)
-        crit.checkAtFac(True)       # (default : False)+        crit.setCheckAtFac(True)       # (default : False)
         metafor.setStopCriterion(crit)         metafor.setStopCriterion(crit)
 </code> </code>
Line 41: Line 41:
 ===== ValueManagerStopCriterion ===== ===== ValueManagerStopCriterion =====
  
-If you want to use a value allready extracted in the ValuesManager : +If you want to use a value, which is already extracted in the ValuesManager : 
   * ValueManagerStopCriterion(ValuesStruct *_valueStruct, int _comp=0)   * ValueManagerStopCriterion(ValuesStruct *_valueStruct, int _comp=0)
  
doc/user/integration/general/stopcriterion.1560445395.txt.gz · Last modified: 2019/06/13 19:03 by boemer

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki