Foal Genotype Calculator

I've made a calculator that can tell you all the possible genotypes you can get in a foal based on its parent's genes, and tell you how likely each is. To use it, click the link below, paste in the genotype of the sire and dam, then click 'Calculate Foal'. That's it! I hope you guys like it. :D

Foal Genotype Calculator

If you see any issues or bugs, have a question, or would like to suggest a feature for a future version, please post it here and I'll help you out.

Frequently Asked Questions

What does the genotype mean? What colour/pattern will the foal be?
The program has now been updated to show the colour and pattern corresponding to each genotype.

What other foal calculators exist?
I have also made a foal stat calculator.

Can I use this to predict a breeding between real life horses?
You can try, but I make no guarantees about accuracy, as Equiverse's genetics system may not be identical to what actually exists in real horses (although it's at least similar). Make sure you untick the box labelled "Use Equiverse genetics" so that it'll handle lethal genes correctly, and input the genes in the same form that Equiverse uses, based on your best guess if the horse hasn't been tested for a particular gene.

Just some interesting stats about the calculator...
- This was made using Javascript and HTML.
- It consists of almost 700 lines of code.

Last edited on 2017-05-03 at 07:10:56 by UlyssesBlue (spare)

THANK YOU SO MUCH

You're welcome. ♥

I would LOVE to see phenotypes for base color listed alongside the genotypes!!

Two thumbs up.

You're amazing!

@Ðemure

It would be great if the phenotype could be listed alongside a genotype, but to be honest I'm not certain this can ever happen, for several reasons:

- Firstly, phenotypes will be a massive undertaking in their own right. So big it will dwarf the original calculator. o.O It would require months of research and bug testing to build up a complete list and get it working.

- Second, such a large addition to the program will drastically increase computational time, and I don't want it to be too slow.

- Also, the current form of the program is very versatile, such that in most cases it will still understand things and make accurate predictions if you write a gene a little wrong, or introduce a new one like pearl. This would be incompatible with a phenotype reader, so the program would lose this versatility and give weird phenotype results. It would also remove future proofing, so if EV changed its genetics system or new genes were discovered in real life, the program would require a massive rewrite.

- Finally, I believe there's a few inaccuracies in EV's genetics, which mean phenotypes don't always reflect what would happen in real life. I would be hesitant to introduce this level of inaccuracy into the program. As it stands a genotype can be interpreted in either an EV context or a real life context, and this is left up to an individual.

Hope this explains things. I'm sorry this can't happen. It would be great if it could work, but I don't think it realistically can.

omg you're a life saver!

Darn... I guess it would be difficult to tell it, say, bay only shows up on a black base, and more detailed forms thereof. Oh well.. I still love the calculator! And I've gotten pretty good at reading the genotypes. Thank you!

No, actually telling it bay only shows up with EE or Ee is relatively simple, since it's just two genes. It's just a matter of an 'if' statement with a logical 'or' operator. It's doing that for every single permutation possible where things get complicated, since there's 17 genes, and you'd also have to perform this calculation for every produced genotype. Basically just tons and tons of nested 'if' statements, inside a 'for' or 'while' loop.

Stickied. Yay :D

Just noticed this is now stickied. ♥ Thank you to whatever mod did that.

Yayyyy, you're a sticky!!!!

For the genotype->phenotype computation, it's much easier have the phenotypes listed, with a sort of "yes, no, irrelevant" marker for each gene. Then you don't need nested conditionals to compute.

For example:

Colour - Extension - Agouti
Black - YES - NO
Bay - YES - YES
Chestnut - NO - IRRELEVANT

And then you just build up that profile for the genes:

if(EE or Ee) Extension = YES
else Extension = NO

if(Extension == No) Agouti = IRRELEVANT
elseif(AA or Aa) Agouti = YES
else Agouti = NO

Gets more complicated for some genes (cream because of incomplete dominance) but that's the logic I use for the invented genetics system of the game I'm working on (rainbow ponies).

Thanks, Almárë! I'll look into that. :)