modellingcomponents:eventsandphases
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
modellingcomponents:eventsandphases [2017/12/11 17:15] – [<Phase>] oliver | modellingcomponents:eventsandphases [2020/06/24 15:58] (aktuell) – [<Event>] oliver | ||
---|---|---|---|
Zeile 12: | Zeile 12: | ||
^ Attribute ^ Default ^ Description ^ Required ^ | ^ Attribute ^ Default ^ Description ^ Required ^ | ||
^ Name | | Name of the created phase type, also used as a prefix of created timeseries of condition an value tjaectories.| Yes | | ^ Name | | Name of the created phase type, also used as a prefix of created timeseries of condition an value tjaectories.| Yes | | ||
- | ^ startEvent | | Create a phase based on existing start event. Available only for pre- or stepbystep processing. | No | | + | ^ startEvent | | Create a phase based on existing start event for pre- or stepbystep processing. For postprocessing phases are created with an additional suffix " |
- | ^ endEvent | | Create a phase based on existing start event. Available only for pre- or stepbystep processing. | | | + | ^ endEvent | | Create a phase based on existing start event for pre- or stepbystep processing. For postprocessing phases are created with an additional suffix " |
- | ^ phase | not used | If set to an existing phase, a frame es included only if the frame is additionally also included in the given phase.| No | | + | ^ phase | not used | If set to an existing phase and if startEvent/ |
^ process | stepbystep | Available values: stepbystep, post, pre; The " | ^ process | stepbystep | Available values: stepbystep, post, pre; The " | ||
- | ^ value | | Used only, if process phase == stepbystep and condition is used. Phases created by the condition are excluded, if for the double timeseries defined by this attribute the values are bigger than the value of the maxvalue attribute or smallen | + | ^ value | | Used only, if process phase == stepbystep and condition is used. Phases created by the condition are excluded, if for the double timeseries defined by this attribute the values are bigger than the value of the maxvalue attribute or smaller |
^ contiguous | true | Used only if startEventTypeName == endEventTypeName. If set to false, an event is used eather as start- or end-event to create non contiguous phases. | No | | ^ contiguous | true | Used only if startEventTypeName == endEventTypeName. If set to false, an event is used eather as start- or end-event to create non contiguous phases. | No | | ||
^ maxvalue | Double.MAX_VALUE | The timserie defined by the " | ^ maxvalue | Double.MAX_VALUE | The timserie defined by the " | ||
^ 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 " | ^ 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 " | ||
- | ^ 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" |
- | ^ 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> | <code xml> | ||
- | <Phase name=" | + | <Phase name=" |
</ | </ | ||
Zeile 50: | Zeile 50: | ||
</ | </ | ||
- | The following code fragment creates | + | The following code fragment creates phases based simply on existing events: |
<code xml> | <code xml> | ||
Zeile 56: | Zeile 56: | ||
| | ||
| | ||
+ | </ | ||
+ | |||
+ | 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 xml> | ||
+ | < | ||
+ | process=" | ||
+ | startEvent=" | ||
+ | value=" | ||
+ | includes=" | ||
</ | </ | ||
=====< | =====< | ||
- | A < | + | A < |
**Attributes** | **Attributes** | ||
Zeile 65: | Zeile 75: | ||
^ Attribute ^ Default ^ Description ^ Required ^ | ^ 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 | | ^ name | | Name of the created event type, also used as a prefix of created timeseries of condition an value trajectories. | Yes | | ||
- | ^ method | min | " | + | ^ method | min | " |
- | ^ process | + | ^ process | post | Only postprocessing is supported. Preprocessing |
^ tolerance | | If set local maxima/ | ^ tolerance | | If set local maxima/ | ||
^ phase | | better use tolerance instead if possible Phase type name which defines phases, for each the event is set. | No | | ^ phase | | better use tolerance instead if possible Phase type name which defines phases, for each the event is set. | No | | ||
+ | ^ value | | Used from methods " | ||
+ | ^ 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 < | ||
+ | |||
+ | ^ Name ^ Precondition ^ Description ^ | ||
+ | ^ frame | The attribute " | ||
+ | ^ value | The attribute " | ||
+ | ^ 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/ | ||
+ | ^ 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/ | ||
+ | ^ minvelocity | ||
+ | ^ maxvelocity | ||
+ | ^ start | Attribute " | ||
+ | ^ end | Attribute " | ||
+ | ^ percent | Attribute " | ||
+ | |||
+ | **Issues** | ||
+ | * For the method " | ||
**Determined events and phases** | **Determined events and phases** | ||
Zeile 134: | Zeile 164: | ||
The element " | The element " | ||
- | " | + | " |
The interesting thing is that this results in four instead of three phases: [482;836], [1436; | The interesting thing is that this results in four instead of three phases: [482;836], [1436; | ||
Zeile 140: | Zeile 170: | ||
The element " | The element " | ||
- | From the events " | + | From the events " |
To plot these phases you have to add the following code fragment into your sheet definition: | To plot these phases you have to add the following code fragment into your sheet definition: |
modellingcomponents/eventsandphases.txt · Zuletzt geändert: 2020/06/24 15:58 von oliver