modellingcomponents:elements:eventsandphases
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
modellingcomponents:elements:eventsandphases [2020/09/10 10:03] – angelegt oliver | modellingcomponents:elements:eventsandphases [2021/09/27 16:47] (aktuell) – [<Phase>] oliver | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
- | dfdf | + | ====== Events and phases ====== |
+ | |||
+ | =====< | ||
+ | |||
+ | A **< | ||
+ | If the value of the formula is bigger than 0, the corresponding frame is part of the phase. | ||
+ | |||
+ | Ether the " | ||
+ | |||
+ | **Attributes** | ||
+ | |||
+ | ^ 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 | | ||
+ | ^ 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 for pre- or stepbystep processing. For postprocessing phases are created with an additional suffix " | ||
+ | ^ phase | not used | If set to an existing phase and if startEvent/ | ||
+ | ^ 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 smaller than the value of the minvalue attribute.| 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 " | ||
+ | ^ 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 " | ||
+ | ^ maxwidth | Integer.MAX_VALUE | 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 | | ||
+ | ^ expectedPhasesCount | -1 | Defines the expected count of phases which should be created. If the created count does not fit the number defined by this attribute a warning is written. | No | | ||
+ | ^ invert | false | If set to true a new set of phases is returnded in the areas of no phases. | No | | ||
+ | |||
+ | |||
+ | **Calculated Trajectories** | ||
+ | ^ Name ^ Type ^ Description ^ | ||
+ | ^ < | ||
+ | ^ < | ||
+ | |||
+ | **Determined events and phases** | ||
+ | |||
+ | ^ Name ^ Description ^ | ||
+ | ^ < | ||
+ | |||
+ | **Examples** | ||
+ | |||
+ | <code xml> | ||
+ | <Phase name=" | ||
+ | </ | ||
+ | |||
+ | The following code fragment, creates a phase with minimal width of 10 frames, for frames where the value of the timeserie RShoulderEleDepHDCalDirCosAngle is smaller than 30 degrees. | ||
+ | |||
+ | <code xml> | ||
+ | < | ||
+ | process=" | ||
+ | minwidth=" | ||
+ | value=" | ||
+ | includes=" | ||
+ | </ | ||
+ | |||
+ | The following code fragment creates phases based simply on existing events: | ||
+ | |||
+ | <code xml> | ||
+ | <Phase name=" | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | 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 < | ||
+ | |||
+ | **Attributes** | ||
+ | |||
+ | ^ 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 | " | ||
+ | ^ process | post | Only postprocessing is supported. Preprocessing und process step by step are not yet implemented.| No | | ||
+ | ^ tolerance | | If set local maxima/ | ||
+ | ^ phase | | Used only, if the attribute " | ||
+ | ^ 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 | | ||
+ | ^ minthreshold | not used | Used in combination with the methods " | ||
+ | ^ maxthreshold | not used | Used in combination with the methods " | ||
+ | |||
+ | ** Methods ** | ||
+ | |||
+ | Available methods defined by the < | ||
+ | |||
+ | ^ Name ^ Precondition ^ Description ^ | ||
+ | ^ frame | The attribute " | ||
+ | ^ value | The attribute " | ||
+ | ^ min | Ether the attribute " | ||
+ | ^ max | Ether the attribute " | ||
+ | ^ minvelocity | ||
+ | ^ maxvelocity | ||
+ | ^ maxabsvelocity | ||
+ | ^ start | Attribute " | ||
+ | ^ end | Attribute " | ||
+ | ^ percent | Attribute " | ||
+ | |||
+ | **Issues** | ||
+ | * For the method " | ||
+ | |||
+ | **Determined events and phases** | ||
+ | |||
+ | ^ Name ^ Type ^ Description ^ | ||
+ | ^ < | ||
+ | ^ < | ||
+ | |||
+ | **Examples** | ||
+ | |||
+ | <code xml> | ||
+ | <!-- be careful: the event is set to the minimum, that means, that this | ||
+ | | ||
+ | <Event name=" | ||
+ | | ||
+ | </ | ||
+ | |||
+ | **Notes** | ||
+ | If the method " | ||
+ | |||
+ | If the content is the name of a timeserie only, a classcast exeception is thrown. | ||
+ | |||
+ | WORKAROUND: | ||
+ | |||
+ | abc*1.0 | ||
+ | |||
+ | **A complex example** | ||
+ | |||
+ | Have a look at the following plot. It shows an elevation/ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | For all repetitions of the movement in the phase defined by RHS and RTO events the elevation phase should be extracted. The position of RHS is 482 and the position from RTO is 2697. | ||
+ | |||
+ | Have a look at the following code fragment which solves this problem: | ||
+ | |||
+ | <code xml> | ||
+ | <Phase name=" | ||
+ | | ||
+ | | ||
+ | | ||
+ | <Event name=" | ||
+ | | ||
+ | | ||
+ | | ||
+ | <Phase name=" | ||
+ | | ||
+ | | ||
+ | | ||
+ | <Event name=" | ||
+ | | ||
+ | <Phase name=" | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | The first element defines a phase with name " | ||
+ | * The frames must be inside the phase defined by RHS and RTO event | ||
+ | * A phase has a minimum length of 10 frames | ||
+ | * A phase is defined by the condition that the y-values of the curve are less than 30. | ||
+ | |||
+ | This result in two phases: [926;1341], [2156; | ||
+ | |||
+ | The element " | ||
+ | |||
+ | " | ||
+ | |||
+ | The interesting thing is that this results in four instead of three phases: [482;836], [1436; | ||
+ | |||
+ | The element " | ||
+ | |||
+ | From the events " | ||
+ | |||
+ | To plot these phases you have to add the following code fragment into your sheet definition: | ||
+ | |||
+ | <code xml> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | {{ : |
modellingcomponents/elements/eventsandphases.1599724983.txt.gz · Zuletzt geändert: 2020/09/10 10:03 von oliver