Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- modellingcomponents:eventsandphases [2018/11/08 18:44] – [<Phase>] oliver
+++ modellingcomponents:eventsandphases [2020/03/27 17:12] – [<Phase>] oliver
@@ Zeile 20: / Zeile 20: @@
 ^ maxvalue | Double.MAX_VALUE | The timserie defined by the "value" attribute is tested if it contains a value higher than the value of this attribute. If this is the case the complete phase is excluded. This attribute is respected only, if the process-flag is set to "post".| No |
 ^ minvalue | -Double.MAX_VALUE| The timeserie defined by the value attribute is tested, if it contains a value lower than the value of this attribute. If this is the case the complete phase is excluded. This attribute is respected only, if the process-flag is set to "post". | No |
-^ minwidth | 0 | Only phases with more than minwidth frames are created. Phases with less frames are ignored. | No |
+^ minwidth | 0 | Only phases with more than "minwidth" frames are created. Phases with less frames are ignored. Be careful: The atttribute must define an integer value.| No |
-^ maxwidth | Integer.MAX_VALLUE | Only phases with less than maxwidth frames are created. Phases with more frames are ignored.| No |
+^ maxwidth | Integer.MAX_VALLUE | Only phases with less than maxwidth frames are created. Phases with more frames are ignored. Be carefule: The attribute must define an integer value.| No |
@@ Zeile 37: / Zeile 37: @@
 <code xml>
-    <Phase name="ABC">abc &gt; 10.0"</Phase>
+    <Phase name="ABC">abc &gt; 10.0</Phase>
 </code>
@@ Zeile 50: / Zeile 50: @@
 </code>
-The following code fragment creates a phases based simply on existing events:
+The following code fragment creates phases based simply on existing events:
 <code xml>
@@ Zeile 59: / Zeile 59: @@
 The following code fragment creates phases based on the given condition but only if they are included completly into phases which are defined by the given start- and end-event.
-<code>
+<code xml>
  <Phase name="LEleStartPhase"
         process="post" minwidth="10"
@@ Zeile 68: / Zeile 69: @@
 =====<Event>=====
-A <Event>-element defines an event, based on the values of a double trajectorie (only), as its child and optional based on a given phase type name.
+A <Event>-element defines an event, based on the values of a double trajectorie (only), as its child and optional based on a given phase type name. All implemented methods are based on "post processing". Future methods cauld be based on other processing methods, e.g. "step by step".
 **Attributes**
@@ Zeile 74: / Zeile 75: @@
 ^ Attribute ^ Default ^ Description ^ Required ^
 ^ name | | Name of the created event type, also used as a prefix of created timeseries of condition an value trajectories. | Yes |
-^ method | min 	| "max", "min", "minvelocity", "maxveclocity" and if the attribute phase is set additional the methods "start" and "end" | No |
+^ method | min 	| "max", "min", "minvelocity", "maxveclocity", "frame", "value" and if the attribute phase is set additional the methods "start" and "end" | No |
-^ process (or deprectaed name calcphase) | | Vielleicht werde ich überhaupt nur **postprocess** unterstützten. preprocess und process sind jedenfalls nicht implementiert! process==in the phase, which it processes, step by step | No |
+^ process | post | Only postprocessing is supported. Preprocessing und process step by step are not yet implemented.| No |
 ^ tolerance | | If set local maxima/minima are determined by first creating phases with values between global min/max and min*(1+tolerance/100) or max*(1-tolerance/100) | No |
 ^ phase | | better use tolerance instead if possible Phase type name which defines phases, for each the event is set. | No |
+^ value | | Used from method "frame" and method "value". In the first case it must be an integer value, in the second case a double. | No |
+^ event | | A new event is created at the position of the given event moved about a given number of frames. | No |
+** Methods **
+Available methods defined by the <event>-elements attribute "method":
+^ Name ^ Precondition ^ Description ^
+^ frame | The attribute "value" must be set to an integer between 0 (inclusive) and trial length (exclusive). The attributes "tolerance" and "phase" are not set. | Creates an event at the given position. |
+^ value | The attribute "phase" must be set. | Create events for each phase of the given type at positions where the given timeserie has the smallest difference to the given value. |
+^ min  | | In a first step the global minimum or the minimum in the given phases, of the given timeseries is determined. Than phases are created in the range of [minimum; minimum*(1+percentTolerance/100)]. Last, for each of these phases an event is created at the position, where the timeseries reaches its minimum.|
+^ max  | | In a first step the global maximum or the maximum in the given phases, of the given timeseries is determined. Than phases are created in the range of [maximum*(1-percentTolerance/100); maximum]. Last, for each of these phases an event is created at the position, where the timeseries reaches its maximum. |
+^ minvelocity  | Attribute "phase" is set. | Same as with method "min", based on the derivative of the given timeserie. |
+^ maxvelocity  | Attribute "phase" is set. | Same as with method "max, based on the derivative of the given timeserie.|
+^ start | Attribute "phase" is set.| Creates an event at the start of the given phase.|
+^ end   | Attribute "phase" is set.| Creates an event at the end of the given phase |
+**Issues**
+  * For the method "frame" principle possible children elements are not processed.
 **Determined events and phases**