emoTouch - Benutzerbeiträge [de]

Bekannte Probleme und Workarounds

2025-05-30T19:33:31Z

Aliebelt:

<languages/>
<translate>

Wie jede komplexe Software, so kann auch emoTouch gelegentlich ein fehlerhaftes oder unerwartetes Verhalten zeigen. Dies tritt oft nur unter bestimmten, seltenen oder ungewöhnlichen Nutzungsbedingungen auf, die wir bei Erstellung er Software so nicht vorhergesehen haben. Je nach Art des konkreten Projekts mit emoTouch können solche Fehler unter Umständen für die Arbeit jedoch sehr lästig oder hinderlich sein.

Falls uns derartige Fehler (‚Bugs‘) auffallen oder von den Nutzern gemeldet werden, versuchen wir diese möglichst zeitnah in einem der nächsten Updates zu beseitigen. Dies kann je nach Komplexität und Dringlichkeit des Problems jedoch auch einige Zeit in Anspruch nehmen.
Diese Seite listet bekannte Probleme und Fehler auf, die unter bestimmten Bedingungen bei der Arbeit mit emoTouch auftreten können und die bislang noch nicht durch ein Update beseitigt werden konnten. Ausserdem ist jeweils angegeben, wie das Problem vermieden, umgangen oder gelöst werden kann.

= Part-Editor: Nach dem Ausloggen sind Änderungen verschwunden =

===Problem===
Im Part-Editor vorgenommene Änderungen werden nicht gespeichert und sind beim nächsten Einloggen verschwunden.

=== Ursache ===
Das Problem tritt auf, wenn man im Editor Änderungen vornimmt und sich dann VOR einem Klick auf den Speichern-Knopf aus emoTouch ausloggt. Man sieht dann zwar eine Warnung ‚Ungespeicherte Änderungen‘ und kann auch auf ’Speichern’ klicken, dies führt aber zu einem ‚HTTP Error 401: Unauthorized‘-Error. Die vorgenommenen Änderungen werden nicht gespeichert.

=== Workaround ===
Klicken Sie einmal auf ‚Speichern‘, bevor Sie emoTouch verlassen oder das Browserfenster schließen. Es gibt zudem keine Notwendigkeit, sich beim Verlassen von emoTouch aktiv aus dem System auszuloggen.

= Participant Interface: Text wird falsch umgebrochen oder ist nicht sichtbar =

=== Problem ===
Bei Textfeldern ragt der Text rechts aus dem Textfeld und ggf. auch aus dem sichtbaren Bereich heraus, obwohl im Part Editor alles korrekt aussieht. Dies tritt besonders bei langen Texten auf, die in den Textfeldern umgebrochen werden.

=== Ursache ===
Grund sind unzuverlässige Textweiten-Informationen der verwendeten, lizenzfreien Zeichensätze.

=== Workaround ===
Verwenden Sie einen anderen Zeichensatz, eine kleinere Zeichengröße oder fügen Sie feste Zeilenumbrüche in Ihren Text ein.

= Chart-Konfiguration: Der Eintrag ‚Durchführung‘ und die Liste zur Session-Auswahl sind leer =

=== Problem ===
Beim Aufruf des Chart-Konfigurationsdialogs bleibt der Eintrag ‚Durchführung‘ leer, obwohl vorher eine Durchführung ausgewählt wurde. Im Bereich ‚Sessions‘ werden keine Sessions angezeigt.

=== Ursache ===
Das Problem kann unter bestimmten Umständen auftreten, wenn zwar für die gesamte Visualisierung eine Durchführung konfiguriert ist, aber nicht für das einzelne Chart. Das Chart verwendet dann zwar die richtige Durchführung, der Konfigurationsdialog zeigt dies jedoch nicht korrekt an.

=== Workaround ===
Wenn im Chart-Konfigurationsdialog die Durchführung aus der Dropdown-Liste neu ausgewählt wird, dann füllt sich auch die Session-Liste mit den Sessions der Durchführung und es können die gewünschten Sessions ausgewählt werden.

</translate>

Bekannte Probleme und Workarounds

2025-04-09T10:19:50Z

Aliebelt:

Bekannte Probleme und Workarounds/en

2025-04-09T10:19:23Z

Aliebelt: Die Seite wurde neu angelegt: „Known issues and workarounds“

<languages/>

Test Text

Translations:Bekannte Probleme und Workarounds/Page display title/en

2025-04-09T10:19:23Z

Aliebelt: Die Seite wurde neu angelegt: „Known issues and workarounds“

Known issues and workarounds

Bekannte Probleme und Workarounds

2025-04-09T10:19:02Z

Aliebelt: Diese Seite wurde zum Übersetzen freigegeben

Hauptseite/en

2025-04-09T10:18:48Z

Aliebelt:

<languages />

[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]

<div class="mw-translate-fuzzy">
Welcome to the Wiki of emoTouch Web, the tool for real-time monitoring and feedback of performative processes from the University of Osnabrück. The pages listed here contain general information, tutorials and application examples.
</div>

== Working with emoTouch ==
'''Projects'''
* [[Projekte#Erstellen/ Bearbeiten | Create/ Edit]]
* [[Projekte#Durchführen | Conduct]]
* [[Projekte#Datenverarbeitung | Data Processing]]
* [[Projekte#Auswerten | Evaluate]]

''' Step-by-step instructions '''
* [[Erste Schritte zum eigenen Projekt|First steps to your own project]]

''' Application examples '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien/en|Application example: evaluation of integrated media]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen/en|Application example: Evaluation of a live situation with different scales]]

'''Assistance'''
* [[Known issues and workarounds]]

== Collaboration ==
* [[Benutzer/en|Users]]

''' Integration of other tools/ in other tools '''
* [[SoSci Survey]]

== General information ==
* [[EmoTouch:Über emoTouch/en|About emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)/en|Version History (emoTouch for iPad)]]
* [[Bisherige "continuous response" - Systeme/en|Previous "continuous response" systems]]
* [[Glossar/en|Glossary]]
* [[Stichwortverzeichnis/en|Index]]

Translations:Hauptseite/23/en

2025-04-09T10:18:48Z

Aliebelt:

'''Assistance'''
* [[Known issues and workarounds]]

Hauptseite/en

2025-04-09T10:16:55Z

Aliebelt:

<languages />

[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]

<div class="mw-translate-fuzzy">
Welcome to the Wiki of emoTouch Web, the tool for real-time monitoring and feedback of performative processes from the University of Osnabrück. The pages listed here contain general information, tutorials and application examples.
</div>

== Working with emoTouch ==
'''Projects'''
* [[Projekte#Erstellen/ Bearbeiten | Create/ Edit]]
* [[Projekte#Durchführen | Conduct]]
* [[Projekte#Datenverarbeitung | Data Processing]]
* [[Projekte#Auswerten | Evaluate]]

''' Step-by-step instructions '''
* [[Erste Schritte zum eigenen Projekt|First steps to your own project]]

''' Application examples '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien/en|Application example: evaluation of integrated media]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen/en|Application example: Evaluation of a live situation with different scales]]

* [[Known issues and workarounds]]

== Collaboration ==
* [[Benutzer/en|Users]]

''' Integration of other tools/ in other tools '''
* [[SoSci Survey]]

== General information ==
* [[EmoTouch:Über emoTouch/en|About emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)/en|Version History (emoTouch for iPad)]]
* [[Bisherige "continuous response" - Systeme/en|Previous "continuous response" systems]]
* [[Glossar/en|Glossary]]
* [[Stichwortverzeichnis/en|Index]]

Translations:Hauptseite/16/en

2025-04-09T10:16:55Z

Aliebelt:

== Working with emoTouch ==
'''Projects'''
* [[Projekte#Erstellen/ Bearbeiten | Create/ Edit]]
* [[Projekte#Durchführen | Conduct]]
* [[Projekte#Datenverarbeitung | Data Processing]]
* [[Projekte#Auswerten | Evaluate]]

Hauptseite/en

2025-04-09T10:15:24Z

Aliebelt: Die Seite wurde neu angelegt: „* Known issues and workarounds“

<languages />

[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]

<div class="mw-translate-fuzzy">
Welcome to the Wiki of emoTouch Web, the tool for real-time monitoring and feedback of performative processes from the University of Osnabrück. The pages listed here contain general information, tutorials and application examples.
</div>

<div class="mw-translate-fuzzy">
== Working with emoTouch ==
'''Projects'''
* [[Projekte#Erstellen/ Bearbeiten | Create/ Edit]]
* [[Projekte#Durchführen | Conduct]]
* [[Projekte#Auswerten | Evaluate]]
</div>

''' Step-by-step instructions '''
* [[Erste Schritte zum eigenen Projekt|First steps to your own project]]

''' Application examples '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien/en|Application example: evaluation of integrated media]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen/en|Application example: Evaluation of a live situation with different scales]]

* [[Known issues and workarounds]]

== Collaboration ==
* [[Benutzer/en|Users]]

''' Integration of other tools/ in other tools '''
* [[SoSci Survey]]

== General information ==
* [[EmoTouch:Über emoTouch/en|About emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)/en|Version History (emoTouch for iPad)]]
* [[Bisherige "continuous response" - Systeme/en|Previous "continuous response" systems]]
* [[Glossar/en|Glossary]]
* [[Stichwortverzeichnis/en|Index]]

Translations:Hauptseite/23/en

2025-04-09T10:15:24Z

Aliebelt: Die Seite wurde neu angelegt: „* Known issues and workarounds“

* [[Known issues and workarounds]]

Hauptseite/en

2025-04-09T10:14:22Z

Aliebelt:

<languages />

[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]

<div class="mw-translate-fuzzy">
Welcome to the Wiki of emoTouch Web, the tool for real-time monitoring and feedback of performative processes from the University of Osnabrück. The pages listed here contain general information, tutorials and application examples.
</div>

<div class="mw-translate-fuzzy">
== Working with emoTouch ==
'''Projects'''
* [[Projekte#Erstellen/ Bearbeiten | Create/ Edit]]
* [[Projekte#Durchführen | Conduct]]
* [[Projekte#Auswerten | Evaluate]]
</div>

''' Step-by-step instructions '''
* [[Erste Schritte zum eigenen Projekt|First steps to your own project]]

''' Application examples '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien/en|Application example: evaluation of integrated media]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen/en|Application example: Evaluation of a live situation with different scales]]

'''Hilfestellungen'''
* [[Bekannte Probleme und Workarounds]]

== Collaboration ==
* [[Benutzer/en|Users]]

''' Integration of other tools/ in other tools '''
* [[SoSci Survey]]

== General information ==
* [[EmoTouch:Über emoTouch/en|About emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)/en|Version History (emoTouch for iPad)]]
* [[Bisherige "continuous response" - Systeme/en|Previous "continuous response" systems]]
* [[Glossar/en|Glossary]]
* [[Stichwortverzeichnis/en|Index]]

Hauptseite/en

2025-04-09T10:13:58Z

Aliebelt:

<languages />

[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]

<div class="mw-translate-fuzzy">
Welcome to the Wiki of emoTouch Web, the tool for real-time monitoring and feedback of performative processes from the University of Osnabrück. The pages listed here contain general information, tutorials and application examples.
</div>

<div class="mw-translate-fuzzy">
== Working with emoTouch ==
'''Projects'''
* [[Projekte#Erstellen/ Bearbeiten | Create/ Edit]]
* [[Projekte#Durchführen | Conduct]]
* [[Projekte#Auswerten | Evaluate]]
</div>

''' Step-by-step instructions '''
* [[Erste Schritte zum eigenen Projekt|First steps to your own project]]

''' Application examples '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien/en|Application example: evaluation of integrated media]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen/en|Application example: Evaluation of a live situation with different scales]]

'''Hilfestellungen'''
* [[Bekannte Probleme und Workarounds]]

== Collaboration ==
* [[Benutzer/en|Users]]

''' Integration of other tools/ in other tools '''
* [[SoSci Survey]]

<div class="mw-translate-fuzzy">
== General information ==
* [[EmoTouch:Über emoTouch/en|About emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)/en|Version History (emoTouch for iPad)]]
* [[Bisherige "continuous response" - Systeme/en|Previous "continuous response" systems]]
* [[Glossar/en|Glossary]]
* [[Stichwortverzeichnis/en|Index]]
</div>

Translations:Hauptseite/18/en

2025-04-09T10:13:58Z

Aliebelt:

== Collaboration ==
* [[Benutzer/en|Users]]

Hauptseite

2025-04-09T10:13:10Z

Aliebelt: Diese Seite wurde zum Übersetzen freigegeben

<languages />
<translate>


[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]


Willkommen im Wiki von emoTouch Web, dem Tool zur Echtzeitbegleitung und Feedback von performativen Prozessen von der Universität Osnabrück. Die hier aufgeführten Seiten beinhalten detaillierte Informationen, Tutorials und Anwendungsbeispiele.

== Arbeiten mit emoTouch == 
''' Projekte '''
* [[Projekte#Erstellen/ Bearbeiten | Erstellen/ Bearbeiten]]
* [[Projekte#Durchführen | Durchführen]]
* [[Projekte#Datenverarbeitung | Datenverarbeitung]]
* [[Projekte#Auswerten und Visualisieren | Auswerten & Visualisieren]]


''' Schritt-für-Schritt Anleitungen '''
* [[Erste Schritte zum eigenen Projekt]]


''' Anwendungsbeispiele '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen]]


'''Hilfestellungen'''
* [[Bekannte Probleme und Workarounds]]

== Zusammenarbeit == 
* [[Benutzer]]


''' Einbindung von anderen Tools/ in andere Tools '''
* [[SoSci Survey]]

== Allgemeine Informationen == 
* [[EmoTouch:Über emoTouch|Über emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)|Versionshistorie (emoTouch für iPad)]]
* [[Bisherige "continuous response" - Systeme]]
* [[Glossar]]

</translate>

Bekannte Probleme und Workarounds

2025-04-09T10:12:51Z

Aliebelt:

Bekannte Probleme und Workarounds

2025-04-07T22:51:07Z

Aliebelt:

Bekannte Probleme und Workarounds

2025-04-07T22:50:08Z

Aliebelt: Leere Seite erstellt

Hauptseite

2025-04-07T22:49:51Z

Aliebelt:

<languages />
<translate>


[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]


Willkommen im Wiki von emoTouch Web, dem Tool zur Echtzeitbegleitung und Feedback von performativen Prozessen von der Universität Osnabrück. Die hier aufgeführten Seiten beinhalten detaillierte Informationen, Tutorials und Anwendungsbeispiele.

== Arbeiten mit emoTouch == 
''' Projekte '''
* [[Projekte#Erstellen/ Bearbeiten | Erstellen/ Bearbeiten]]
* [[Projekte#Durchführen | Durchführen]]
* [[Projekte#Datenverarbeitung | Datenverarbeitung]]
* [[Projekte#Auswerten und Visualisieren | Auswerten & Visualisieren]]


''' Schritt-für-Schritt Anleitungen '''
* [[Erste Schritte zum eigenen Projekt]]


''' Anwendungsbeispiele '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen]]

'''Hilfestellungen'''
* [[Bekannte Probleme und Workarounds]]

== Zusammenarbeit == 
* [[Benutzer]]


''' Einbindung von anderen Tools/ in andere Tools '''
* [[SoSci Survey]]

== Allgemeine Informationen == 
* [[EmoTouch:Über emoTouch|Über emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)|Versionshistorie (emoTouch für iPad)]]
* [[Bisherige "continuous response" - Systeme]]
* [[Glossar]]

</translate>

Hauptseite

2025-04-07T22:49:42Z

Aliebelt:

<languages />
<translate>


[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]


Willkommen im Wiki von emoTouch Web, dem Tool zur Echtzeitbegleitung und Feedback von performativen Prozessen von der Universität Osnabrück. Die hier aufgeführten Seiten beinhalten detaillierte Informationen, Tutorials und Anwendungsbeispiele.

== Arbeiten mit emoTouch == 
''' Projekte '''
* [[Projekte#Erstellen/ Bearbeiten | Erstellen/ Bearbeiten]]
* [[Projekte#Durchführen | Durchführen]]
* [[Projekte#Datenverarbeitung | Datenverarbeitung]]
* [[Projekte#Auswerten und Visualisieren | Auswerten & Visualisieren]]


''' Schritt-für-Schritt Anleitungen '''
* [[Erste Schritte zum eigenen Projekt]]


''' Anwendungsbeispiele '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen]]

'''Hilfestellung'''
* [[Bekannte Probleme und Workarounds]]

== Zusammenarbeit == 
* [[Benutzer]]


''' Einbindung von anderen Tools/ in andere Tools '''
* [[SoSci Survey]]

== Allgemeine Informationen == 
* [[EmoTouch:Über emoTouch|Über emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)|Versionshistorie (emoTouch für iPad)]]
* [[Bisherige "continuous response" - Systeme]]
* [[Glossar]]

</translate>

EmoTouch R Webservice Dokumentation

2024-11-19T20:52:38Z

Aliebelt:

= Additional documentation =
Additional documentation is served by swagger when running R web service:

http://127.0.0.1:8000/__docs__/

= Results structure =
Results from R web service are always wrapped in a list to provide error handling and extra metadata about the returned object.

== on R side ==
In case of successfully computed request (of a function returning scalar integer value 3):

list(
error = <span style="color: purple;"> NULL</span>,
results = <span style="color: green;"> 3L</span>,
type = <span style="color: red;"> "integer"</span>,
length = <span style="color: green;"> 1L</span>
)

In case of an error:

list(
error = <span style="color: red;"> "an error message"</span>,
results = <span style="color: purple;"> NULL </span>,
type = <span style="color: purple;"> NULL</span>,
length = <span style="color: purple;"> NULL</span>
)

== on JavaScript side ==
Note that results field is always boxed, even for scalar result:

{"error":{},"result":[3],"type":"double","length":1}

An error:

{"error":"an error message","result":{},"type":{},"length":{}}

= Functions =
All functions that takes any arguments are meant to be called as POST method. Those without arguments via GET method.

== version ==
Returns the version of the R webservice.
Takes no arguments.

curl -H "Content-Type: application/json" http://localhost:8000/version

{"error":{},"result":["0.3"],"type":"character","length":1}

== degap ==

Synchronize multiple series according to their indexes. Fill gaps with Last Observation Carried Forward.
Indices provided in idx must have same sampling rate. Arguments:
* x: list of series of numeric values.
* idx: list of series of indexes, must be same number of series as series provided to x, must have same length as corresponding series provided to x.
* sync: boolean default to true, takes min and max index from all indices to expand all series of x into it. See examples below.
* how: character, default "locf" means that gaps are filled with last observation carried forward, could be also "nocb" for next observation carried backward, or "const" for the constant value specified in fill argument.
* fill: numeric to be used when how="const".

examples of sync=true (default), sampling rate 1.

x1 = [4,5,8,7,6]
x2 = [2,3,4,5,7]
idx1 = [2,3,5,6,8]
idx2 = [0,1,3,4,6]

synchronized indices

idx12 = [0,1,2,3,4,5,6,7,8]
x1gap = [ , ,4,5, ,8,7, ,6]
x2gap = [2,3, ,4,5, ,7, , ]

gaps filled with locf (default)

x1out = [ , ,4,5,5,8,7,7,6]
x2out = [2,3,3,4,5,5,7,7,7]

Note that x and idx can contain 1+ series.

Working example of 2 series (sampling rate 2):

curl -H "Content-Type: application/json" --data '{"x": [[1,2.5,3,4,5.5,6,7,8],[1.5,3.5,4,4,5.5,6,7]],"idx": [[0,2,4,8,10,14,16,18],[0,2,4,6,8,14,18]]}' http://localhost:8000/degap
#{"error":{}, "result":[[1,2.5,3,3,4,5.5,5.5,6,7,8],[1.5,3.5,4,4,5.5,5.5,5.5,6,6,7]], "type":"length":2}

When sync=false then each series has gaps filled only within its own min-max boundaries.
According to use cases discussed, use of sync=false and how!="locf" should be considered undesired.

Graphical representation of the function:

x = c(4,6.5,3,4,7.5,4,8,9)
idx = c(0,1,2,4,5,6,7,9)

(((((Platzhalter Bild)))))))

== norm ==
Normalizes multiple series.
Arguments:
* x: list of series of numeric values to normalize.
* how: character, default "max", other supported values are "mean/sd" and "diff". The method used to normalize values, described below.

Note that x can contain 1+ series.

# max
x / max(x)

# mean/sd
(x - mean(x)) / sd(x)

# diff # Lagged Differences: https://stat.ethz.ch/R-manual/R-devel/library/base/html/diff.html
diff(x)

Working example of 2 series, three different how argument values

curl -H "Content-Type: application/json" --data '{"x":[[1,2.5,3,3,4,5.5,5.5,6,7,8],[1.5,3.5,4,4,5.5,5.5,5.5,6,6,7]],"how":"max"}' http://localhost:8000/norm
#{"error":{},"result":[[0.125,0.3125,0.375,0.375,0.5,0.6875,0.6875,0.75,0.875,1],[0.2143,0.5,0.5714,0.5714,0.7857,0.7857,0.7857,0.8571,0.8571,1]],"type":"list","length":2}

curl -H "Content-Type: application/json" --data '{"x":[[1,2.5,3,3,4,5.5,5.5,6,7,8],[1.5,3.5,4,4,5.5,5.5,5.5,6,6,7]],"how":"mean/sd"}' http://localhost:8000/norm
#{"error":{},"result":[[-1.6106,-0.9301,-0.7032,-0.7032,-0.2495,0.431,0.431,0.6578,1.1115,1.5652],[-2.0944,-0.844,-0.5314,-0.5314,0.4064,0.4064,0.4064,0.719,0.719,1.3442]],"type":"list","length":2}

curl -H "Content-Type: application/json" --data '{"x":[[1,2.5,3,3,4,5.5,5.5,6,7,8],[1.5,3.5,4,4,5.5,5.5,5.5,6,6,7]],"how":"diff"}' http://localhost:8000/norm
#{"error":{},"result":[[1.5,0.5,0,1,1.5,0,0.5,1,1],[2,0.5,0,1.5,0,0,0.5,0,1]],"type":"list","length":2}

Graphical representation of the function:

x = c(4, 6.5, 3, 3, 4, 7.5, 4, 8, 8, 9)

(((((((Platzhalter Bild ))))))

== denoise ==
Applies noise reduction over provided series. Arguments:
* x: list of series of numeric values to apply noise reduction.
* n: integer size of smoothing window.
* how: character, default "median", also supported "mean". The method used to reduce noise.

Note that x can contain 1+ series.

n-1 leading observations are computed on partial window.

# median of last 3 observations
curl -H "Content-Type: application/json" --data '{"x":[[-1.6106,-0.9301,-0.7032,-0.7032,-0.2495,0.431,0.431,0.6578,1.1115,1.5652],[-2.0944,-0.844,-0.5314,-0.5314,0.4064,0.4064,0.4064,0.719,0.719,1.3442]],"n":3,"how":"median"}' http://localhost:8000/denoise
#{"error":{},"result":[[-1.6106,-1.2704,-0.9301,-0.7032,-0.7032,-0.2495,0.431,0.431,0.6578,1.1115],[-2.0944,-1.4692,-0.844,-0.5314,-0.5314,0.4064,0.4064,0.4064,0.719,0.719]],"type":"list","length":2}

# mean of last 3 observations
curl -H "Content-Type: application/json" --data '{"x":[[-1.6106,-0.9301,-0.7032,-0.7032,-0.2495,0.431,0.431,0.6578,1.1115,1.5652],[-2.0944,-0.844,-0.5314,-0.5314,0.4064,0.4064,0.4064,0.719,0.719,1.3442]],"n":3,"how":"mean"}' http://localhost:8000/denoise
#{"error":{},"result":[[-1.6106,-1.2704,-1.0813,-0.7788,-0.552,-0.1739,0.2042,0.5066,0.7334,1.1115],[-2.0944,-1.4692,-1.1566,-0.6356,-0.2188,0.0938,0.4064,0.5106,0.6148,0.9274]],"type":"list","length":2}

# mean of last 5 observations
curl -H "Content-Type: application/json" --data '{"x":[[-1.6106,-0.9301,-0.7032,-0.7032,-0.2495,0.431,0.431,0.6578,1.1115,1.5652],[-2.0944,-0.844,-0.5314,-0.5314,0.4064,0.4064,0.4064,0.719,0.719,1.3442]],"n":5,"how":"mean"}' http://localhost:8000/denoise
#{"error":{},"result":[[-1.6106,-1.2704,-1.0813,-0.9868,-0.8393,-0.431,-0.1588,0.1134,0.4764,0.8393],[-2.0944,-1.4692,-1.1566,-1.0003,-0.719,-0.2188,0.0313,0.2814,0.5314,0.719]],"type":"list","length":2}

Graphical representation of the function:

x = c(4, 6.5, 3, 3, 4, 7.5, 4, 8, 8, 9)

((((((((Platzhalter Bild))))))))

== degap_norm_denoise ==
This function wraps around 3 other functions degap, norm and denoise.
For detailed argument description see mentioned functions above.
Arguments:
* x: list of series of numeric values.
* degap.idx: idx passed to degap.
* degaps.sync: sync passed to degap.
* degap.how: how passed to degap.
* degap.fill: fill passed to degap.
* norm.how: how passed to norm.
* denoise.n: n passed to denoise.
* denoise.how: how passed to denoise.

curl -H "Content-Type: application/json" --data '{"x":[[1,2.5,3,4,5.5,6,7,8],[1.5,3.5,4,4,5.5,6,7]],"degap.idx":[[0,2,4,8,10,14,16,18],[0,2,4,6,8,14,18]],"norm.how":"max","denoise.n":3,"denoise.how":"mean"} ' http://localhost:8000/degap_norm_denoise
#{"error":{},"result":[[0.125,0.2188,0.2708,0.3542,0.4167,0.5208,0.625,0.7083,0.7708,0.875],[0.2143,0.3571,0.4286,0.5476,0.6429,0.7143,0.7857,0.8095,0.8333,0.9048]],"type":"list","length":2}

Graphical representation of the function:

x = c(4,6.5,3,4,7.5,4,8,9)
idx = c(0,1,2,4,5,6,7,9)

((((((((Platzhalter Bild ))))))))

== dists ==
Computes time series distance statistics: autocorrelation, cross correlation, dynamic time warping, granger test p-value.
Arguments:
* x: first numeric series.
* y: second numeric series.
* granger.order: pass to granger test as order argument.

Note that x is not a list of numeric series but a single numeric series. Similarly y.

curl -H "Content-Type: application/json" --data '{"x":[-1.6106,-1.2703,-0.9301,-0.7032,-0.7032,-0.2495,0.431,0.431,0.6578,1.1115],"y":[-2.0944,-1.4692,-0.844,-0.5314,-0.5314,0.4064,0.4064,0.4064,0.719,0.719],"granger.order":5}' http://localhost:8000/dists
#{"error":{},"result":{"acf":[0.1071],"ccor":[0.3566],"dtw":[2.6025],"gran":[0]},"type":"list","length":4}

Granger test p-value may be 0 in case when its function raises aliased coefficients error or perfect fit warning.

= Horizontal scaling =
R package valve can provide concurrency for requests to R webservice API.

= Maintainer =
Jan Gorecki

EmoTouch R Webservice Dokumentation

2024-11-19T20:42:09Z

Aliebelt:

Hauptseite

2024-11-19T20:17:27Z

Aliebelt:

<languages />
<translate>


[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]


Willkommen im Wiki von emoTouch Web, dem Tool zur Echtzeitbegleitung und Feedback von performativen Prozessen von der Universität Osnabrück. Die hier aufgeführten Seiten beinhalten detaillierte Informationen, Tutorials und Anwendungsbeispiele.

== Arbeiten mit emoTouch == 
''' Projekte '''
* [[Projekte#Erstellen/ Bearbeiten | Erstellen/ Bearbeiten]]
* [[Projekte#Durchführen | Durchführen]]
* [[Projekte#Datenverarbeitung | Datenverarbeitung]]
* [[Projekte#Auswerten und Visualisieren | Auswerten & Visualisieren]]


''' Schritt-für-Schritt Anleitungen '''
* [[Erste Schritte zum eigenen Projekt]]


''' Anwendungsbeispiele '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen]]

== Zusammenarbeit == 
* [[Benutzer]]


''' Einbindung von anderen Tools/ in andere Tools '''
* [[SoSci Survey]]

== Allgemeine Informationen == 
* [[EmoTouch:Über emoTouch|Über emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)|Versionshistorie (emoTouch für iPad)]]
* [[Bisherige "continuous response" - Systeme]]
* [[Glossar]]

</translate>

Hauptseite

2024-11-19T20:16:41Z

Aliebelt:

<languages />
<translate>


[[Datei:Logo emoTouchWeb2.png|rahmenlos|rechts]]


Willkommen im Wiki von emoTouch Web, dem Tool zur Echtzeitbegleitung und Feedback von performativen Prozessen von der Universität Osnabrück. Die hier aufgeführten Seiten beinhalten detaillierte Informationen, Tutorials und Anwendungsbeispiele.

== Arbeiten mit emoTouch == 
''' Projekte '''
* [[Projekte#Erstellen/ Bearbeiten | Erstellen/ Bearbeiten]]
* [[Projekte#Durchführen | Durchführen]]
* [[Projekte#Datenverarbeitung | Datenverarbeitung]]
* [[Projekte#Auswerten und Visualisieren | Auswerten & Visualisieren]]


''' Schritt-für-Schritt Anleitungen '''
* [[Erste Schritte zum eigenen Projekt]]


''' Anwendungsbeispiele '''
* [[Anwendungsbeispiel: Bewertung von integrierten Medien]]
* [[Anwendungsbeispiel: Bewertung einer Live-Situation mit verschiedenen Skalen]]

== Zusammenarbeit == 
* [[Benutzer]]


''' Einbindung von anderen Tools/ in andere Tools '''
* [[SoSci Survey]]

== Allgemeine Informationen == 
* [[EmoTouch:Über emoTouch|Über emoTouch]]
* [[Versionshistorie_(emoTouch_für_iPad)|Versionshistorie (emoTouch für iPad)]]
* [[Bisherige "continuous response" - Systeme]]
* [[Glossar]]

[[test]]

</translate>

EmoTouch R Webservice Dokumentation

2024-11-19T20:16:00Z

Aliebelt: /* on R side */

= Additional documentation =
Additional documentation is served by swagger when running R web service:

<code> http://127.0.0.1:8000/__docs__/ </code>

= Results structure =
Results from R web service are always wrapped in a list to provide error handling and extra metadata about the returned object.

== on R side ==
In case of successfully computed request (of a function returning scalar integer value 3):

list(
error = <span style="color: purple;"> NULL</span>,
results = <span style="color: green;"> 3L</span>,
type = <span style="color: red;"> "integer"</span>,
length = <span style="color: green;"> 1L</span>
)

EmoTouch R Webservice Dokumentation

2024-11-19T20:15:40Z

Aliebelt: /* on R side */

= Additional documentation =
Additional documentation is served by swagger when running R web service:

<code> http://127.0.0.1:8000/__docs__/ </code>

= Results structure =
Results from R web service are always wrapped in a list to provide error handling and extra metadata about the returned object.

== on R side ==
In case of successfully computed request (of a function returning scalar integer value 3):

list(
error = <span style="color: purple;"> NULL </span> ,
results = <span style="color: green;"> 3L </span> ,
type = <span style="color: red;"> "integer" </span> ,
length = <span style="color: green;"> 1L </span>
)

EmoTouch R Webservice Dokumentation

2024-11-19T20:14:44Z

Aliebelt: Die Seite wurde neu angelegt: „= Additional documentation = Additional documentation is served by swagger when running R web service: <code> http://127.0.0.1:8000/__docs__/ </code> = Resu…“

= Additional documentation =
Additional documentation is served by swagger when running R web service:

<code> http://127.0.0.1:8000/__docs__/ </code>

= Results structure =
Results from R web service are always wrapped in a list to provide error handling and extra metadata about the returned object.

== on R side ==
In case of successfully computed request (of a function returning scalar integer value 3):

list(
error = <span style="color: purple;"> NULL,</span>
results = <span style="color: green;"> 3L, </span>
type = <span style="color: red;"> "integer", </span>
length = <span style="color: green;"> 1L </span>
)

Projekte

2024-11-19T14:40:03Z

Aliebelt:

<languages />
<translate>


[[File:EmoTouch Schaubild.png|caption|right|400px|Ebenen eines Projekts]]
Die Arbeit mit Projekten in emoTouch umfasst drei Hauptschritte: '''Erstellen, Durchführen''' und '''Auswerten'''. Alle Funktionen lassen sich in einen dieser drei Prozessschritte eingliedern. Seit Version 2.0 können die Daten nun auch im Anschluss oder live während der Durchführung '''visualisiert''' werden. Dieser Artikel bietet eine Übersicht für den Einstieg in die Software und ihre Möglichkeiten im Manager Interface.


Ist ein Projekt erstellt, können '''beliebig viele Durchführungen''' (Realisations) gestartet werden, an denen wiederum '''beliebig viele Personen''' (Sessions) teilnehmen können (siehe Grafik).

Wählen Sie zwischen zwei verschiedenen Varianten der Durchführung: "Live" oder "Playback".

In '''Playback-Projekten''' können Audio- oder Videodateien in das Projekt integriert werden und die Teilnehmenden navigieren selbstständig durch die Parts. Im Gegensatz dazu finden '''Live-Projekte''' parallel zu einem Event statt, auf dessen Grundlage Daten erhoben werden und der Manager navigiert alle Teilnehmenden gleichzeitig durch das Projekt.

== Erstellen/ Bearbeiten == 
Über den Reiter "Projekte" im Manager Interface verwalten oder bearbeiten Sie Ihre bereits erstellten oder freigegebenen Projekte und erstellen neue. Zum Bearbeiten klicken Sie auf eine Ihrer bereits vorhandenen Projekte. Um grundsätzliche Parameter wie die Auflösung zu verändern, nutzen Sie jeweils das „=“ Menü.
Zum Erstellen klicken Sie auf den „Neues Projekt“ Button.


→ [[Ein Projekt erstellen]]


Öffnen Sie eines Ihrer Projekte, können Sie diese im Editor designen.


→ [[Editor|Zum Artikel "Editor"]]


Optional: Wenn Sie einen Query-String an die an die Teilnehmenden zu verteilende URL anhängen möchten, folgen Sie der folgenden Anleitung.


→ [[Parameterübergabe]]

== Durchführen == 
Ist Ihr Projekt fertig designed, klicken Sie im Reiter "Durchführungen" auf "neue Durchführung".


→ [[Dialog: Durchführung erstellen]]


Es können von einem Projekt mehrere Durchführungen mit jeweils mehreren Sessions gleichzeitig laufen. Sie sind im Reiter "Durchführungen" aufgelistet. Klicken Sie auf eine Durchführung in der Liste, um Details anzusehen und sie zu verwalten und zu steuern.


→ [[Durchführungen verwalten]]

== Datenverarbeitung == 


Die erfassten Rohdaten können als CSV Datei exportiert und mit einer beliebigen Tabellenkalkulations- oder Statistiksoftware weiterverwertet werden. Klicken Sie dafür im Reiter "Durchführungen" auf die gewünschte Durchführung und anschließend auf den "exportieren"-Button oben rechts. Im darauf folgenden Dialogfeld konfigurieren Sie unter anderem das [[Zeitstempel-Formate|Zeitstempel-Format]] oder das [[Resampling]]. Sie können sich nun Zeitreihendaten und Metadaten im Tabellenformat herunterladen.


→ [[Zeitstempel-Formate]]


→ [[Datenexport|So lesen Sie die exportierte Tabelle]]


Für alle Analysen, die Berechnungen auf der Basis von mehreren Teilnehmern beinhalten (z.B. die Berechnung des Mittelwerts einer Schiebereglerposition über alle Teilnehmenden zu einem bestimmten Zeitstempel), müssen die erfassten Rohdaten von emoTouch in 'resampelte Daten' ('Resampled Data') umgewandelt werden.


→ [[Resampling|Zum Artikel "Resampling"]]


In Playback Projekten finden die Sessions gewöhnlich asynchron statt und die Daten werden daher vor der Auswertung vorverarbeitet und synchronisiert.


→ [[Datenvorverarbeitung und Synchronisierung von Playback Projekten |Zum Artikel "Datenvorverarbeitung und Synchronisierung von Playback Projekten"]]


Die Daten können Sie mit einer Software wie Microsoft Excel, SPSS, Open Office, Libre Office, Apple Numbers, etc. auswerten.


→ [[Datenexport und -Import für Microsoft Excel, SPSS und Co.]]

== Auswerten und Visualisieren == 


Das '''Chart Interface''' ermöglicht seit Version 2.0 sowohl die graphische Aufarbeitung gespeicherter Daten zurückliegender Durchführungen, als auch die Live-Ausgabe und Aufbereitung eingehender Daten aus einer gerade laufenden Durchführung.
Jedes Chart greift nach frei definierbaren Filter-Kriterien auf Live- und/oder Datenbank-Daten zu und kann diese in Form diverser Chart-Typen (z. B. Diagramme oder auch perspektivisch Tabellen oder numerische Auswertungsergebnisse) darstellen.


Für eine Übersicht aller aktuell verfügbaren Chart-Typen nutzen Sie den '''Hauptmenüpunkt "Charts"''' im Manager Interface.


Navigieren Sie innerhalb eines Projekts zum '''Reiter "Visualisierungen"''' für eine Übersicht aller bisher erstellten Visualisierungen für dieses Projekt und um neue zu erstellen.


→ [[Visualisierungen erstellen und konfigurieren]]


→ [[Charts hinzufügen und konfigurieren]]


→ [[Live Visualisierungen in ein laufendes Projekt integrieren| Live Visualisierungen in ein laufendes Projekt einpflegen]]


→ [[Neue Charts erstellen]]

→ [[emoTouch R Webservice Dokumentation | R Webservice]]

</translate>

Projekte

2024-11-18T10:33:11Z

Aliebelt:

Datenexport/en

2024-10-24T11:42:49Z

Aliebelt: Die Seite wurde neu angelegt: „Example of a typical emoTouch export“

<languages/>

‘’‘Export data of a completed realisation’‘’

[[Datei:Exportierte Tabelle.png|mini|Example of a typical emoTouch export]]

The collected raw data can be exported as a CSV file and further processed with any spreadsheet or statistical software. To do so, click on the desired realisation in the "Realisations" tab and then on the "Export" button in the top right corner. In the following dialogue box, you can configurate the time stamp format or the resampling, among other settings. You can now download time series data and metadata in table format.

'''Sync-Offset'''

The latency that occurs during communication between the device and the server is automatically measured and compensated. The offset that can occur as a result is displayed in the session info, but is already automatically corrected in the export. This means that the exported timestamps are directly comparable.

‘’‘Time zones’‘’

A timestamp including time zone offset is generated in the data, which is appended to the timestamp (possible formatting of the appendix: ‘UTC+2’). The manager interface is modified so that it displays the local time zone of the device used by default. However, other time zones can be selected.

'''Display of the scale start values'''

In playback projects, media can be played in the part and data, e.g. on scales, can be collected in parallel. If the medium is to be started manually by the participants, a pop-up window with a play dialogue appears at the beginning of the part. It is not yet possible to interact with the scale at this point.
Nevertheless, tick change events (with a negative time stamp) are generated in the export file, which show the initial value of the scale. This must be recorded in case the pointer is not moved by the participants.

== The columns of the exported file ==

{| class="wikitable"
|-
! The columns of the exported file !! Explanation
|-
| session_id || The ID of the current session (automatically created)
|-
| part || The name of the active part, or "Part n". "n" indicates the position of the part in the sequence.
|-
|part_counter || Indicates how often a part has been accessed repeatedly (repeated access to a part is possible, for example, in the case of randomisation). The first time it is accessed the counter shows "0", the first time it is repeated it shows "1", and so on.
|-
| object_id || The ID of the object that was interacted with. This can be, for example, a scale (automatically created).
|-
|object || Indicates the name or type of the corresponding object that was interacted with.
|-
| created_at || A time/date string in Unix millisecond format that can be used to read the time from when the event in question started.
|-
| created_at_relative || The relative time in milliseconds to the synchronisation event of the respective part.
|-
| type || The type of the current event. More detailed descriptions of the different event types are explained [[Special:MyLanguage/Datenexport#Ereignistypen|in the next chapter]].
|-
|x
|Here, different values can be generated depending on the event and object. Generally, the X-value is used for horizontal scales. In 2D scales, x and y values are generated.
|-
|y
|Here, different values can be generated depending on the event and object. Generally, the Y value is used for vertical scales. In 2D scales, x and y values are generated.
|-
|Position
| 2 values for geolocation of the participating device: ‘latitude/longitude’ & ‘Accuracy’ (accuracy in metres - the smaller the value, the more accurately the position is tracked). Values in this column can only be generated if the geolocalisation tool was added to a part in the editor before the realisation. Otherwise, the object is missing in the table or generates the value ‘null’. The ‘created at’ event for geolocalisation is triggered when the position of the device changes.
|-
| Key Values s1-s8/ i1-i8 || (relevant for combined emoTouch and [[SoSci Survey]] projects) Creates a number that matches the respective "Case" number in the exported SoSci Survey data. That way, the sessions from both tools can be assigned to one another. '''To be found in the table of the matadata'''.
|}

== Event types ==

{| class="wikitable"
|-
! Data (active interactions with the interface by the participant) !! Explanation
|-
| Pointerchange || Within a 2D scale, the participant has pressed the left mouse button and moved the mouse, or touched the touch screen and moved the finger/ stylus.
Note: Since version 1.6.1 (02.09.2022), the values of the pointer position within the 2D scale are standardised to values between 0 and 1. The point 0/0 is located in the lower-left corner of the scale. In earlier versions, the values output were the position of the pointer within the entire interface instead of within the scale. They thus varied depending on where the scale was positioned in the part.
|-
| Dblclick || The participant has double-clicked within a part.
|-
| Tickchange || The participant changes the value of a one-dimensional scale. The output X- or Y-value corresponds to the value of the selected step. The initial value of the scale is output as a tickchange event with a negative time stamp (see explanation text above).
|-
| Check || The participant changes the value of a multiple-choice category scale. A comma-separated list with labels of the selected options is printed.
|-
| Optionchange || he participant changes the value of a single-choice category scale. The label of the selected option is printed.
|-
| Button || A button was clicked.
|-
| Buttontap || A tap button was clicked. Two events are generated: one for pressing and one for releasing the button. This keeps track of how long the button was pressed.
|-
| Buttonsingle || The single-use button outputs its current state for each event: 0 for "not pressed", 1 for "pressed".
|-
| Buttontoggle || The toggle button was clicked and changed its status. It outputs its current state at each event like the single-use button: 0 for "not pressed", 1 for "pressed".
|-
! Meta (passively triggered events by interaction with the participant's device) !! Explanation
|-
| Part || The currently displayed part has changed. The event is triggered when the manager selects a different part from the current one in an ongoing live project and it is displayed in the Participant Interface. In a playback project, the event is selected when buttons in the participant interface have been used to navigate to another part and the new part is displayed.
|-
| Blur || emoTouch is running in the background. The event is triggered when the participant switches to another window, tab or application during an ongoing project.
|-
| Focus || The event is triggered when the Blur state is ended. The participant has switched back to the tab/window with emoTouch as the application currently running in the foreground.
|-
| Play || A medium starts playing.
|-
| Ytstatechanged || For an embedded YouTube video, certain values of the API are printed. For example, the time when the video actually starts playing. More information on this can be found at [https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status Documentation of the intersection]
|-
| Fullscreen || The display of the project is changed from window mode to fullscreen mode.
|-
| Orientationchange || The screen orientation of the user's mobile device is about to change. The event is triggered when the participant turns their mobile device 90° during an ongoing project.
|-
| Orientationchangeend || The screen orientation of the user's mobile device has fully changed. The event is triggered when the participant is done turning their mobile device 90° during an ongoing project.
|-
| End-Events || Are generated automatically for each interactive element for resampling.
|}

[[Datei:Integrierte Medien Play.png|mini|Integrated media: play dialogue]]

== Sources ==

* https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status (last access 28 Feb 2022).

Translations:Datenexport/20/en

2024-10-24T11:42:49Z

Aliebelt: Die Seite wurde neu angelegt: „Example of a typical emoTouch export“

[[Datei:Exportierte Tabelle.png|mini|Example of a typical emoTouch export]]

Datenexport/en

2024-10-24T11:42:34Z

Aliebelt:

<languages/>

‘’‘Export data of a completed realisation’‘’

[[Datei:Exportierte Tabelle.png|mini|Beispielhafte Darstellung eines typischen emoTouch-Exports]]

The collected raw data can be exported as a CSV file and further processed with any spreadsheet or statistical software. To do so, click on the desired realisation in the "Realisations" tab and then on the "Export" button in the top right corner. In the following dialogue box, you can configurate the time stamp format or the resampling, among other settings. You can now download time series data and metadata in table format.

'''Sync-Offset'''

The latency that occurs during communication between the device and the server is automatically measured and compensated. The offset that can occur as a result is displayed in the session info, but is already automatically corrected in the export. This means that the exported timestamps are directly comparable.

‘’‘Time zones’‘’

A timestamp including time zone offset is generated in the data, which is appended to the timestamp (possible formatting of the appendix: ‘UTC+2’). The manager interface is modified so that it displays the local time zone of the device used by default. However, other time zones can be selected.

'''Display of the scale start values'''

In playback projects, media can be played in the part and data, e.g. on scales, can be collected in parallel. If the medium is to be started manually by the participants, a pop-up window with a play dialogue appears at the beginning of the part. It is not yet possible to interact with the scale at this point.
Nevertheless, tick change events (with a negative time stamp) are generated in the export file, which show the initial value of the scale. This must be recorded in case the pointer is not moved by the participants.

== The columns of the exported file ==

{| class="wikitable"
|-
! The columns of the exported file !! Explanation
|-
| session_id || The ID of the current session (automatically created)
|-
| part || The name of the active part, or "Part n". "n" indicates the position of the part in the sequence.
|-
|part_counter || Indicates how often a part has been accessed repeatedly (repeated access to a part is possible, for example, in the case of randomisation). The first time it is accessed the counter shows "0", the first time it is repeated it shows "1", and so on.
|-
| object_id || The ID of the object that was interacted with. This can be, for example, a scale (automatically created).
|-
|object || Indicates the name or type of the corresponding object that was interacted with.
|-
| created_at || A time/date string in Unix millisecond format that can be used to read the time from when the event in question started.
|-
| created_at_relative || The relative time in milliseconds to the synchronisation event of the respective part.
|-
| type || The type of the current event. More detailed descriptions of the different event types are explained [[Special:MyLanguage/Datenexport#Ereignistypen|in the next chapter]].
|-
|x
|Here, different values can be generated depending on the event and object. Generally, the X-value is used for horizontal scales. In 2D scales, x and y values are generated.
|-
|y
|Here, different values can be generated depending on the event and object. Generally, the Y value is used for vertical scales. In 2D scales, x and y values are generated.
|-
|Position
| 2 values for geolocation of the participating device: ‘latitude/longitude’ & ‘Accuracy’ (accuracy in metres - the smaller the value, the more accurately the position is tracked). Values in this column can only be generated if the geolocalisation tool was added to a part in the editor before the realisation. Otherwise, the object is missing in the table or generates the value ‘null’. The ‘created at’ event for geolocalisation is triggered when the position of the device changes.
|-
| Key Values s1-s8/ i1-i8 || (relevant for combined emoTouch and [[SoSci Survey]] projects) Creates a number that matches the respective "Case" number in the exported SoSci Survey data. That way, the sessions from both tools can be assigned to one another. '''To be found in the table of the matadata'''.
|}

== Event types ==

{| class="wikitable"
|-
! Data (active interactions with the interface by the participant) !! Explanation
|-
| Pointerchange || Within a 2D scale, the participant has pressed the left mouse button and moved the mouse, or touched the touch screen and moved the finger/ stylus.
Note: Since version 1.6.1 (02.09.2022), the values of the pointer position within the 2D scale are standardised to values between 0 and 1. The point 0/0 is located in the lower-left corner of the scale. In earlier versions, the values output were the position of the pointer within the entire interface instead of within the scale. They thus varied depending on where the scale was positioned in the part.
|-
| Dblclick || The participant has double-clicked within a part.
|-
| Tickchange || The participant changes the value of a one-dimensional scale. The output X- or Y-value corresponds to the value of the selected step. The initial value of the scale is output as a tickchange event with a negative time stamp (see explanation text above).
|-
| Check || The participant changes the value of a multiple-choice category scale. A comma-separated list with labels of the selected options is printed.
|-
| Optionchange || he participant changes the value of a single-choice category scale. The label of the selected option is printed.
|-
| Button || A button was clicked.
|-
| Buttontap || A tap button was clicked. Two events are generated: one for pressing and one for releasing the button. This keeps track of how long the button was pressed.
|-
| Buttonsingle || The single-use button outputs its current state for each event: 0 for "not pressed", 1 for "pressed".
|-
| Buttontoggle || The toggle button was clicked and changed its status. It outputs its current state at each event like the single-use button: 0 for "not pressed", 1 for "pressed".
|-
! Meta (passively triggered events by interaction with the participant's device) !! Explanation
|-
| Part || The currently displayed part has changed. The event is triggered when the manager selects a different part from the current one in an ongoing live project and it is displayed in the Participant Interface. In a playback project, the event is selected when buttons in the participant interface have been used to navigate to another part and the new part is displayed.
|-
| Blur || emoTouch is running in the background. The event is triggered when the participant switches to another window, tab or application during an ongoing project.
|-
| Focus || The event is triggered when the Blur state is ended. The participant has switched back to the tab/window with emoTouch as the application currently running in the foreground.
|-
| Play || A medium starts playing.
|-
| Ytstatechanged || For an embedded YouTube video, certain values of the API are printed. For example, the time when the video actually starts playing. More information on this can be found at [https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status Documentation of the intersection]
|-
| Fullscreen || The display of the project is changed from window mode to fullscreen mode.
|-
| Orientationchange || The screen orientation of the user's mobile device is about to change. The event is triggered when the participant turns their mobile device 90° during an ongoing project.
|-
| Orientationchangeend || The screen orientation of the user's mobile device has fully changed. The event is triggered when the participant is done turning their mobile device 90° during an ongoing project.
|-
| End-Events || Are generated automatically for each interactive element for resampling.
|}

[[Datei:Integrierte Medien Play.png|mini|Integrated media: play dialogue]]

== Sources ==

* https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status (last access 28 Feb 2022).

Translations:Datenexport/11/en

2024-10-24T11:42:34Z

Aliebelt:

{| class="wikitable"
|-
! The columns of the exported file !! Explanation
|-
| session_id || The ID of the current session (automatically created)
|-
| part || The name of the active part, or "Part n". "n" indicates the position of the part in the sequence.
|-
|part_counter || Indicates how often a part has been accessed repeatedly (repeated access to a part is possible, for example, in the case of randomisation). The first time it is accessed the counter shows "0", the first time it is repeated it shows "1", and so on.
|-
| object_id || The ID of the object that was interacted with. This can be, for example, a scale (automatically created).
|-
|object || Indicates the name or type of the corresponding object that was interacted with.
|-
| created_at || A time/date string in Unix millisecond format that can be used to read the time from when the event in question started.
|-
| created_at_relative || The relative time in milliseconds to the synchronisation event of the respective part.
|-
| type || The type of the current event. More detailed descriptions of the different event types are explained [[Special:MyLanguage/Datenexport#Ereignistypen|in the next chapter]].
|-
|x
|Here, different values can be generated depending on the event and object. Generally, the X-value is used for horizontal scales. In 2D scales, x and y values are generated.
|-
|y
|Here, different values can be generated depending on the event and object. Generally, the Y value is used for vertical scales. In 2D scales, x and y values are generated.
|-
|Position
| 2 values for geolocation of the participating device: ‘latitude/longitude’ & ‘Accuracy’ (accuracy in metres - the smaller the value, the more accurately the position is tracked). Values in this column can only be generated if the geolocalisation tool was added to a part in the editor before the realisation. Otherwise, the object is missing in the table or generates the value ‘null’. The ‘created at’ event for geolocalisation is triggered when the position of the device changes.
|-
| Key Values s1-s8/ i1-i8 || (relevant for combined emoTouch and [[SoSci Survey]] projects) Creates a number that matches the respective "Case" number in the exported SoSci Survey data. That way, the sessions from both tools can be assigned to one another. '''To be found in the table of the matadata'''.
|}

Datenexport/en

2024-10-24T11:37:59Z

Aliebelt: Die Seite wurde neu angelegt: „A timestamp including time zone offset is generated in the data, which is appended to the timestamp (possible formatting of the appendix: ‘UTC+2’). The man…“

<languages/>

‘’‘Export data of a completed realisation’‘’

[[Datei:Exportierte Tabelle.png|mini|Beispielhafte Darstellung eines typischen emoTouch-Exports]]

The collected raw data can be exported as a CSV file and further processed with any spreadsheet or statistical software. To do so, click on the desired realisation in the "Realisations" tab and then on the "Export" button in the top right corner. In the following dialogue box, you can configurate the time stamp format or the resampling, among other settings. You can now download time series data and metadata in table format.

'''Sync-Offset'''

The latency that occurs during communication between the device and the server is automatically measured and compensated. The offset that can occur as a result is displayed in the session info, but is already automatically corrected in the export. This means that the exported timestamps are directly comparable.

‘’‘Time zones’‘’

A timestamp including time zone offset is generated in the data, which is appended to the timestamp (possible formatting of the appendix: ‘UTC+2’). The manager interface is modified so that it displays the local time zone of the device used by default. However, other time zones can be selected.

'''Display of the scale start values'''

In playback projects, media can be played in the part and data, e.g. on scales, can be collected in parallel. If the medium is to be started manually by the participants, a pop-up window with a play dialogue appears at the beginning of the part. It is not yet possible to interact with the scale at this point.
Nevertheless, tick change events (with a negative time stamp) are generated in the export file, which show the initial value of the scale. This must be recorded in case the pointer is not moved by the participants.

== The columns of the exported file ==

<div class="mw-translate-fuzzy">
{| class="wikitable"
|-
! The columns of the exported file !! Explanation
|-
| session_id || The ID of the current session (automatically created)
|-
| part || The name of the active part, or "Part n". "n" indicates the position of the part in the sequence.
|-
|part_counter || Indicates how often a part has been accessed repeatedly (repeated access to a part is possible, for example, in the case of randomisation). The first time it is accessed the counter shows "0", the first time it is repeated it shows "1", and so on.
|-
| object_id || The ID of the object that was interacted with. This can be, for example, a scale (automatically created).
|-
|object || Indicates the name or type of the corresponding object that was interacted with.
|-
| created_at || A time/date string in Unix millisecond format that can be used to read the time from when the event in question started.
|-
| created_at_relative || The relative time in milliseconds to the synchronisation event of the respective part.
|-
| type || The type of the current event. More detailed descriptions of the different event types are explained [[Special:MyLanguage/Datenexport#Ereignistypen|in the next chapter]].
|-
|x
|Here, different values can be generated depending on the event and object. Generally, the X-value is used for horizontal scales. In 2D scales, x and y values are generated.
|-
|y
|Here, different values can be generated depending on the event and object. Generally, the Y value is used for vertical scales. In 2D scales, x and y values are generated.
|-
| s1 || (relevant for combined emoTouch and [[SoSci Survey]] projects) Creates a number that matches the respective "Case" number in the exported SoSci Survey data. That way, the sessions from both tools can be assigned to one another. '''To be found in the table of the matadata'''.
|}
</div>

== Event types ==

{| class="wikitable"
|-
! Data (active interactions with the interface by the participant) !! Explanation
|-
| Pointerchange || Within a 2D scale, the participant has pressed the left mouse button and moved the mouse, or touched the touch screen and moved the finger/ stylus.
Note: Since version 1.6.1 (02.09.2022), the values of the pointer position within the 2D scale are standardised to values between 0 and 1. The point 0/0 is located in the lower-left corner of the scale. In earlier versions, the values output were the position of the pointer within the entire interface instead of within the scale. They thus varied depending on where the scale was positioned in the part.
|-
| Dblclick || The participant has double-clicked within a part.
|-
| Tickchange || The participant changes the value of a one-dimensional scale. The output X- or Y-value corresponds to the value of the selected step. The initial value of the scale is output as a tickchange event with a negative time stamp (see explanation text above).
|-
| Check || The participant changes the value of a multiple-choice category scale. A comma-separated list with labels of the selected options is printed.
|-
| Optionchange || he participant changes the value of a single-choice category scale. The label of the selected option is printed.
|-
| Button || A button was clicked.
|-
| Buttontap || A tap button was clicked. Two events are generated: one for pressing and one for releasing the button. This keeps track of how long the button was pressed.
|-
| Buttonsingle || The single-use button outputs its current state for each event: 0 for "not pressed", 1 for "pressed".
|-
| Buttontoggle || The toggle button was clicked and changed its status. It outputs its current state at each event like the single-use button: 0 for "not pressed", 1 for "pressed".
|-
! Meta (passively triggered events by interaction with the participant's device) !! Explanation
|-
| Part || The currently displayed part has changed. The event is triggered when the manager selects a different part from the current one in an ongoing live project and it is displayed in the Participant Interface. In a playback project, the event is selected when buttons in the participant interface have been used to navigate to another part and the new part is displayed.
|-
| Blur || emoTouch is running in the background. The event is triggered when the participant switches to another window, tab or application during an ongoing project.
|-
| Focus || The event is triggered when the Blur state is ended. The participant has switched back to the tab/window with emoTouch as the application currently running in the foreground.
|-
| Play || A medium starts playing.
|-
| Ytstatechanged || For an embedded YouTube video, certain values of the API are printed. For example, the time when the video actually starts playing. More information on this can be found at [https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status Documentation of the intersection]
|-
| Fullscreen || The display of the project is changed from window mode to fullscreen mode.
|-
| Orientationchange || The screen orientation of the user's mobile device is about to change. The event is triggered when the participant turns their mobile device 90° during an ongoing project.
|-
| Orientationchangeend || The screen orientation of the user's mobile device has fully changed. The event is triggered when the participant is done turning their mobile device 90° during an ongoing project.
|-
| End-Events || Are generated automatically for each interactive element for resampling.
|}

[[Datei:Integrierte Medien Play.png|mini|Integrated media: play dialogue]]

== Sources ==

* https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status (last access 28 Feb 2022).

Translations:Datenexport/23/en

2024-10-24T11:37:59Z

A timestamp including time zone offset is generated in the data, which is appended to the timestamp (possible formatting of the appendix: ‘UTC+2’). The manager interface is modified so that it displays the local time zone of the device used by default. However, other time zones can be selected.

Datenexport/en

2024-10-24T11:37:24Z

Aliebelt: Die Seite wurde neu angelegt: „‘’‘Time zones’‘’“

<languages/>

‘’‘Export data of a completed realisation’‘’

[[Datei:Exportierte Tabelle.png|mini|Beispielhafte Darstellung eines typischen emoTouch-Exports]]

The collected raw data can be exported as a CSV file and further processed with any spreadsheet or statistical software. To do so, click on the desired realisation in the "Realisations" tab and then on the "Export" button in the top right corner. In the following dialogue box, you can configurate the time stamp format or the resampling, among other settings. You can now download time series data and metadata in table format.

'''Sync-Offset'''

The latency that occurs during communication between the device and the server is automatically measured and compensated. The offset that can occur as a result is displayed in the session info, but is already automatically corrected in the export. This means that the exported timestamps are directly comparable.

‘’‘Time zones’‘’

Es wird in den Daten ein Zeitstempel inklusive Zeitzonenversatz erzeugt, welcher an den Zeitstempel angehängt ist (mögliche Formatierung des Anhangs: "UTC+2"). Das Manager Interface ist so modifiziert, dass es standardmäßig die lokale Zeitzone des genutzten Gerätes anzeigt. Andere Zeitzonen sind aber auswählbar.

'''Display of the scale start values'''

In playback projects, media can be played in the part and data, e.g. on scales, can be collected in parallel. If the medium is to be started manually by the participants, a pop-up window with a play dialogue appears at the beginning of the part. It is not yet possible to interact with the scale at this point.
Nevertheless, tick change events (with a negative time stamp) are generated in the export file, which show the initial value of the scale. This must be recorded in case the pointer is not moved by the participants.

== The columns of the exported file ==

<div class="mw-translate-fuzzy">
{| class="wikitable"
|-
! The columns of the exported file !! Explanation
|-
| session_id || The ID of the current session (automatically created)
|-
| part || The name of the active part, or "Part n". "n" indicates the position of the part in the sequence.
|-
|part_counter || Indicates how often a part has been accessed repeatedly (repeated access to a part is possible, for example, in the case of randomisation). The first time it is accessed the counter shows "0", the first time it is repeated it shows "1", and so on.
|-
| object_id || The ID of the object that was interacted with. This can be, for example, a scale (automatically created).
|-
|object || Indicates the name or type of the corresponding object that was interacted with.
|-
| created_at || A time/date string in Unix millisecond format that can be used to read the time from when the event in question started.
|-
| created_at_relative || The relative time in milliseconds to the synchronisation event of the respective part.
|-
| type || The type of the current event. More detailed descriptions of the different event types are explained [[Special:MyLanguage/Datenexport#Ereignistypen|in the next chapter]].
|-
|x
|Here, different values can be generated depending on the event and object. Generally, the X-value is used for horizontal scales. In 2D scales, x and y values are generated.
|-
|y
|Here, different values can be generated depending on the event and object. Generally, the Y value is used for vertical scales. In 2D scales, x and y values are generated.
|-
| s1 || (relevant for combined emoTouch and [[SoSci Survey]] projects) Creates a number that matches the respective "Case" number in the exported SoSci Survey data. That way, the sessions from both tools can be assigned to one another. '''To be found in the table of the matadata'''.
|}
</div>

== Event types ==

{| class="wikitable"
|-
! Data (active interactions with the interface by the participant) !! Explanation
|-
| Pointerchange || Within a 2D scale, the participant has pressed the left mouse button and moved the mouse, or touched the touch screen and moved the finger/ stylus.
Note: Since version 1.6.1 (02.09.2022), the values of the pointer position within the 2D scale are standardised to values between 0 and 1. The point 0/0 is located in the lower-left corner of the scale. In earlier versions, the values output were the position of the pointer within the entire interface instead of within the scale. They thus varied depending on where the scale was positioned in the part.
|-
| Dblclick || The participant has double-clicked within a part.
|-
| Tickchange || The participant changes the value of a one-dimensional scale. The output X- or Y-value corresponds to the value of the selected step. The initial value of the scale is output as a tickchange event with a negative time stamp (see explanation text above).
|-
| Check || The participant changes the value of a multiple-choice category scale. A comma-separated list with labels of the selected options is printed.
|-
| Optionchange || he participant changes the value of a single-choice category scale. The label of the selected option is printed.
|-
| Button || A button was clicked.
|-
| Buttontap || A tap button was clicked. Two events are generated: one for pressing and one for releasing the button. This keeps track of how long the button was pressed.
|-
| Buttonsingle || The single-use button outputs its current state for each event: 0 for "not pressed", 1 for "pressed".
|-
| Buttontoggle || The toggle button was clicked and changed its status. It outputs its current state at each event like the single-use button: 0 for "not pressed", 1 for "pressed".
|-
! Meta (passively triggered events by interaction with the participant's device) !! Explanation
|-
| Part || The currently displayed part has changed. The event is triggered when the manager selects a different part from the current one in an ongoing live project and it is displayed in the Participant Interface. In a playback project, the event is selected when buttons in the participant interface have been used to navigate to another part and the new part is displayed.
|-
| Blur || emoTouch is running in the background. The event is triggered when the participant switches to another window, tab or application during an ongoing project.
|-
| Focus || The event is triggered when the Blur state is ended. The participant has switched back to the tab/window with emoTouch as the application currently running in the foreground.
|-
| Play || A medium starts playing.
|-
| Ytstatechanged || For an embedded YouTube video, certain values of the API are printed. For example, the time when the video actually starts playing. More information on this can be found at [https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status Documentation of the intersection]
|-
| Fullscreen || The display of the project is changed from window mode to fullscreen mode.
|-
| Orientationchange || The screen orientation of the user's mobile device is about to change. The event is triggered when the participant turns their mobile device 90° during an ongoing project.
|-
| Orientationchangeend || The screen orientation of the user's mobile device has fully changed. The event is triggered when the participant is done turning their mobile device 90° during an ongoing project.
|-
| End-Events || Are generated automatically for each interactive element for resampling.
|}

[[Datei:Integrierte Medien Play.png|mini|Integrated media: play dialogue]]

== Sources ==

* https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status (last access 28 Feb 2022).

Translations:Datenexport/22/en

2024-10-24T11:37:24Z

Aliebelt: Die Seite wurde neu angelegt: „‘’‘Time zones’‘’“

‘’‘Time zones’‘’

Datenexport/en

2024-10-24T11:37:07Z

Aliebelt: Die Seite wurde neu angelegt: „The collected raw data can be exported as a CSV file and further processed with any spreadsheet or statistical software. To do so, click on the desired realisa…“

<languages/>

‘’‘Export data of a completed realisation’‘’

[[Datei:Exportierte Tabelle.png|mini|Beispielhafte Darstellung eines typischen emoTouch-Exports]]

The collected raw data can be exported as a CSV file and further processed with any spreadsheet or statistical software. To do so, click on the desired realisation in the "Realisations" tab and then on the "Export" button in the top right corner. In the following dialogue box, you can configurate the time stamp format or the resampling, among other settings. You can now download time series data and metadata in table format.

'''Sync-Offset'''

The latency that occurs during communication between the device and the server is automatically measured and compensated. The offset that can occur as a result is displayed in the session info, but is already automatically corrected in the export. This means that the exported timestamps are directly comparable.

'''Zeitzonen'''

Es wird in den Daten ein Zeitstempel inklusive Zeitzonenversatz erzeugt, welcher an den Zeitstempel angehängt ist (mögliche Formatierung des Anhangs: "UTC+2"). Das Manager Interface ist so modifiziert, dass es standardmäßig die lokale Zeitzone des genutzten Gerätes anzeigt. Andere Zeitzonen sind aber auswählbar.

'''Display of the scale start values'''

In playback projects, media can be played in the part and data, e.g. on scales, can be collected in parallel. If the medium is to be started manually by the participants, a pop-up window with a play dialogue appears at the beginning of the part. It is not yet possible to interact with the scale at this point.
Nevertheless, tick change events (with a negative time stamp) are generated in the export file, which show the initial value of the scale. This must be recorded in case the pointer is not moved by the participants.

== The columns of the exported file ==

<div class="mw-translate-fuzzy">
{| class="wikitable"
|-
! The columns of the exported file !! Explanation
|-
| session_id || The ID of the current session (automatically created)
|-
| part || The name of the active part, or "Part n". "n" indicates the position of the part in the sequence.
|-
|part_counter || Indicates how often a part has been accessed repeatedly (repeated access to a part is possible, for example, in the case of randomisation). The first time it is accessed the counter shows "0", the first time it is repeated it shows "1", and so on.
|-
| object_id || The ID of the object that was interacted with. This can be, for example, a scale (automatically created).
|-
|object || Indicates the name or type of the corresponding object that was interacted with.
|-
| created_at || A time/date string in Unix millisecond format that can be used to read the time from when the event in question started.
|-
| created_at_relative || The relative time in milliseconds to the synchronisation event of the respective part.
|-
| type || The type of the current event. More detailed descriptions of the different event types are explained [[Special:MyLanguage/Datenexport#Ereignistypen|in the next chapter]].
|-
|x
|Here, different values can be generated depending on the event and object. Generally, the X-value is used for horizontal scales. In 2D scales, x and y values are generated.
|-
|y
|Here, different values can be generated depending on the event and object. Generally, the Y value is used for vertical scales. In 2D scales, x and y values are generated.
|-
| s1 || (relevant for combined emoTouch and [[SoSci Survey]] projects) Creates a number that matches the respective "Case" number in the exported SoSci Survey data. That way, the sessions from both tools can be assigned to one another. '''To be found in the table of the matadata'''.
|}
</div>

== Event types ==

{| class="wikitable"
|-
! Data (active interactions with the interface by the participant) !! Explanation
|-
| Pointerchange || Within a 2D scale, the participant has pressed the left mouse button and moved the mouse, or touched the touch screen and moved the finger/ stylus.
Note: Since version 1.6.1 (02.09.2022), the values of the pointer position within the 2D scale are standardised to values between 0 and 1. The point 0/0 is located in the lower-left corner of the scale. In earlier versions, the values output were the position of the pointer within the entire interface instead of within the scale. They thus varied depending on where the scale was positioned in the part.
|-
| Dblclick || The participant has double-clicked within a part.
|-
| Tickchange || The participant changes the value of a one-dimensional scale. The output X- or Y-value corresponds to the value of the selected step. The initial value of the scale is output as a tickchange event with a negative time stamp (see explanation text above).
|-
| Check || The participant changes the value of a multiple-choice category scale. A comma-separated list with labels of the selected options is printed.
|-
| Optionchange || he participant changes the value of a single-choice category scale. The label of the selected option is printed.
|-
| Button || A button was clicked.
|-
| Buttontap || A tap button was clicked. Two events are generated: one for pressing and one for releasing the button. This keeps track of how long the button was pressed.
|-
| Buttonsingle || The single-use button outputs its current state for each event: 0 for "not pressed", 1 for "pressed".
|-
| Buttontoggle || The toggle button was clicked and changed its status. It outputs its current state at each event like the single-use button: 0 for "not pressed", 1 for "pressed".
|-
! Meta (passively triggered events by interaction with the participant's device) !! Explanation
|-
| Part || The currently displayed part has changed. The event is triggered when the manager selects a different part from the current one in an ongoing live project and it is displayed in the Participant Interface. In a playback project, the event is selected when buttons in the participant interface have been used to navigate to another part and the new part is displayed.
|-
| Blur || emoTouch is running in the background. The event is triggered when the participant switches to another window, tab or application during an ongoing project.
|-
| Focus || The event is triggered when the Blur state is ended. The participant has switched back to the tab/window with emoTouch as the application currently running in the foreground.
|-
| Play || A medium starts playing.
|-
| Ytstatechanged || For an embedded YouTube video, certain values of the API are printed. For example, the time when the video actually starts playing. More information on this can be found at [https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status Documentation of the intersection]
|-
| Fullscreen || The display of the project is changed from window mode to fullscreen mode.
|-
| Orientationchange || The screen orientation of the user's mobile device is about to change. The event is triggered when the participant turns their mobile device 90° during an ongoing project.
|-
| Orientationchangeend || The screen orientation of the user's mobile device has fully changed. The event is triggered when the participant is done turning their mobile device 90° during an ongoing project.
|-
| End-Events || Are generated automatically for each interactive element for resampling.
|}

[[Datei:Integrierte Medien Play.png|mini|Integrated media: play dialogue]]

== Sources ==

* https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status (last access 28 Feb 2022).

Translations:Datenexport/21/en

2024-10-24T11:37:07Z

The collected raw data can be exported as a CSV file and further processed with any spreadsheet or statistical software. To do so, click on the desired realisation in the "Realisations" tab and then on the "Export" button in the top right corner. In the following dialogue box, you can configurate the time stamp format or the resampling, among other settings. You can now download time series data and metadata in table format.

Datenexport/en

2024-10-24T11:36:22Z

Aliebelt:

<languages/>

‘’‘Export data of a completed realisation’‘’

[[Datei:Exportierte Tabelle.png|mini|Beispielhafte Darstellung eines typischen emoTouch-Exports]]

Die erfassten Rohdaten können als CSV Datei exportiert und mit einer beliebigen Tabellenkalkulations- oder Statistiksoftware weiterverwertet werden. Klicken Sie dafür im Reiter "Durchführungen" auf die gewünschte Durchführung und anschließend auf den "exportieren"-Button oben rechts. Im darauf folgenden Dialogfeld konfigurieren Sie unter anderem das Zeitstempel-Format oder das Resampling. Sie können sich nun Zeitreihendaten und Metadaten im Tabellenformat herunterladen.

'''Sync-Offset'''

The latency that occurs during communication between the device and the server is automatically measured and compensated. The offset that can occur as a result is displayed in the session info, but is already automatically corrected in the export. This means that the exported timestamps are directly comparable.

'''Zeitzonen'''

Es wird in den Daten ein Zeitstempel inklusive Zeitzonenversatz erzeugt, welcher an den Zeitstempel angehängt ist (mögliche Formatierung des Anhangs: "UTC+2"). Das Manager Interface ist so modifiziert, dass es standardmäßig die lokale Zeitzone des genutzten Gerätes anzeigt. Andere Zeitzonen sind aber auswählbar.

'''Display of the scale start values'''

In playback projects, media can be played in the part and data, e.g. on scales, can be collected in parallel. If the medium is to be started manually by the participants, a pop-up window with a play dialogue appears at the beginning of the part. It is not yet possible to interact with the scale at this point.
Nevertheless, tick change events (with a negative time stamp) are generated in the export file, which show the initial value of the scale. This must be recorded in case the pointer is not moved by the participants.

== The columns of the exported file ==

<div class="mw-translate-fuzzy">
{| class="wikitable"
|-
! The columns of the exported file !! Explanation
|-
| session_id || The ID of the current session (automatically created)
|-
| part || The name of the active part, or "Part n". "n" indicates the position of the part in the sequence.
|-
|part_counter || Indicates how often a part has been accessed repeatedly (repeated access to a part is possible, for example, in the case of randomisation). The first time it is accessed the counter shows "0", the first time it is repeated it shows "1", and so on.
|-
| object_id || The ID of the object that was interacted with. This can be, for example, a scale (automatically created).
|-
|object || Indicates the name or type of the corresponding object that was interacted with.
|-
| created_at || A time/date string in Unix millisecond format that can be used to read the time from when the event in question started.
|-
| created_at_relative || The relative time in milliseconds to the synchronisation event of the respective part.
|-
| type || The type of the current event. More detailed descriptions of the different event types are explained [[Special:MyLanguage/Datenexport#Ereignistypen|in the next chapter]].
|-
|x
|Here, different values can be generated depending on the event and object. Generally, the X-value is used for horizontal scales. In 2D scales, x and y values are generated.
|-
|y
|Here, different values can be generated depending on the event and object. Generally, the Y value is used for vertical scales. In 2D scales, x and y values are generated.
|-
| s1 || (relevant for combined emoTouch and [[SoSci Survey]] projects) Creates a number that matches the respective "Case" number in the exported SoSci Survey data. That way, the sessions from both tools can be assigned to one another. '''To be found in the table of the matadata'''.
|}
</div>

== Event types ==

{| class="wikitable"
|-
! Data (active interactions with the interface by the participant) !! Explanation
|-
| Pointerchange || Within a 2D scale, the participant has pressed the left mouse button and moved the mouse, or touched the touch screen and moved the finger/ stylus.
Note: Since version 1.6.1 (02.09.2022), the values of the pointer position within the 2D scale are standardised to values between 0 and 1. The point 0/0 is located in the lower-left corner of the scale. In earlier versions, the values output were the position of the pointer within the entire interface instead of within the scale. They thus varied depending on where the scale was positioned in the part.
|-
| Dblclick || The participant has double-clicked within a part.
|-
| Tickchange || The participant changes the value of a one-dimensional scale. The output X- or Y-value corresponds to the value of the selected step. The initial value of the scale is output as a tickchange event with a negative time stamp (see explanation text above).
|-
| Check || The participant changes the value of a multiple-choice category scale. A comma-separated list with labels of the selected options is printed.
|-
| Optionchange || he participant changes the value of a single-choice category scale. The label of the selected option is printed.
|-
| Button || A button was clicked.
|-
| Buttontap || A tap button was clicked. Two events are generated: one for pressing and one for releasing the button. This keeps track of how long the button was pressed.
|-
| Buttonsingle || The single-use button outputs its current state for each event: 0 for "not pressed", 1 for "pressed".
|-
| Buttontoggle || The toggle button was clicked and changed its status. It outputs its current state at each event like the single-use button: 0 for "not pressed", 1 for "pressed".
|-
! Meta (passively triggered events by interaction with the participant's device) !! Explanation
|-
| Part || The currently displayed part has changed. The event is triggered when the manager selects a different part from the current one in an ongoing live project and it is displayed in the Participant Interface. In a playback project, the event is selected when buttons in the participant interface have been used to navigate to another part and the new part is displayed.
|-
| Blur || emoTouch is running in the background. The event is triggered when the participant switches to another window, tab or application during an ongoing project.
|-
| Focus || The event is triggered when the Blur state is ended. The participant has switched back to the tab/window with emoTouch as the application currently running in the foreground.
|-
| Play || A medium starts playing.
|-
| Ytstatechanged || For an embedded YouTube video, certain values of the API are printed. For example, the time when the video actually starts playing. More information on this can be found at [https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status Documentation of the intersection]
|-
| Fullscreen || The display of the project is changed from window mode to fullscreen mode.
|-
| Orientationchange || The screen orientation of the user's mobile device is about to change. The event is triggered when the participant turns their mobile device 90° during an ongoing project.
|-
| Orientationchangeend || The screen orientation of the user's mobile device has fully changed. The event is triggered when the participant is done turning their mobile device 90° during an ongoing project.
|-
| End-Events || Are generated automatically for each interactive element for resampling.
|}

[[Datei:Integrierte Medien Play.png|mini|Integrated media: play dialogue]]

== Sources ==

* https://developers.google.com/youtube/iframe_api_reference?hl=de#Playback_status (last access 28 Feb 2022).

Translations:Datenexport/7/en

2024-10-24T11:36:22Z

Aliebelt:

‘’‘Export data of a completed realisation’‘’

Erste Schritte zum eigenen Projekt/en

2024-10-24T11:33:44Z

Aliebelt: Die Seite wurde neu angelegt: „=== Resampling === For all analyses that involve calculations based on several participants (e.g. calculating the mean value of a slider position across all pa…“

<languages/>

Here you can follow all the steps involved in conducting a project with emoTouch, from preparation to evaluation.
A playback project for real-time data collection while listening to a piece of music is created as an example.

In playback projects, audio or video files are integrated into the project and the participants navigate through the parts themselves. In contrast, live projects take place simultaneously with an event, on the basis of which data is collected and the manager navigates all participants through the project all at once.

== Preparation/ considerations ==
Depending on the research context, preparatory work involves various steps. In this exemplary project, the following steps can be helpful in preparation:
* What data should be collected?
* Which form of questioning (e.g. which type of scale) best suits the survey?

== Registering and creating a project ==

<gallery widths=300px heights=200px>

Datei:01 Website Login.png|Register or log in to www.emotouch.de at no charge.

Datei:02 Studien Reiter.png|Click on ‘+NEW PROJECT’ in the ‘Projects’ tab.

Datei:03 Studie erstellen.png|In the ‘Create a project’ dialogue window, select a name for the project. You can make further adjustments or work with the default settings.

</gallery>

The project has now been created and you will be forwarded to the editor.

=== Designing the project ===

<gallery widths=300px heights=200px>

Datei:04 Editor.png|A project usually consists of several parts which, like presentation slides, provide an interactive surface on which data can be collected, information presented or audio and video files played (particularly useful for playback projects).

Datei:05 Passive Elemente.png|The editor offers numerous options for customising the individual parts of your project.

</gallery>

You can:
* Add passive elements (decorative/ informative)
* Create text boxes
* Embed audio and video files
* Embed buttons and links
* Integrate interactive websites with iframes
* Create and personalise 1D and 2D scales for real-time data acquisition

==== Integrate audio and video files ====

<gallery widths=300px heights=200px>

Datei:07 Audio einfügen.png|Click the ‘Add audio’ button.

Datei:06 Audio hochladen.png|Upload a file here or select an audio from the 'Files' tab that you have previously uploaded there.

</gallery>

==== Real-time data acquisition: use of scales (sliders) ====

<gallery widths=300px heights=200px>

Datei:09 Skala einfügen.png|The 1D scales shaped like sliders can be easily added as an element and further customised and personalised in the inspector.

Datei:10 Skala beschriften .png| Customise the alignment, values and step intervals according to your needs.

</gallery>

Data collection is always linked to an event (e.g. a piece of music). Create as many parts as you like for different events, which you or the participants can navigate through during realisation.

== Realisation ==
=== Create realisation ===

<gallery widths=300px heights=200px>

Datei:11 Durchführung-Reiter.png|Save the project and click on ‘New realisation’ in the ‘’Realisations‘’ tab.

Datei:12 Durchführung erstellen Dialog.png| Give the realisation a title and shortcode and set the starting time. You can either activate the realisation now or schedule it to start at a later time.

Datei:13 Durchführung Übersicht.png|emoTouch now creates a QR code, a link and a shortcode that participants can use to join the event without registering. The shortcode can be entered on www.emotouch.de.

</gallery>

=== Managing Realisations ===
<gallery widths=300px heights=200px>

Datei:14 Liste Durchführungen.png|Keep an overview of planned, ongoing and completed realisations in the "Realisations" tab. Any number of participants can join a running realisation. They each create a ‘session’. Click on a realisation in the list for an overview of the sessions that have been created.

</gallery>

You can run several active realisations at the same time. Caution: Pausing is not possible. Ending a realisation will terminate it permanently.

== Analysing - exporting values and data ==

<gallery widths=300px heights=200px>
Datei:15 Zum Export Button.png|Close the realisation when you have collected all of the desired data. Click on the ‘’‘completed’‘’' realisation that you want to analyse and click the “EXPORT” button.

Datei:16 Daten exportieren Dialog.png|Configure formatting details. emoTouch creates a CSV file with the raw data, or optionally resampled data, which can be further processed with any spreadsheet or statistics software.

</gallery>

Exportierbar sind:
* Zeitreihendaten
* Finale Zeitreihendaten
* Sitzungs-Metadaten
* Objekt-Metadaten

=== Resampling ===
For all analyses that involve calculations based on several participants (e.g. calculating the mean value of a slider position across all participants at a specific time stamp), the raw data recorded by emoTouch must be converted into ‘resampled data’.

Translations:Erste Schritte zum eigenen Projekt/19/en

2024-10-24T11:33:44Z

=== Resampling ===
For all analyses that involve calculations based on several participants (e.g. calculating the mean value of a slider position across all participants at a specific time stamp), the raw data recorded by emoTouch must be converted into ‘resampled data’.

Translations:Erste Schritte zum eigenen Projekt/18/en

2024-10-24T11:32:34Z

Aliebelt: Die Seite wurde neu angelegt: „Exportierbar sind: * Zeitreihendaten * Finale Zeitreihendaten * Sitzungs-Metadaten * Objekt-Metadaten“

Exportierbar sind:
* Zeitreihendaten
* Finale Zeitreihendaten
* Sitzungs-Metadaten
* Objekt-Metadaten

Erste Schritte zum eigenen Projekt/en

2024-10-24T11:31:02Z

Aliebelt: Die Seite wurde neu angelegt: „== Analysing - exporting values and data == <gallery widths=300px heights=200px> Datei:15 Zum Export Button.png|Close the realisation when you have collected…“

<languages/>

Here you can follow all the steps involved in conducting a project with emoTouch, from preparation to evaluation.
A playback project for real-time data collection while listening to a piece of music is created as an example.

In playback projects, audio or video files are integrated into the project and the participants navigate through the parts themselves. In contrast, live projects take place simultaneously with an event, on the basis of which data is collected and the manager navigates all participants through the project all at once.

== Preparation/ considerations ==
Depending on the research context, preparatory work involves various steps. In this exemplary project, the following steps can be helpful in preparation:
* What data should be collected?
* Which form of questioning (e.g. which type of scale) best suits the survey?

== Registering and creating a project ==

<gallery widths=300px heights=200px>

Datei:01 Website Login.png|Register or log in to www.emotouch.de at no charge.

Datei:02 Studien Reiter.png|Click on ‘+NEW PROJECT’ in the ‘Projects’ tab.

Datei:03 Studie erstellen.png|In the ‘Create a project’ dialogue window, select a name for the project. You can make further adjustments or work with the default settings.

</gallery>

The project has now been created and you will be forwarded to the editor.

=== Designing the project ===

<gallery widths=300px heights=200px>

Datei:04 Editor.png|A project usually consists of several parts which, like presentation slides, provide an interactive surface on which data can be collected, information presented or audio and video files played (particularly useful for playback projects).

Datei:05 Passive Elemente.png|The editor offers numerous options for customising the individual parts of your project.

</gallery>

You can:
* Add passive elements (decorative/ informative)
* Create text boxes
* Embed audio and video files
* Embed buttons and links
* Integrate interactive websites with iframes
* Create and personalise 1D and 2D scales for real-time data acquisition

==== Integrate audio and video files ====

<gallery widths=300px heights=200px>

Datei:07 Audio einfügen.png|Click the ‘Add audio’ button.

Datei:06 Audio hochladen.png|Upload a file here or select an audio from the 'Files' tab that you have previously uploaded there.

</gallery>

==== Real-time data acquisition: use of scales (sliders) ====

<gallery widths=300px heights=200px>

Datei:09 Skala einfügen.png|The 1D scales shaped like sliders can be easily added as an element and further customised and personalised in the inspector.

Datei:10 Skala beschriften .png| Customise the alignment, values and step intervals according to your needs.

</gallery>

Data collection is always linked to an event (e.g. a piece of music). Create as many parts as you like for different events, which you or the participants can navigate through during realisation.

== Realisation ==
=== Create realisation ===

<gallery widths=300px heights=200px>

Datei:11 Durchführung-Reiter.png|Save the project and click on ‘New realisation’ in the ‘’Realisations‘’ tab.

Datei:12 Durchführung erstellen Dialog.png| Give the realisation a title and shortcode and set the starting time. You can either activate the realisation now or schedule it to start at a later time.

Datei:13 Durchführung Übersicht.png|emoTouch now creates a QR code, a link and a shortcode that participants can use to join the event without registering. The shortcode can be entered on www.emotouch.de.

</gallery>

=== Managing Realisations ===
<gallery widths=300px heights=200px>

Datei:14 Liste Durchführungen.png|Keep an overview of planned, ongoing and completed realisations in the "Realisations" tab. Any number of participants can join a running realisation. They each create a ‘session’. Click on a realisation in the list for an overview of the sessions that have been created.

</gallery>

You can run several active realisations at the same time. Caution: Pausing is not possible. Ending a realisation will terminate it permanently.

== Analysing - exporting values and data ==

<gallery widths=300px heights=200px>
Datei:15 Zum Export Button.png|Close the realisation when you have collected all of the desired data. Click on the ‘’‘completed’‘’' realisation that you want to analyse and click the “EXPORT” button.

Datei:16 Daten exportieren Dialog.png|Configure formatting details. emoTouch creates a CSV file with the raw data, or optionally resampled data, which can be further processed with any spreadsheet or statistics software.

</gallery>

Exportierbar sind:
* Zeitreihendaten
* Finale Zeitreihendaten
* Sitzungs-Metadaten
* Objekt-Metadaten

=== Resampling ===
Für alle Analysen, die Berechnungen auf der Basis von mehreren Teilnehmern beinhalten (z.B. die Berechnung des Mittelwerts einer Schiebereglerposition über alle Teilnehmer zu einem bestimmten Zeitstempel), müssen die erfassten Rohdaten von emoTouch in 'resampelte Daten' ('Resampled Data') umgewandelt werden.

Translations:Erste Schritte zum eigenen Projekt/17/en

2024-10-24T11:31:01Z

== Analysing - exporting values and data ==

<gallery widths=300px heights=200px>
Datei:15 Zum Export Button.png|Close the realisation when you have collected all of the desired data. Click on the ‘’‘completed’‘’' realisation that you want to analyse and click the “EXPORT” button.

Datei:16 Daten exportieren Dialog.png|Configure formatting details. emoTouch creates a CSV file with the raw data, or optionally resampled data, which can be further processed with any spreadsheet or statistics software.

</gallery>

Erste Schritte zum eigenen Projekt/en

2024-10-24T11:22:22Z

Aliebelt: Die Seite wurde neu angelegt: „You can run several active realisations at the same time. Caution: Pausing is not possible. Ending a realisation will terminate it permanently.“

<languages/>

Here you can follow all the steps involved in conducting a project with emoTouch, from preparation to evaluation.
A playback project for real-time data collection while listening to a piece of music is created as an example.

In playback projects, audio or video files are integrated into the project and the participants navigate through the parts themselves. In contrast, live projects take place simultaneously with an event, on the basis of which data is collected and the manager navigates all participants through the project all at once.

== Preparation/ considerations ==
Depending on the research context, preparatory work involves various steps. In this exemplary project, the following steps can be helpful in preparation:
* What data should be collected?
* Which form of questioning (e.g. which type of scale) best suits the survey?

== Registering and creating a project ==

<gallery widths=300px heights=200px>

Datei:01 Website Login.png|Register or log in to www.emotouch.de at no charge.

Datei:02 Studien Reiter.png|Click on ‘+NEW PROJECT’ in the ‘Projects’ tab.

Datei:03 Studie erstellen.png|In the ‘Create a project’ dialogue window, select a name for the project. You can make further adjustments or work with the default settings.

</gallery>

The project has now been created and you will be forwarded to the editor.

=== Designing the project ===

<gallery widths=300px heights=200px>

Datei:04 Editor.png|A project usually consists of several parts which, like presentation slides, provide an interactive surface on which data can be collected, information presented or audio and video files played (particularly useful for playback projects).

Datei:05 Passive Elemente.png|The editor offers numerous options for customising the individual parts of your project.

</gallery>

You can:
* Add passive elements (decorative/ informative)
* Create text boxes
* Embed audio and video files
* Embed buttons and links
* Integrate interactive websites with iframes
* Create and personalise 1D and 2D scales for real-time data acquisition

==== Integrate audio and video files ====

<gallery widths=300px heights=200px>

Datei:07 Audio einfügen.png|Click the ‘Add audio’ button.

Datei:06 Audio hochladen.png|Upload a file here or select an audio from the 'Files' tab that you have previously uploaded there.

</gallery>

==== Real-time data acquisition: use of scales (sliders) ====

<gallery widths=300px heights=200px>

Datei:09 Skala einfügen.png|The 1D scales shaped like sliders can be easily added as an element and further customised and personalised in the inspector.

Datei:10 Skala beschriften .png| Customise the alignment, values and step intervals according to your needs.

</gallery>

Data collection is always linked to an event (e.g. a piece of music). Create as many parts as you like for different events, which you or the participants can navigate through during realisation.

== Realisation ==
=== Create realisation ===

<gallery widths=300px heights=200px>

Datei:11 Durchführung-Reiter.png|Save the project and click on ‘New realisation’ in the ‘’Realisations‘’ tab.

Datei:12 Durchführung erstellen Dialog.png| Give the realisation a title and shortcode and set the starting time. You can either activate the realisation now or schedule it to start at a later time.

Datei:13 Durchführung Übersicht.png|emoTouch now creates a QR code, a link and a shortcode that participants can use to join the event without registering. The shortcode can be entered on www.emotouch.de.

</gallery>

=== Managing Realisations ===
<gallery widths=300px heights=200px>

Datei:14 Liste Durchführungen.png|Keep an overview of planned, ongoing and completed realisations in the "Realisations" tab. Any number of participants can join a running realisation. They each create a ‘session’. Click on a realisation in the list for an overview of the sessions that have been created.

</gallery>

You can run several active realisations at the same time. Caution: Pausing is not possible. Ending a realisation will terminate it permanently.

== Auswerten - Werte und Daten exportieren ==
<gallery widths=300px heights=200px>
Datei:15 Zum Export Button.png|Beenden Sie die Durchführung, wenn Sie alle benötigten Daten erhoben haben. Klicken Sie in die '''abgeschlossene''' Durchführung, die Sie auswerten wollen und klicken Sie den "EXPORTIEREN" - Button.
Datei:16 Daten exportieren Dialog.png|Konfigurieren Sie Formatierungsdetails. emoTouch erstellt eine CSV Datei mit den Rohdaten, oder wahlweise resampelten Daten, die mit einer beliebigen Tabellenkalkulations- oder Statistiksoftware weiterverwertet werden kann.
</gallery>

Exportierbar sind:
* Zeitreihendaten
* Finale Zeitreihendaten
* Sitzungs-Metadaten
* Objekt-Metadaten

=== Resampling ===
Für alle Analysen, die Berechnungen auf der Basis von mehreren Teilnehmern beinhalten (z.B. die Berechnung des Mittelwerts einer Schiebereglerposition über alle Teilnehmer zu einem bestimmten Zeitstempel), müssen die erfassten Rohdaten von emoTouch in 'resampelte Daten' ('Resampled Data') umgewandelt werden.

Translations:Erste Schritte zum eigenen Projekt/16/en

2024-10-24T11:22:22Z

Aliebelt: Die Seite wurde neu angelegt: „You can run several active realisations at the same time. Caution: Pausing is not possible. Ending a realisation will terminate it permanently.“

You can run several active realisations at the same time. Caution: Pausing is not possible. Ending a realisation will terminate it permanently.

Erste Schritte zum eigenen Projekt/en

2024-10-24T11:20:00Z

Aliebelt: Die Seite wurde neu angelegt: „=== Managing Realisations === <gallery widths=300px heights=200px> Datei:14 Liste Durchführungen.png|Keep an overview of planned, ongoing and completed reali…“

<languages/>

Here you can follow all the steps involved in conducting a project with emoTouch, from preparation to evaluation.
A playback project for real-time data collection while listening to a piece of music is created as an example.

In playback projects, audio or video files are integrated into the project and the participants navigate through the parts themselves. In contrast, live projects take place simultaneously with an event, on the basis of which data is collected and the manager navigates all participants through the project all at once.

== Preparation/ considerations ==
Depending on the research context, preparatory work involves various steps. In this exemplary project, the following steps can be helpful in preparation:
* What data should be collected?
* Which form of questioning (e.g. which type of scale) best suits the survey?

== Registering and creating a project ==

<gallery widths=300px heights=200px>

Datei:01 Website Login.png|Register or log in to www.emotouch.de at no charge.

Datei:02 Studien Reiter.png|Click on ‘+NEW PROJECT’ in the ‘Projects’ tab.

Datei:03 Studie erstellen.png|In the ‘Create a project’ dialogue window, select a name for the project. You can make further adjustments or work with the default settings.

</gallery>

The project has now been created and you will be forwarded to the editor.

=== Designing the project ===

<gallery widths=300px heights=200px>

Datei:04 Editor.png|A project usually consists of several parts which, like presentation slides, provide an interactive surface on which data can be collected, information presented or audio and video files played (particularly useful for playback projects).

Datei:05 Passive Elemente.png|The editor offers numerous options for customising the individual parts of your project.

</gallery>

You can:
* Add passive elements (decorative/ informative)
* Create text boxes
* Embed audio and video files
* Embed buttons and links
* Integrate interactive websites with iframes
* Create and personalise 1D and 2D scales for real-time data acquisition

==== Integrate audio and video files ====

<gallery widths=300px heights=200px>

Datei:07 Audio einfügen.png|Click the ‘Add audio’ button.

Datei:06 Audio hochladen.png|Upload a file here or select an audio from the 'Files' tab that you have previously uploaded there.

</gallery>

==== Real-time data acquisition: use of scales (sliders) ====

<gallery widths=300px heights=200px>

Datei:09 Skala einfügen.png|The 1D scales shaped like sliders can be easily added as an element and further customised and personalised in the inspector.

Datei:10 Skala beschriften .png| Customise the alignment, values and step intervals according to your needs.

</gallery>

Data collection is always linked to an event (e.g. a piece of music). Create as many parts as you like for different events, which you or the participants can navigate through during realisation.

== Realisation ==
=== Create realisation ===

<gallery widths=300px heights=200px>

Datei:11 Durchführung-Reiter.png|Save the project and click on ‘New realisation’ in the ‘’Realisations‘’ tab.

Datei:12 Durchführung erstellen Dialog.png| Give the realisation a title and shortcode and set the starting time. You can either activate the realisation now or schedule it to start at a later time.

Datei:13 Durchführung Übersicht.png|emoTouch now creates a QR code, a link and a shortcode that participants can use to join the event without registering. The shortcode can be entered on www.emotouch.de.

</gallery>

=== Managing Realisations ===
<gallery widths=300px heights=200px>

Datei:14 Liste Durchführungen.png|Keep an overview of planned, ongoing and completed realisations in the "Realisations" tab. Any number of participants can join a running realisation. They each create a ‘session’. Click on a realisation in the list for an overview of the sessions that have been created.

</gallery>

Sie können zeitgleich mehrere aktive Durchführungen laufen lassen. Achtung: Pausieren ist nicht möglich. Das Stoppen einer Durchführung beendet diese endgültig.

== Auswerten - Werte und Daten exportieren ==
<gallery widths=300px heights=200px>
Datei:15 Zum Export Button.png|Beenden Sie die Durchführung, wenn Sie alle benötigten Daten erhoben haben. Klicken Sie in die '''abgeschlossene''' Durchführung, die Sie auswerten wollen und klicken Sie den "EXPORTIEREN" - Button.
Datei:16 Daten exportieren Dialog.png|Konfigurieren Sie Formatierungsdetails. emoTouch erstellt eine CSV Datei mit den Rohdaten, oder wahlweise resampelten Daten, die mit einer beliebigen Tabellenkalkulations- oder Statistiksoftware weiterverwertet werden kann.
</gallery>

Exportierbar sind:
* Zeitreihendaten
* Finale Zeitreihendaten
* Sitzungs-Metadaten
* Objekt-Metadaten

=== Resampling ===
Für alle Analysen, die Berechnungen auf der Basis von mehreren Teilnehmern beinhalten (z.B. die Berechnung des Mittelwerts einer Schiebereglerposition über alle Teilnehmer zu einem bestimmten Zeitstempel), müssen die erfassten Rohdaten von emoTouch in 'resampelte Daten' ('Resampled Data') umgewandelt werden.

Translations:Erste Schritte zum eigenen Projekt/15/en

2024-10-24T11:20:00Z

=== Managing Realisations ===
<gallery widths=300px heights=200px>

Datei:14 Liste Durchführungen.png|Keep an overview of planned, ongoing and completed realisations in the "Realisations" tab. Any number of participants can join a running realisation. They each create a ‘session’. Click on a realisation in the list for an overview of the sessions that have been created.

</gallery>