Hadoop Online Training by Edureka

CouplesCope: Dyadic sequences of 64 heterosexual couples

Description Usage Format Details Source References

Description

Will be used to exemplify a typical data structure and to illustrate the several function of this package.

Usage

1

Format

A data frame with 64 rows and 98 variables:

Details

In the original sample study, which was promoted as a study on close relationship and stress, 198 heterosexual couples living in Switzerland participated.

The couples had to have been in the current romantic relationship for at least a year and to use German language as their main communication language. During the study, either the woman, the man, or both partners were stressed using the Trier Social Stress Test (TSST; Kirschbaum, Pirke, Hellhammer, 1993). For exemplification purposes, only those 64 couples are included where only the female partner was stressed. Directly after the stress induction, both partners joint again and the couple was left alone for eight minutes. During this period (a 'fake' waiting condition) the two partners were filmed for 8 minutes divided into 48 intervals of ten seconds length. It was coded if the female partners showed stress communication (SC) within an interval (sequence 1; Colums 50:97) and if the male partner showd dyadic coping reactions (DC; sequence 2; columns 2:49). For rurther insides about dyadic coping and/or stress communication, see Bodenmann (2015).

Coding:

  • code: ID variable

  • IKCB01-IKCB48: Was stress communication (SC) shown in the time intervalls 1-48?

  • DCCB01-DCCB48: Was dyadic coping (DC) shown in the time intervalls 1-48?

  • EDCm: Men's self-assessed dyadic coping ability

Source

data: research grants 100013-115948/1 and 100014-115948 from the Swiss National Science Foundation.

References

  • Kirschbaum, C., Pirke, K. M., & Hellhammer, D. H. (1993) <DOI: 10.1159/000119004>

  • Bodenmann, G. (2015) <DOI: 10.1037/11031-002>



Search within the DySeq package
Search all R packages, documentation and source code

Questions? Problems? Suggestions? or email at ian@mutexlabs.com.

Please suggest features or report bugs with the GitHub issue tracker.

All documentation is copyright its authors; we didn't write any of that.