/discent

Gradient descent for estimating inbreeding spatial coefficients from pairwise-IBD estimates

Primary LanguageROtherNOASSERTION

DISCent

main_build main_build Code Coverage

Overview

This is a simple package with a single function that runs a simple isolation by distance and identity by descent model for producing deme inbreeding spatial coefficients (DISCs). By theory, genetic relatnedness is strictly limited to measure of identity by descent. For a full mathematical overview of the simple model, please see the supplements from Brazeau et al. 2022.

Briefly, in the early 1970s, Malécot described a relationship between genetic relatedness and physical distance under the premise that pairs that are far apart are less likely to mate: isolation by distance. Capitalizing on this framework by using measures of identity by descent (IBD), we produce a deme inbreeding spatial coefficient (DISC) for point process data in continuous space. Essentially, this measure estimates the amount of "inbreeding" or within deme relatedness under the assumption that relatedness between two locations in space can be measured from the average pairwise IBD between those two locations conditional on the physical distance that seperates them. Further, we assume that geographic distance is scaled by a migration rate, which is a global parameter among all spatial locations (i.e. the migration rate is assumed to be constant through space). As a result, the model produces a DISC for each spatial location considered (user defined) and an overall migration rate parameter (m). Parameter optimization is achieved with a "vanilla" gradient descent algorithm. Given that "vanilla" gradient descent is used, we recommend running numerous models from a wide of array of start parameters to ensure that your final results are the global maximum and not a local maximum (i.e. a false peak).

Running the Model

For instructions on running the model, please see our vignettes: Vignettes

IMPORTANT NOTES

⚠️ This model has planned development and is not guaranteed to be backwards compatible. Version updates that are not backwards compatible will be noted in the NEWS.md file.