-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow parentage information #17
Comments
As stated in #4 (comment):
|
@ThatLionLady and I agreed that the format for this input should be
If using demographic information (#4), the Sire should be Male and Dam should be Female -- if either is Unknown (not both) then I need to make a decision on whether I infer the Sex or keep it as Unknown. Better yet, I could print Info messages when making inferences and denote any node with inference of any kind with a |
Attention: Make parentage supersede the relatedness input. |
Attention: If both parentage and demographics input is used, fail if they do not agree with one another. |
Fails if the two demographics and parentage disagree (see 175e270). Parentage superseding relatedness happens strictly via the path finding of the graph. Still remaining is accounting for the magic values of |
Separate, but related to #4, is allowing one to input any suspected parentage calls and have them validated via relatedness and, if relatedness agrees, have the pedigree show parent above offspring.
In addition, it would be best if in the pedigree any suspected parentage that was confirmed via relatedness was formatted slightly differently from the inferred parentage. I would expect using a tool such as this one would be more interested in the points of where suspected did not match observed, as well as where the inference occurred -- therefore those matching suspected relationships could be formatted to be mildly translucent or be formatted smaller than inferences.
The text was updated successfully, but these errors were encountered: