Accused murderer wins right to check source code of DNA testing kit
1–10 of 520 posts
Re: Accused murderer wins right to check source code of DNA testing kit
#2Re: Accused murderer wins right to check source code of DNA testing kit
#3So it’s definitely riddled with bugs. And I can’t imagine that much matlab code following rigorous software engineering practices.
Re: Accused murderer wins right to check source code of DNA testing kit
#4Re: Accused murderer wins right to check source code of DNA testing kit
#5https://dna-explained.com/2017/01/19/concepts-segment-size-l...
Re: Accused murderer wins right to check source code of DNA testing kit
#6Re: Accused murderer wins right to check source code of DNA testing kit
#7Re: Accused murderer wins right to check source code of DNA testing kit
#8> Mark Perlin, is said to have argued against source code analysis by claiming that the program, consisting of 170,000 lines of MATLAB code, is so dense it would take eight and a half years to review at a rate of ten lines an hour. So it’s definitely riddled with bugs. And I can’t imagine that much matlab code following rigorous software engineering practices.
Re: Accused murderer wins right to check source code of DNA testing kit
#9> Mark Perlin, is said to have argued against source code analysis by claiming that the program, consisting of 170,000 lines of MATLAB code, is so dense it would take eight and a half years to review at a rate of ten lines an hour. So it’s definitely riddled with bugs. And I can’t imagine that much matlab code following rigorous software engineering practices.
Re: Accused murderer wins right to check source code of DNA testing kit
#10"Those arguing on behalf of the defense cited past problems with other genetic testing software such as STRmix and FST (Forensic Statistical Tool). Defense expert witnesses Mats Heimdahl and Jeanna Matthews, for example, said that STRmix had 13 coding errors that affected 60 criminal cases, errors not revealed until a source code review." "They also pointed out, as the appeals court ruling describes, how an FST source code review "uncovered that a 'secret function . . . was present in the software, tending to overestimate the likelihood of guilt.'"
An analogous situation with an alcohol and drug testing lab caused a scandal in Canada and called into question 16,000 child protective services cases: https://en.wikipedia.org/wiki/Motherisk , and then at the same hospital(!), a forensic pathologist was giving fake prosecution evidence, https://en.wikipedia.org/wiki/Charles_Smith_(pathologist)
Maybe there's just something about Toronto and compromised processes, but defense challenges to the integrity of automated systems looks like a growth field.