Giter Club home page Giter Club logo

Comments (3)

JiscaH avatar JiscaH commented on June 2, 2024

Hello Oliver,

The most likely reason I can think of in this case is that this is due to genotyping errors: Based on the presumed genotyping error rate you provide ('Err'), a maximum is calculated for the number of opposing homozygous (OH) loci between parent-offspring pairs and parent-parent-offspring trios. If the OH count for a pair exceeds this value, the likelihood to be parent-offspring is not calculated (as there is no point and would just take time). If you run CalcPairLL() with 'U' specified as focal relationship, it should a likelihood value for PO, as they do not appear to be excluded based on age difference.

To check whether this is indeed the problem, you can run sequoia() and/or GetMaybeRel() with a higher presumed genotyping error rate than you used now. The thresholds sequoia() used are in the $specs element of the output, they are calculated by CalcMaxMismatch().

If this does not solve the problem, please let me know!

Edit: Actually, if genotyping error rate is the problem, the PO column should be '999' (=missing) rather than '777' (=impossible). It's hard to know what the problem is without the arguments that you passed to CalcPairLL(), but I am going to assume this is conditional on the pedigree and you have specified strict monogamy? An individual can only get assigned a single parent when that parent has no other offspring yet (i.e. doesn't have a monogamous mate yet), otherwise only a parent-pair gets assigned. I think this criterium is not behaving as expected in combination with CalcPairLL() (or GetMaybeRel() ), and I think it would give you likelihoods if you specify Complex='simp' (or edit the value in $Specs if you are providing SeqList.

I'd like to resolve this issue; would you be able/allowed to email me your data, or mock data generating the same problem?

Thanks,
Jisca

from sequoia.

OliverPStuart avatar OliverPStuart commented on June 2, 2024

Hi Jisca,

Thanks for your detailed response. Yes, it's not a problem of genotyping error. All of these SNPs have been filtered for Mendelian impossibilities based on the pedigree. I am being very strict with my calling and filtering before getting to this stage.

The command I use is:

sequoia_out_assign <- sequoia(GenoM = sequoia_geno,
        LifeHistData = life_hist,
        Module = "par")

The information I give is very minimal. The life_hist object has columns ID, Sex, BirthYear (BirthYear==2020 for parents, BirthYear==2021 for offspring). I am not specifying monogamous mating in these tests; my aim is to test the use of this software + these sites for deployment with wild-caught individuals where no information except rough age is known (only slightly overlapping generations in the wild and polyandry + polygyny). Later I will be doing more extensive tests by dropping parents from consideration and simulating more complicated scenarios. For now, I am confirming that I can reconstruct the simple monogamous pedigree.

A curious thing: although there are no opposing homozygous SNPs between these offspring and these parents, there is indeed a small set of SNPs which are causing a problem. I start with ~330 SNPs and when I take a random subset of these sites I sometimes get 100 % accuracy (all parents correctly assigned). I took more random subsets and ranked SNPs by assignment accuracy and I find a consistent set of 35 SNPs the removal of which gives perfect assignment accuracy. When I look at the genotypes of these SNPs for the offspring and the parents I see nothing out of the ordinary. Although this is good, it does not answer what is causing the issue.

What is your best email address? I can send the plink files + life history data to recreate the issue.

Oliver

from sequoia.

JiscaH avatar JiscaH commented on June 2, 2024

Well that's odd indeed!

From your detective work it does sound like an issue with those 35 SNPs is the most likely - perhaps genotyping errors that did not result in Mendelian impossibilities, but in Mendelian highly unlikely genetic combinations for a parent-parent-offspring trio. If this is indeed the problem, it should work OK if you set a higher presumed genotyping error rate, e.g. 5e-4 or 1e-3 instead of the default value of 1e-4.

My email address is jisca.huisman @ gmail.com , thanks! Could you please also include the argument you used for GetMaybeRel? As that may or may not be a separate issue.

from sequoia.

Related Issues (17)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.