Datenvorverarbeitung und Synchronisierung von Playback Projekten/en - Versionsgeschichte

Aliebelt am 4. September 2023 um 11:58 Uhr

2023-09-04T11:58:53Z

FuzzyBot: FuzzyBot verschob die Seite Datenvorverarbeitung und Synchronisierung von Playback Studien/en nach Datenvorverarbeitung und Synchronisierung von Playback Projekten/en, ohne dabei eine Weiterleitung anzulegen: Teil der übersetzbaren Seite „Datenvorverarbeitung und Synchronisierung von Playback Studien“

2023-08-07T14:48:36Z

FuzzyBot verschob die Seite Datenvorverarbeitung und Synchronisierung von Playback Studien/en nach Datenvorverarbeitung und Synchronisierung von Playback Projekten/en, ohne dabei eine Weiterleitung anzulegen: Teil der übersetzbaren Seite „Datenvorverarbeitung und Synchronisierung von Playback Studien“

Aliebelt am 27. Juni 2023 um 08:44 Uhr

2023-06-27T08:44:35Z

Aliebelt am 27. Juni 2023 um 08:44 Uhr

2023-06-27T08:44:26Z

Aliebelt am 27. Juni 2023 um 08:32 Uhr

2023-06-27T08:32:56Z

Aliebelt am 27. Juni 2023 um 08:31 Uhr

2023-06-27T08:31:48Z

Aliebelt am 27. Juni 2023 um 08:31 Uhr

2023-06-27T08:31:42Z

Aliebelt am 27. Juni 2023 um 08:29 Uhr

2023-06-27T08:29:43Z

Fgehrs: Die Seite wurde neu angelegt: „In live studies, the sessions can also start staggered (e.g. if a participant joins later or slight latencies occur). In this case, however, the part-start eve…“

2023-06-26T11:07:19Z

Die Seite wurde neu angelegt: „In live studies, the sessions can also start staggered (e.g. if a participant joins later or slight latencies occur). In this case, however, the part-start eve…“

Fgehrs: Die Seite wurde neu angelegt: „== Synchronization for live studies ==“

2023-06-26T11:07:08Z

Die Seite wurde neu angelegt: „== Synchronization for live studies ==“

@@ Zeile 1: / Zeile 1: @@
 <languages />
-'''Note:''' Data preprocessing with session synchronization works only for sessions of one realisation, not across realisations.
+'''Note:''' Data preprocessing with session synchronization works only for sessions of '''one''' realisation, not across realisations.
 == Problem ==

@@ Zeile 37: / Zeile 37: @@
-== Synchronization for live studies ==
+== Synchronisation for live studies ==
 In live studies, the sessions can also start staggered (e.g. if a participant joins later or slight latencies occur). In this case, however, the part-start events must not be synchronized, as the data would otherwise be shifted.
 In live studies, therefore, the absolute time stamp must determine the measure, i.e. a concrete point in time during the study, or alternatively a concrete event originating from the performers.

@@ Zeile 24: / Zeile 24: @@
 # The raw data:
 #* The sessions have taken place one after the other and the raw data is stored. The boundary lines within a part mark start and pause events of a played medium. Between the boundaries, the medium is therefore paused, i.e. the data collected during this period, if any, is no longer medium-related and thus negligible for the study.
-#* Synchronization events are generated. These correspond to the start event of a medium, e.g. the playing of a video.
+#* Synchronisation events are generated. These correspond to the start event of a medium, e.g. the playing of a video.
 # The pauses within the parts are skipped for resampling.
 #* This may cause pauses between the parts, because sections have been removed. However, the start event of the next part remains in place and is not moved with it.
-# The sessions are synchronized.
+# The sessions are synchronised.
 #* Duplicated parts within a session are bundled on top of each other.
-#* The synchronization events of all sessions are superimposed. Thereby all parts align themselves after the one, which had the most "idle time" before the first sync event.  So again this can cause gaps.
+#* The synchronisation events of all sessions are superimposed. Thereby all parts align themselves after the one, which had the most "waiting time" before the first sync event. So again this can cause gaps.
 #* Part-end events are created.
 # Relative timestamps are created. There are 2 types of relative timestamps:

@@ Zeile 20: / Zeile 20: @@
 == Synchronisation process ==
-The synchronization happens in several steps, which are shown graphically in two example sessions here.
+The synchronisation happens in several steps, which are shown graphically in two example sessions here.
 # The raw data:

← Nächstältere Version		Version vom 27. Juni 2023, 08:31 Uhr
Zeile 18:		Zeile 18:


−	== ~~Synchronization~~ process ==	+	== Synchronisation process ==

	The synchronization happens in several steps, which are shown graphically in two example sessions here.		The synchronization happens in several steps, which are shown graphically in two example sessions here.

@@ Zeile 14: / Zeile 14: @@
 <div class="et-screenshot">
-[[Datei:Datenvorverarbeitung und Synchronisierung.png|Grafische Darstellung der Synchronisierung mehrerer Playback Studien]]
+[[Datei:Datenvorverarbeitung und Synchronisierung.png|Graphical representation of the synchronisation of several playback studies]]
 </div>

@@ Zeile 10: / Zeile 10: @@
 # A part in Session 1 is rarely exactly the same length as the same part in Session 2.
 # If a part contains a pausable medium, there may be periods during the pause in which no data are generated.
-# If randomization is used in the study, Parts may be duplicated or missing. These data must also be comparable.
+# If randomisation is used in the study, Parts may be duplicated or missing. These data must also be comparable.

@@ Zeile 37: / Zeile 37: @@
-== Synchronisierung bei Live-Studien ==
+== Synchronization for live studies ==
 In Live Studien können die Sessions auch versetzt beginnen (z.B. Wenn ein Teilnehmer später dazustößt oder leichte Latenzen auftreten). Die Part-Start Events dürfen in diesem Fall allerdings nicht synchronisiert werden, da die Daten sonst verschoben werden würden.
 In Live Studien muss also der absolute Zeitstempel das Maß bestimmen, also ein konkreter Zeitpunkt während der Studie, oder alternativ ein von den Durchführenden ausgehendes konkretes Event.