Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- modellingcomponents:eventsandphases [2018/07/10 11:10] – [<Event>] oliver
+++ modellingcomponents:eventsandphases [2018/11/08 18:44] – [<Phase>] oliver
@@ Zeile 12: / Zeile 12: @@
 ^ 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. 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 "Global", integrated in the condition. | No |
-^ 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 "Global", integrated in the condition.| No |
-^ 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/endEvent is not used, a frame es included only if the frame is additionally also included in the given phase.| No |
 ^ process | stepbystep | Available values: stepbystep, post, pre; The "process phase", in which the time phase is created. If the condition attribute is used, the condition traj wrapper is calculated step-by-step, but the phases are created also in the postprocess phase. If start-/end-event is used, the phases are created with the first frame. | No |
 ^ 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 than the value of the minvalue attribute.| No |
@@ Zeile 56: / Zeile 56: @@
        calibrateIncludes="dynamic_calibrate_right_shoulder"
        includes="dummy"/>
+</code>
+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>
+ <Phase name="LEleStartPhase"
+        process="post" minwidth="10"
+        startEvent="LHS" endEvent="LTO"
+        value="LShoulderEleDepHDCalDirCosAngle*1.0"
+        includes="ShoulderAbdAdd,ShoulderAnteRetro">LShoulderEleDepHDCalDirCosAngle &lt; 30.0</Phase>
 </code>
 =====<Event>=====
@@ Zeile 134: / Zeile 143: @@
 The element "REleStart" determines for each of the phases above an event at the position where the curve has its minimum. So we have the start positions of the wanted elevation phases: 1164, 2399
-"REleEndPhase" looks for phases where the y-values of the curve are bigger than 60 and also the assumption defined by RHS and RTO and a min length of 40 frames.
+"REleEndPhase" looks for phases where the y-values of the curve are bigger than 60 and also the assumption defined by RHS and RTO and a min length of 40 frames. "Bigger than 60" results in the need of a minimum elevation of 60+40=100 degree to autodetect a REleEndPhase.
 The interesting thing is that this results in four instead of three phases: [482;836], [1436;1634], [1637;2054] and [2691;2697]. The second phase is split because of a gap in the curve.