Datenvorverarbeitung und Synchronisierung von Playback Projekten/en: Unterschied zwischen den Versionen

Aus emoTouch
Zur Navigation springen Zur Suche springen
(Die Seite wurde neu angelegt: „== Synchronization process ==“)
 
(11 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
 
<languages />
 
<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 ==
 
== Problem ==
Zeile 10: Zeile 10:
 
# A part in Session 1 is rarely exactly the same length as the same part in Session 2.  
 
# 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 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.  
  
  
 
<div class="et-screenshot">
 
<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>
 
</div>
  
  
−
== Synchronization process ==
+
== Synchronisation process ==
  
−
Die Synchronisierung passiert in mehreren Schritten, die in hier grafisch an zwei Beispielsessions dargestellt sind.
+
The synchronisation happens in several steps, which are shown graphically in two example sessions here.
  
−
# Die Rohdaten:  
+
# The raw data:  
−
#* Die Sessions haben nacheinander stattgefunden und die Rohdaten sind gespeichert. Die Grenzlinien innerhalb eines Parts markieren Start- und Pausenevents eines abgespielten Mediums. Zwischen den Begrenzungen ist das Medium also pausiert, d.h. die in diesem Zeitraum ggf. erhobenen Daten sind nicht mehr Mediumsbezogen und damit für die Studie vernachlässigbar.  
+
#* 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.  
−
#* Es werden Synchronisierungsevents erzeugt. Diese entsprechen jeweils dem Start-Event eines Mediums, also z.B. dem Abspielen eines Vodeos.  
+
#* Synchronisation events are generated. These correspond to the start event of a medium, e.g. the playing of a video.  
−
# Die Pausen innerhalb der Parts werden für das Resampling übersprungen.  
+
# The pauses within the parts are skipped for resampling.  
−
#* Dadurch entstehen ggf. Pausen zwischen den Parts, da Abschnitte entfernt wurden. Das Start-Event des nächsten Parts bleibt aber an Ort und Stelle und wird nicht mit verschoben.  
+
#* 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.  
−
# Die Sessions werden synchronisiert.
+
# The sessions are synchronised.
−
#* Gedoppelte Parts innerhalb einer Session werden gebündelt übereinandergelegt.  
+
#* Duplicated parts within a session are bundled on top of each other.  
−
#* Die Synchroniesierungsevents aller Sessions werden übereinandergelegt. Dabei richten sich alle Parts nach demjenigen aus, welcher den meisten "Leerlauf" vor dem ersten Sync-Event hatte. Auch dadurch können also wieder Lücken entstehen.  
+
#* 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 werden erstellt.  
+
#* Part-end events are created.  
−
# Relative Zeitstempel werden erstellt. Es existieren 2 Arten von relativen Zeitstempeln:  
+
# Relative timestamps are created. There are 2 types of relative timestamps:  
−
#* Session-bezogene relative Zeitstempel (Session Zeitstempel)
+
#* Session-related relative timestamps (Session timestamps).
−
#* Part-bezogener relativer Zeitstempel (Part-Zeitstempel)
+
#* Part-related relative timestamp (Part timestamp)
  
  
  
−
== Synchronisierung bei Live-Studien ==
+
== Synchronisation 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 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 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.
+
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.

Aktuelle Version vom 4. September 2023, 11:58 Uhr

Sprachen:
Deutsch • ‎English

Note: Data preprocessing with session synchronization works only for sessions of one realisation, not across realisations.

Problem

In playback studies, the sessions usually take place asynchronously. In order to be able to compare the data of all sessions, the parts must be exactly superimposed before resampling. This article explains the process by which the sessions are (automatically) synchronized. The following circumstances must be taken into account:

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


Graphical representation of the synchronisation of several playback studies


Synchronisation process

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

  1. 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.
    • Synchronisation events are generated. These correspond to the start event of a medium, e.g. the playing of a video.
  2. 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.
  3. The sessions are synchronised.
    • Duplicated parts within a session are bundled on top of each other.
    • 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.
  4. Relative timestamps are created. There are 2 types of relative timestamps:
    • Session-related relative timestamps (Session timestamps).
    • Part-related relative timestamp (Part timestamp)


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.

Abgerufen von „https://wiki.emotouch.de/index.php?title=Datenvorverarbeitung_und_Synchronisierung_von_Playback_Projekten/en&oldid=3497“