knitr::opts_chunk$set( collapse = TRUE, comment = "#>", fig.align = "center" ) options(rmarkdown.html_vignette.check_title = FALSE)
The {discord} package was originally developed for use with the National Longitudinal Survey of Youth (NLSY), but its functionality extends far beyond that. When paired with its sister package {BGmisc}, discord can be applied to any dataset containing basic family structure information, allowing researchers to explore genetic and environmental influences without requiring pre-constructed kinship links.
This vignette demonstrates how to:
We use tools from {BGmisc} and a toy dataset to illustrate the workflow.
We begin by loading the required packages and a built-in dataset from {BGmisc}.
library(BGmisc) library(tidyverse) library(discord) data(potter)
We rename the family ID column to avoid naming conflicts and generate a pedigree-encoded data frame.
df_potter <- potter names(df_potter)[names(df_potter) == "famID"] <- "oldfam" df_potter <- ped2fam(df_potter, famID = "famID", personID = "personID" )
We also verify and repair sex coding to ensure compatibility with downstream pedigree operations.
df_potter <- checkSex(df_potter, code_male = 1, code_female = 0, verbose = FALSE, repair = TRUE )
BGmisc::plotPedigree(df_potter, verbose = FALSE)
The pedigree plot provides a visual representation of the kinship structure in the dataset. Each node represents an individual, and the edges indicate familial relationships.
To extract the necessary kinship information, we need to compute two matrices: the additive genetic relatedness matrix and the shared environment matrix. These matrices are derived from the pedigree data and are essential for understanding the genetic and environmental relationships among individuals. Using {BGmisc}, we compute:
The additive genetic relatedness matrix (add).
The shared environment matrix (cn), indicating whether kin were raised together (1) or apart (0).
add <- ped2add(df_potter) cn <- ped2cn(df_potter)
The ped2add()
function computes the additive genetic relatedness matrix, which quantifies the genetic similarity between individuals based on their pedigree information. The ped2cn()
function computes the shared environment matrix, which indicates whether individuals were raised in the same environment (1) or different environments (0).
The resulting matrices are symmetric, with diagonal elements representing self-relatedness (1.0). The off-diagonal elements represent the relatedness between pairs of individuals, with values ranging from 0 (no relatedness) to 0.5 (full siblings) to 1 (themselves).
We convert the component matrices into a long-form data frame of kin pairs using com2links()
. Self-pairs and duplicate entries are removed.
df_links <- com2links( writetodisk = FALSE, ad_ped_matrix = add, cn_ped_matrix = cn, drop_upper_triangular = TRUE ) %>% filter(ID1 != ID2) df_links %>% slice(1:10) %>% knitr::kable()
We then extract two subsets:
Full siblings: additive relatedness = 0.5 and shared environment = 1
Cousins: additive relatedness = 0.125 and shared environment = 0
df_sim <- df_links %>% filter(addRel == .5) %>% # only full siblings %>% filter(cnuRel == 1) # only kin raised in the same home df_cousin <- df_links %>% filter(addRel == .125) %>% # only cousins %>% filter(cnuRel == 0) # only kin raised in separate homes
To simulate phenotypic data, we need to create a data frame that includes the kinship information and the outcome variables. We will simulate two outcome variables (y1 and y2) for each cousin pair in the dataset. The kinsim()
function from {discord} is used to generate the simulated data based on the specified variance structure.
set.seed(1234) syn_df <- discord::kinsim( mu_all = c(1, 1), cov_a = .4, cov_e = .4, c_all = 0, r_vector = df_cousin$addRel ) %>% select(-c( A1_1, A1_2, A2_1, A2_2, C1_1, C1_2, C2_1, C2_2, E1_1, E1_2, E2_1, E2_2, r ))
The simulated data reflect a known variance structure: additive genetic covariance = .4, genetic correlation = 0.125, no shared environment, and residual (unique environment) variance = 0.4. Latent component scores are excluded from the final dataset, but they can be useful for debugging and understanding the underlying structure of the data.
We bind the simulated outcome data to the cousin link data to prepare it for modeling.
data_demo <- cbind(df_cousin, syn_df) summary(data_demo)
The data_demo
data frame now contains the kinship information along with the simulated outcome variables y1 and y2. Each row represents a pair of cousins, and the columns include the IDs of the individuals, their relatedness, and the simulated phenotypic data.
We then use discord_regression()
to fit a discordant-kinship model, predicting y1 from y2. Based on the structure of the data, we expect that there will be a significant association between the two outcome variables, as there is a known overlapping non-shared environment covariance.
The model is fit using the discord_regression()
function, which takes the following arguments:
model_output <- discord_regression( data = data_demo, outcome = "y1", predictors = "y2", id = "id", sex = NULL, race = NULL, pair_identifiers = c("_1", "_2") ) summary(model_output)
The output of the model includes estimates of the regression coefficients, standard errors, and p-values for the association between the two outcome variables.
This vignette demonstrates how {BGmisc} and discord enable researchers to perform discordant-kinship analyses starting from simple family data. There’s no need for pre-constructed kinship links or specialized datasets like the NLSY—just basic family identifiers are sufficient to generate kinship structures and apply powerful behavior genetic models.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.