Last updated: 2023-03-02
Checks: 1 1
Knit directory: POPFORGE/
This reproducible R Markdown analysis was created with workflowr (version 1.7.0). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
The R Markdown file has unstaged changes. To know which version of
the R Markdown file created these results, you’ll want to first commit
it to the Git repo. If you’re still working on the analysis, you can
ignore this warning. When you’re finished, you can run
wflow_publish to commit the R Markdown file and build the
HTML.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.
The results in this page were generated with repository version 51ed5a6. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
Note that you need to be careful to ensure that all relevant files for
the analysis have been committed to Git prior to generating the results
(you can use wflow_publish or
wflow_git_commit). workflowr only checks the R Markdown
file, but you know if there are other scripts or data files that it
depends on. Below is the status of the Git repository when the results
were generated:
Ignored files:
Ignored: .Rproj.user/
Untracked files:
Untracked: data/US_popsize.csv
Unstaged changes:
Modified: analysis/_site.yml
Modified: analysis/index.Rmd
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
These are the previous versions of the repository in which changes were
made to the R Markdown (analysis/index.Rmd) and HTML
(docs/index.html) files. If you’ve configured a remote Git
repository (see ?wflow_git_remote), click on the hyperlinks
in the table below to view the files as they were in that past version.
| File | Version | Author | Date | Message |
|---|---|---|---|---|
| html | 51ed5a6 | Tina Lasisi | 2023-03-02 | Build site. |
| html | 13ed9ae | Tina Lasisi | 2023-03-02 | Publishing POPFORGE |
| Rmd | 144ddae | Tina Lasisi | 2023-03-02 | Start workflowr project. |
The use of genetic data to identify individuals has become increasingly prevalent with the rise of consumer genomics databases and forensic genetic genealogy. Recent studies have shown that long-range familial searches can implicate the majority of US individuals of European descent (see Ehrlich et al 2018 and Coop & Edge 2019). These findings have motivated us to carry out further investigations into the disparities between populations in the likelihood of identifying individuals through genetic relatives.
African-Americans are overrepresented in forensic databases (see Murphy and Tong, 2019 ), but what we know about direct-to-consumer databases suggests that Europeans are highly represented there.
Our study aims to examine the impact of the varying degrees of representation across different types of genetic databases on the potential consequences for different populations, as well as the impact of different types of genetic data such as SNP genotyping and STR markers.
The POPFORGE (Population Differences in Forensic Identification of Genetic Relatives) project aims to address this question by using mathematical estimations of genetic relatedness based on previous methods, as well as simulating pedigrees and genomes for two populations based on input parameters. Additionally, demographic data from the US Census microdata will be used to obtain population size information on European and African Americans.