1 of 100

Analysis of the Genealogy Process in Forensic Genetic Genealogy

Lawrence M. Wein

Mine Su Erturk

Graduate School of Business, Stanford University

Colleen Fitzpatrick

Identifinders

Margaret Press

DNA Doe Project

2 of 100

CRIME RESEARCH AGENDA

Reduce Type I errors with respect to incarceration

- Reduce overcrowding in jails, PLOS ONE, NY Times 2015

- Effect of judge rotation on criminal sentencing

3 of 100

CRIME RESEARCH AGENDA

Reduce Type I errors with respect to incarceration

- Reduce overcrowding in jails, PLOS ONE, NY Times 2015

- Effect of judge rotation on criminal sentencing

Reduce Type II errors with respect to incarceration

- Ballistic imaging: Journal of Forensic Sciences 2017

AFTE Journal 2018

4 of 100

IMPACT OF BALLISTIC IMAGING PAPER

s

Starting in July 2018, the U.S. Bureau of Alcohol, Tobacco,

Firearms and Explosives (ATF) is requiring all NIBIN sites to:

- Enter 100% of cartridges into NIBIN

- Prioritize entry based on evidence, crime code and caliber

- Use LCFS

5 of 100

CRIME RESEARCH AGENDA

Reduce Type I errors with respect to incarceration

- Reduce overcrowding in jails, PLOS ONE, NY Times 2015

- Effect of judge rotation on criminal sentencing

Reduce Type II errors with respect to incarceration

- Ballistic imaging: Journal of Forensic Sciences 2017

AFTE Journal 2018

- Sexual assault kits:

Testing the backlog: Journal of Forensic Sciences 2018

cnn.com 2018

How to test the backlog: PNAS 2020

6 of 100

CRIME RESEARCH AGENDA

Reduce Type I errors with respect to incarceration

- Reduce overcrowding in jails, PLOS ONE, NY Times 2015

- Effect of judge rotation on criminal sentencing

Reduce Type II errors with respect to incarceration

- Ballistic imaging: Journal of Forensic Sciences 2017

AFTE Journal 2018

- Sexual assault kits:

Testing the backlog: Journal of Forensic Sciences 2018

cnn.com 2018

How to test the backlog: PNAS 2020

- Forensic Genetic Genealogy

7 of 100

OUTLINE

Introduction: research questions and data

Main results

Parameter estimation

Modeling the two-stage genealogy process

Proposed strategy

Limitations

Conclusions

8 of 100

Golden State Killer Case 2018

9 of 100

STEPS IN THE FGG PROCESS

1. Obtain DNA sample from crime scene or unidentified

remains and perform genotyping (SNPs)

10 of 100

STEPS IN THE FGG PROCESS

1. Obtain DNA sample from crime scene or unidentified

remains and perform genotyping (SNPs)

2. Upload SNP data to third-party service to obtain relatives

of target

11 of 100

STEPS IN THE FGG PROCESS

1. Obtain DNA sample from crime scene or unidentified

remains and perform genotyping (SNPs)

2. Upload SNP data to third-party service to obtain relatives

of target

3. Perform genealogy research to identify target

12 of 100

STEPS IN THE FGG PROCESS

1. Obtain DNA sample from crime scene or unidentified

remains and perform genotyping (SNPs)

2. Upload SNP data to third-party service to obtain relatives

of target

3. Perform genealogy research to identify target

4. Obtain confirmatory DNA sample from identified target or

family member

13 of 100

FGG ECOSYSTEM IS EVOLVING

GEDmatch switched to opt in (1.4M 🡪 260k in database)

14 of 100

FGG ECOSYSTEM IS EVOLVING

GEDmatch switched to opt in (1.4M 🡪 260k in database)

Field pioneered by four women (Colleen Fitzpatrick,

CeCe Moore, Margaret Press, Barbara Rae-Venter)

15 of 100

FGG ECOSYSTEM IS EVOLVING

GEDmatch switched to opt in (1.4M 🡪 260k in database)

Field pioneered by four women (Colleen Fitzpatrick,

CeCe Moore, Margaret Press, Barbara Rae-Venter)

Some small FGG companies bought by large companies

(Bode, Parabon)

16 of 100

FGG ECOSYSTEM IS EVOLVING

GEDmatch switched to opt in (1.4M 🡪 260k in database)

Field pioneered by four women (Colleen Fitzpatrick,

CeCe Moore, Margaret Press, Barbara Rae-Venter)

Some small FGG companies bought by large companies

(Bode, Parabon)

Most police departments outsource FGG

17 of 100

FGG ECOSYSTEM IS EVOLVING

GEDmatch switched to opt in (1.4M 🡪 260k in database)

Field pioneered by four women (Colleen Fitzpatrick,

CeCe Moore, Margaret Press, Barbara Rae-Venter)

Some small FGG companies bought by large companies

(Bode, Parabon)

Most police departments outsource FGG

Several hundred cold cases solved in 2018-21 (50% success)

4. Obtain confirmatory DNA sample from identified suspect

18 of 100

FGG ECOSYSTEM IS EVOLVING

GEDmatch switched to opt in (1.4M 🡪 260k in database)

Field pioneered by four women (Colleen Fitzpatrick,

CeCe Moore, Margaret Press, Barbara Rae-Venter)

Some small FGG companies bought by large companies

(Bode, Parabon)

Most police departments outsource FGG

Several hundred cold cases solved in 2018-21 (50% success)

DNA Doe Project is nonprofit, uses crowdsourced

volunteers (retired women), and identifies unidentified

human remains (rather than solving criminal cases)

4. Obtain confirmatory DNA sample from identified suspect

19 of 100

RESEARCH QUESTIONS

First mathematical analysis of the backend of the FGG process

(i.e., GEDmatch/FTDNA output 🡪 identify target)

20 of 100

RESEARCH QUESTIONS

First mathematical analysis of the backend of the FGG process

(i.e., GEDmatch/FTDNA output 🡪 identify target)

Performance analysis:

Given the GEDmatch/FTDNA output, compute:

Probability of identifying target

Expected workload (= size of final family tree)

21 of 100

RESEARCH QUESTIONS

First mathematical analysis of the backend of the FGG process

(i.e., GEDmatch/FTDNA output 🡪 identify target)

Performance analysis:

Given the GEDmatch/FTDNA output, compute:

Probability of identifying target

Expected workload (= size of final family tree)

Optimization:

How many and which matches to investigate?

When/if to descend from (possible) MRCAs

(MRCA = Most Recent Common Ancestor)

22 of 100

17 CASES FROM DNA DOE PROJECT

23 of 100

GEDmatch OUTPUT

23

Jane Doe

24 of 100

24

Jane Doe

Total cM

25 of 100

PROBABILISTIC MAPPING FROM TOTAL cM TO RELATIONSHIPS

25

https://thednageek.com/science-the-heck-out-of-your-dna-part-3/

Ball et al. (2016), Ancestry DNA Matching White Paper.

26 of 100

26

Jane Doe

Bob

Total cM

https://thednageek.com/science-the-heck-out-of-your-dna-part-3/

Ball et al. (2016), Ancestry DNA Matching White Paper.

182.2

27 of 100

AUTO CLUSTER TOOL IN GEDmatch

28 of 100

OUTLINE

Introduction: research questions and data

Main results

Parameter estimation

Modeling the two-stage genealogy process

Proposed strategy

Limitations

Conclusions

29 of 100

BENCHMARK STRATEGY

Search for common ancestors between two matches

30 of 100

BENCHMARK STRATEGY

Search for common ancestors between two matches

Descend from these ancestors to look for an intersection

(marriage) between both sides of target’s family tree

31 of 100

BENCHMARK STRATEGY

Search for common ancestors between two matches

Descend from these ancestors to look for an intersection

(marriage) between both sides of target’s family tree

Investigate n matches prioritized by highest total cM

32 of 100

BENCHMARK STRATEGY

Search for common ancestors between two matches

Descend from these ancestors to look for an intersection

(marriage) between both sides of target’s family tree

Investigate n matches prioritized by highest total cM

Vary n to generate Pr(identify target) vs. workload curve

33 of 100

PROPOSED vs. BENCHMARK STRATEGY

34 of 100

PROPOSED vs. BENCHMARK STRATEGY

  • It solves cases much more quickly: at workload = 7500,
  • it solves 94% of cases vs. 4% for Benchmark

35 of 100

OUTLINE

Introduction: research questions and data

Main results

Parameter estimation

Modeling the two-stage genealogy process

Proposed strategy

Limitations

Conclusions

36 of 100

PARAMETERS

  • Pr(can identify a match) = 0.59

37 of 100

PARAMETERS

  • Pr(can identify a match) = 0.59

  • Pr(can identify someone’s spouse) = 1

Pr(can identify someone’s child) = 0.98 (also considered 0.90)

Pr(can identify someone’s parents) = 0.60 (by simulation)

38 of 100

PARAMETERS

  • Pr(can identify a match) = 0.59

  • Pr(can identify someone’s spouse) = 1

Pr(can identify someone’s child) = 0.98 (also considered 0.90)

Pr(can identify someone’s parents) = 0.60 (by simulation)

Number of children per couple

39 of 100

NUMBER OF CHILDREN PER COUPLE

40 of 100

OUTLINE

Introduction: research questions and data

Main results

Parameter estimation

Modeling the two-stage genealogy process

Proposed strategy

Limitations

Conclusions

41 of 100

ASCENDING STAGE

  • Given: list of GEDmatch/FTDNA matches to investigate

  • Ascending: build family tree up (backwards in time) from matches

  • State of the system at the end of the ascending stage:
  • For each generation g and cluster c = 1,…,2g-1
  • Lg,c = number of possible MRCAs identified
  • Pg,c = Pr(one of the Lg,c MRCAs is the correct MRCA)

42 of 100

ASCENDING STAGE

  • Given: list of GEDmatch/FTDNA matches to investigate

  • Ascending: build family tree up (backwards in time) from matches

  • Goal: Find Most Recent Common Ancestors (MRCAs) between target and each match

  • State of the system at the end of the ascending stage:
  • For each generation g and cluster c = 1,…,2g-1
  • Lg,c = number of possible MRCAs identified
  • Pg,c = Pr(one of the Lg,c MRCAs is the correct MRCA)

43 of 100

Target

2nd cousin

MOST RECENT COMMON ANCESTORS

44 of 100

Target

2nd cousin

MOST RECENT COMMON ANCESTORS

Cluster = ancestral couple of target�7 clusters in this example

45 of 100

ASCENDING STAGE

  • Given: list of GEDmatch/FTDNA matches to investigate

  • Ascending: build family tree up (backwards in time) from matches

  • Goal: Find Most Recent Common Ancestors (MRCAs) between target and each match

  • State of system during ascending stage:
  • For each generation g and cluster c = 1,…,2g-1
  • Lg,c = number of possible MRCAs identified
  • Pg,c = Pr(one of the Lg,c MRCAs is the correct MRCA)

  • State of the system at the end of the ascending stage:
  • For each generation g and cluster c = 1,…,2g-1
  • Lg,c = number of possible MRCAs identified
  • Pg,c = Pr(one of the Lg,c MRCAs is the correct MRCA)

46 of 100

MOST RECENT COMMON ANCESTORS

Target

2nd cousin

List size L = 0, 1, 2, 3 or 4�

47 of 100

MOST RECENT COMMON ANCESTORS

Target

2nd cousin

List size L = 0, 1, 2, 3 or 4�P=0 if L=0, and P=1 if L=4�

48 of 100

MOST RECENT COMMON ANCESTORS

Target

2nd cousin

List size L = 0, 1, 2, 3 or 4�P=0 if L=0, and P=1 if L=4�Other P’s ≠ 1/4, 1/2, 3/4

49 of 100

MOST RECENT COMMON ANCESTORS

Target

2nd cousin

1st cousin

50 of 100

MOST RECENT COMMON ANCESTORS

Target

2nd cousin

1st cousin

Now state changes from (L=4,P=1) to (L=1,P=1)

51 of 100

DESCENDING STAGE

Given: State of system during ascending stage:

  • For each generation g and cluster c = 1,…,2g-1
  • Lg,c = number of possible MRCAs identified
  • Pg,c = Pr(one of the Lg,c MRCAs is the correct MRCA)

  • Descending: build family tree down (forwards in time) from possible MRCAs between target and match

Goal: Find intersection of (i.e., marriage between) maternal

and paternal family trees

52 of 100

FIND INTERSECTION OF FAMILY TREES

Target

1st cousin

2nd cousin

53 of 100

FIND INTERSECTION OF FAMILY TREES

Target

1st cousin

2nd cousin

54 of 100

DESCENDING STAGE

Given: State of system at end of ascending stage:

  • For each generation g and cluster c = 1,…,2g-1
  • Lg,c = number of possible MRCAs identified
  • Pg,c = Pr(one of the Lg,c MRCAs is the correct MRCA)

  • Descending: build family tree down (forwards in time) from possible MRCAs between target and match

Goal: Find intersection of (i.e., marriage between) maternal

and paternal family trees

Compute: 1) probability of finding intersection of family trees

  • 2) expected workload

55 of 100

OUTLINE

Introduction: research questions and data

Main results

Parameter estimation

Modeling the two-stage genealogy process

Proposed strategy

Limitations

Conclusions

56 of 100

PROPOSED vs. BENCHMARK STRATEGY

  • It solves cases much more quickly: at workload = 7500,
  • it solves 94% of cases vs. 4% for Benchmark

57 of 100

STOCHASTIC DYNAMIC PROGRAMMING

Observe state, take action, observe probabilistic transition to

new state, take new action,…to maximize objective

58 of 100

STOCHASTIC DYNAMIC PROGRAMMING

Observe state, take action, observe probabilistic transition to

new state, take new action,…to maximize objective

State: 1) list of uninvestigated matches with cM and cluster

2) for each cluster and generation, Pr(list contains correct

MRCA of target) and size of list of MRCAs

3) list of cluster-generation pairs for which a descending

search has been performed

59 of 100

STOCHASTIC DYNAMIC PROGRAMMING

Observe state, take action, observe probabilistic transition to

new state, take new action,…to maximize objective

State: 1) list of uninvestigated matches with cM and cluster

2) for each cluster and generation, Pr(list contains correct

MRCA of target) and size of list of MRCAs

3) list of cluster-generation pairs for which a descending

search has been performed

Actions: 1) start an ascending search of a new match with cM

and cluster

2) start a descending search from cluster-generation

3) end the search

60 of 100

STOCHASTIC DYNAMIC PROGRAMMING

Observe state, take action, observe probabilistic transition to

new state, take new action,…to maximize objective

State: 1) list of uninvestigated matches with cM and cluster

2) for each cluster and generation, Pr(list contains correct

MRCA of target) and size of list of MRCAs

3) list of cluster-generation pairs for which a descending

search has been performed

Actions: 1) start an ascending search of a new match with cM

and cluster

2) start a descending search from cluster-generation

3) end the search

Objective: maximize Pr(target identified) – (cost x E[workload])

61 of 100

PROPOSED STRATEGY

SDP problem was too hard to solve (huge state space)

62 of 100

PROPOSED STRATEGY

SDP problem was too hard to solve (huge state space)

Derive state transition probabilities for SDP

63 of 100

PROPOSED STRATEGY

SDP problem was too hard to solve (huge state space)

Derive state transition probabilities for SDP

Derive five structural results

64 of 100

PROPOSED STRATEGY

SDP problem was too hard to solve (huge state space)

Derive state transition probabilities for SDP

Derive five structural results

Construct threshold strategy that is consistent with structural results

65 of 100

PROPOSED STRATEGY

SDP problem was too hard to solve (huge state space)

Derive state transition probabilities for SDP

Derive five structural results

Construct threshold strategy that is consistent with structural results

Based on cost-effectiveness:

- compute ΔP (increase in probability of identifying target) and

ΔW (increase in mean workload) for each action

- cost-effectiveness of action = ΔP/ ΔW

66 of 100

PROPOSED STRATEGY

Use a myopic approach with parameter c

1) Given current state, compute ΔP (increase in probability of identifying target) and ΔWd(increase in E[workload]) for each undescended cluster-generation. If max ΔP/ ΔWd >c, then descend.

67 of 100

PROPOSED STRATEGY

Use a myopic approach with parameter c

1) Given current state, compute ΔP (increase in probability of identifying target) and ΔWd(increase in E[workload]) for each undescended cluster-generation. If max ΔP/ ΔWd >c, then descend.

2) Otherwise, for each cluster-generation, assume that we ascend n* times (= min n s.t. max ΔP/ ΔWd >c) and then descend.

68 of 100

PROPOSED STRATEGY

Use a myopic approach with parameter c

1) Given current state, compute ΔP (increase in probability of identifying target) and ΔWd(increase in E[workload]) for each undescended cluster-generation. If max ΔP/ ΔWd >c, then descend.

2) Otherwise, for each cluster-generation, assume that we ascend n* times (= min n s.t. max ΔP/ ΔWd >c) and then descend. If max ΔP(n*)/ [ΔWa(n*)+ ΔWd(n*)]>c, then ascend from max cM match in cluster-generation.

69 of 100

PROPOSED STRATEGY

Use a myopic approach with parameter c

1) Given current state, compute ΔP (increase in probability of identifying target) and ΔWd(increase in E[workload]) for each undescended cluster-generation. If max ΔP/ ΔWd >c, then descend.

2) Otherwise, for each cluster-generation, assume that we ascend n* times (= min n s.t. max ΔP/ ΔWd >c) and then descend. If max ΔP(n*)/ [ΔWa(n*)+ ΔWd(n*)]>c, then ascend from max cM match in cluster-generation.

3) Otherwise, stop.

70 of 100

PROPOSED VS. BENCHMARK STRATEGY

The Proposed strategy:

1) Ascends to exactly the generation of the correct MRCA

between the match and the target

71 of 100

PROPOSED VS. BENCHMARK STRATEGY

M1, M2, T = Match 1, Match 2, Target

g(x,y) = generation of MRCA between x and y

72 of 100

PROPOSED VS. BENCHMARK STRATEGY

M1, M2, T = Match 1, Match 2, Target

g(x,y) = generation of MRCA between x and y

Case 1: g(M1,M2) = min{g(M1,T), g(M2,T)}

equivalent outcomes

73 of 100

PROPOSED VS. BENCHMARK STRATEGY

M1, M2, T = Match 1, Match 2, Target

g(x,y) = generation of MRCA between x and y

Case 1: g(M1,M2) = min{g(M1,T), g(M2,T)}

equivalent outcomes

Case 2: g(M1,M2) < min{g(M1,T), g(M2,T)}

MRCA of 2 Matches cannot be ancestor of Target!

74 of 100

PROPOSED VS. BENCHMARK STRATEGY

M1, M2, T = Match 1, Match 2, Target

g(x,y) = generation of MRCA between x and y

Case 1: g(M1,M2) = min{g(M1,T), g(M2,T)}

equivalent outcomes

Case 2: g(M1,M2) < min{g(M1,T), g(M2,T)}

MRCA of 2 Matches cannot be ancestor of Target!

Case 3: g(M1,M2) > min{g(M1,T), g(M2,T)}

Overshoot: inefficient descents from g(M1,M2)

75 of 100

PROPOSED VS. BENCHMARK STRATEGY

The Proposed strategy:

1) Ascends to exactly the generation of the correct MRCA

between the match and the target

2) Uses the Autocluster tool to prioritize among ascending

actions based on cost-effectiveness

3) Aggressively descends from ancestral couples based on their

cost-effectiveness

76 of 100

BEHAVIOR OF PROPOSED STRATEGY

It aggressively descends from clusters: the average probability

that the list of potential MRCAs contains the correct MRCA is 0.38

77 of 100

BEHAVIOR OF PROPOSED STRATEGY

It aggressively descends from clusters: the average probability

that the list of potential MRCAs contains the correct MRCA is 0.38

Mean list size at time of descent = 5.5 (maximum = 76)

78 of 100

BEHAVIOR OF PROPOSED STRATEGY

It aggressively descends from clusters: the average probability

that the list of potential MRCAs contains the correct MRCA is 0.38

Mean list size at time of descent = 5.5 (maximum = 76)

12.6 descents per case

79 of 100

BEHAVIOR OF PROPOSED STRATEGY

It aggressively descends from clusters: the average probability

that the list of potential MRCAs contains the correct MRCA is 0.38

Mean list size at time of descent = 5.5 (maximum = 76)

12.6 descents per case

1.9 descents per cluster

80 of 100

BEHAVIOR OF PROPOSED STRATEGY

It aggressively descends from clusters: the average probability

that the list of potential MRCAs contains the correct MRCA is 0.36

Mean list size at time of descent = 5.5 (maximum = 76)

12.6 descents per case

1.9 descents per cluster

Great majority of work is in descents

81 of 100

BEHAVIOR OF PROPOSED STRATEGY

It aggressively descends from clusters: the average probability

that the list of potential MRCAs contains the correct MRCA is 0.36

Mean list size at time of descent = 5.5 (maximum = 76)

12.6 descents per case

1.9 descents per cluster

Great majority of work is in descents

Sequence of actions depends on detailed network structure in

complicated way

82 of 100

PROPOSED STRATEGY FOR CASE #1

  • Closest matches in Case #1 are at distance 6
  • = ascending from distance (left vertical axis)
  • = descending from cluster-generation with probability of true MRCA (right vertical axis)

Probability for

Distance for △

Action

83 of 100

OUTLINE

Introduction: research questions and data

Main results

Parameter estimation

Modeling the two-stage genealogy process

Proposed strategy

Limitations

Conclusions

84 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

85 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

No endogamy

86 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

No endogamy

No half-relationships

87 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

No endogamy

No half-relationships

No geographical information

88 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

No endogamy

No half-relationships

No geographical information

No ethnicity information

89 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

No endogamy

No half-relationships

No geographical information

No ethnicity information

AutoCluster information is perfect

90 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

No endogamy

No half-relationships

No geographical information

No ethnicity information

AutoCluster information is perfect

No Y-STR data to infer surname (Gymrek, Science 2013)

91 of 100

LIMITATIONS

Cases: small sample size and not chosen randomly

No endogamy

No half-relationships

No geographical information

No ethnicity information

AutoCluster information is perfect

No Y-STR data to infer surname (Gymrek, Science 2013)

Search probabilities do not depend on generation

92 of 100

OUTLINE

Introduction: research questions and data

Main results

Parameter estimation

Modeling the two-stage genealogy process

Proposed strategy

Limitations

Conclusions

93 of 100

CONCLUSIONS

Pr(identify target) and E[workload] are useful only in relative terms

- But police departments and FGG companies need to

assess solvability and workload upfront

94 of 100

CONCLUSIONS

Pr(identify target) and E[workload] are useful only in relative terms

- But police departments and FGG companies need to

assess solvability and workload upfront

Hard cases appear to be solvable but require high workload

- Tradeoff curves allow for identification of sweet spot

95 of 100

CONCLUSIONS

Pr(identify target) and E[workload] are useful only in relative terms

- But police departments and FGG companies need to

assess solvability and workload upfront

Hard cases appear to be solvable but require high workload

- Tradeoff curves allow for identification of sweet spot

Proposed Strategy solves cases faster by:

- looking for MRCAs between the target and each match

- aggressively descending from possible MRCAs

96 of 100

CONCLUSIONS

Pr(identify target) and E[workload] are useful only in relative terms

- But police departments and FGG companies need to

assess solvability and workload upfront

Hard cases appear to be solvable but require high workload

- Tradeoff curves allow for identification of sweet spot

Proposed Strategy solves cases faster by:

- looking for MRCAs between the target and each match

- aggressively descending from possible MRCAs

Proposed Strategy is meant to aid, not to replace, genealogists’

decisions

  • Slope of curve = marginal cost-effectiveness of investigating
  • an additional match at distance d
  • Marginal analysis (Fox 1966) gives simple solution,
  • but there are interdependencies

97 of 100

NEXT STEPS

Talks at ISHI (Sept 21), SWGDAM (Oct 21) and AAFS (Feb 22)

98 of 100

NEXT STEPS

Talks at ISHI (Sept 21), SWGDAM (Oct 21) and AAFS (Feb 22)

New project: Privacy (targeted testing) vs. Performance tradeoff

99 of 100

NEXT STEPS

Talks at ISHI (Sept 21), SWGDAM (Oct 21) and AAFS (Feb 22)

New project: Privacy (targeted testing) vs. Performance tradeoff

We are testing performance analysis tool (compute Pr(solve case)

and W50 given GEDmatch output) with 908 cases from GEDmatch

100 of 100

NEXT STEPS

Talks at ISHI (Sept 21), SWGDAM (Oct 21) and AAFS (Feb 22)

New project: Privacy (targeted testing) vs. Performance tradeoff

We are testing performance analysis tool (compute Pr(solve case)

and W50 given GEDmatch output) with 908 cases from GEDmatch

We are testing optimization tool on an open cold case