Last updated: 2024-07-10
Checks: 6 1
Knit directory: PODFRIDGE/
This reproducible R Markdown analysis was created with workflowr (version 1.7.1). 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 job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.
The command set.seed(20230302)
was run prior to running
the code in the R Markdown file. Setting a seed ensures that any results
that rely on randomness, e.g. subsampling or permutations, are
reproducible.
Great job! Recording the operating system, R version, and package versions is critical for reproducibility.
Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.
Great job! Using relative paths to the files within your workflowr project makes it easier to run your code on other machines.
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 f80f86e. 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: .DS_Store
Ignored: .Rhistory
Ignored: .Rproj.user/
Ignored: data/.DS_Store
Unstaged changes:
Modified: analysis/STR-simulation.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/STR-simulation.Rmd
) and
HTML (docs/STR-simulation.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 |
---|---|---|---|---|
Rmd | f80f86e | tinalasisi | 2024-07-10 | Updated STR-simulation.Rmd |
html | f80f86e | tinalasisi | 2024-07-10 | Updated STR-simulation.Rmd |
Rmd | 11fb32c | Tina Lasisi | 2024-03-10 | write CSVs with output data |
html | cf281b6 | Tina Lasisi | 2024-03-03 | Build site. |
Rmd | 2596546 | Tina Lasisi | 2024-03-03 | wflow_publish("analysis/*", republish = TRUE, all = TRUE, verbose = TRUE) |
Likelihood ratio for a single locus is:
R=κ0+κ1/RpX+κ2/RuX Where κ is the probability of having 0, 1 or 2 alleles IBD for a given relationship.
The RX terms are quantifying the “surprisingness” of a particular pattern of allele sharing.
The RpX terms attached to the kappa1 are defined in the following table:
Table 7.2 Single-locus LRs for paternity when CM is unavailable. cQRX×(1+2FST)AAAA3FST+(1−FST)pAAAAB2(2FST+(1−FST)pA)ABAA2(2FST+(1−FST)pA)ABAC4(FST+(1−FST)pA)ABAB4(FST+(1−FST)pA)(FST+(1−FST)pB)/(2FST+(1−FST)(pA+pB))
For our purposes we will take out the FST values. So the table will be as follows:
cQRXAAAApAAAAB2pAABAA2pAABAC4pAABAB4pApB/(pA+pB)
If none of the alleles match, then the κ1/RpX=0.
The RuX terms attached to the kappa2 are defined as:
If both alleles match and are homozygous the equation is 6.4 (pg 85). Single locus match probability: CSP=GQ=AA (2FST+(1−FST)pA)(3FST+(1−FST)pA)(1+FST)(1+2FST) Simplified to: pA2
If both alleles match and are heterozygous, the equation is 6.5 (pg 85) Single locus match probability: CSP=GQ=AB 2(FST+(1−FST)pA)(FST+(1−FST)pB)(1+FST)(1+2FST) Simplified to:
2pApB If both alleles do not match then κ2/RuX=0.
Flowchart
Input for LR function
Initialization: Load required R packages and set the working directory.
Parameter Configuration: Input parameters for the number of simulations for unrelated and related pairs are specified, allowing adjustable sample sizes.
Data Preparation: Aggregate CODIS allele frequency data from CSV files representing different populations into a single dataset.
IBD Probability Definitions: Construct a table detailing the probabilities of sharing zero, one, or two alleles identical by descent (IBD) for various relationship types.
Allele Frequency Calculation: Calculate allele frequencies within the population for each simulated pair to determine the likelihood of observing specific allele combinations.
Likelihood Ratio Computation: Calculate likelihood ratios for each pair using allele frequencies and IBD probabilities, focusing on RXp and RXu values.
Simulation of Individual Pairs: Generate alleles for individuals based on population-specific allele frequencies to simulate STR pairs.
Shared Allele Analysis: Evaluate the number of alleles shared between pairs, categorizing them by their genetic relationship.
Aggregate Analysis and Visualization: Summarize the results and generate visual representations, such as box plots and heatmaps, to illustrate the relationship between known and tested relationships across populations.
Result Exportation: Export aggregated results as CSV files for further analysis.
Due to the computational cost of simulating large numbers of STR pairs, the script has been run separately and we visualize the results below.
Rows: 360000 Columns: 6
── Column specification ────────────────────────────────────────────────────────
Delimiter: ","
chr (3): population, known_relationship_type, tested_relationship_type
dbl (3): replicate_id, num_shared_alleles_sum, log_R_sum
ℹ Use `spec()` to retrieve the full column specification for this data.
ℹ Specify the column types or set `show_col_types = FALSE` to quiet this message.
population relationship_type fp_rate prop_exceeding
1 AfAm parent_child 0.1 1.000
2 Asian parent_child 0.1 1.000
3 Cauc parent_child 0.1 1.000
4 Hispanic parent_child 0.1 1.000
5 AfAm full_siblings 0.1 0.794
6 Asian full_siblings 0.1 0.820
`summarise()` has grouped output by 'population'. You can override using the
`.groups` argument.
`summarise()` has grouped output by 'population'. You can override using the
`.groups` argument.
# A tibble: 24 × 7
population known_relationship_type mean_log_R_sum median_log_R_sum
<chr> <chr> <dbl> <dbl>
1 AfAm cousins -0.533 2.42
2 AfAm full_siblings 10.5 11.5
3 AfAm half_siblings 3.85 6.80
4 AfAm parent_child 19.6 19.0
5 AfAm second_cousins -1.23 1.78
6 AfAm unrelated -2.00 0.914
7 Asian cousins -0.538 2.42
8 Asian full_siblings 10.5 11.6
9 Asian half_siblings 3.82 6.78
10 Asian parent_child 19.5 18.9
# ℹ 14 more rows
# ℹ 3 more variables: min_log_R_sum <dbl>, max_log_R_sum <dbl>, count <int>