Differences

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

--- doc:user:integration:general:stopcriterion [2019/06/13 19:03] – [ValueExtractorStopCriterion] boemer
+++ doc:user:integration:general:stopcriterion [2019/06/13 19:04] – [Introduction] boemer
@@ Line 5: / Line 5: @@
 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.
@@ Line 41: / Line 41: @@
 ===== 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)