Color Coding Relatives and Spouses Without Reference To RM's Relationship Codes
I know I could use your examples and just assign the 8 colors to the 8 great-grandparents, then recursively color the same color to their ancestors, then for each of the 8 colors recursively color lighter colors for the descendants, but that wouldn't give priority to the color of the closer cousin. The descendants would just be colored in the order of the SQL coding.
Quote from thejerrybryan on 2025-01-07, 2:44 pmI have not yet played with RM's new DNA feature, so I don't know if using the DNA feature would help or not...I have not yet fully mastered recursive queries in SQLite,
DNA table would be of limited help I think for the average users. Yes I believe recursive queries would better the address issues of how any two people are related as well as reporting on cousin who married in etc. Though I have not yet understood them well enough to play with them for such things,
Quote from Chad Kurszewski on 2025-01-07, 2:54 pmI know I could use your examples and just assign the 8 colors to the 8 great-grandparents, then recursively color the same color to their ancestors, then for each of the 8 colors recursively color lighter colors for the descendants, but that wouldn't give priority to the color of the closer cousin. The descendants would just be colored in the order of the SQL coding.
well yes that is one options -- however, I am related to my wife's sister inlaw (she is not) and also related to her uncle (Spouse of her Blood aunt). So children end up having duplicate relationships to them and their cousins thereof. That example aside...
I assume you essentially want to color code from a Common Ancestor and their descendants This can be done within RM using advanced Groups in RM10 wit the cavaet of anyone belonging to more than one ancestor will be written over with the last "Write". At 8 Gen back and even a relatively small tree -- this might be more likely than one would think
Quote from kevync on 2025-01-07, 3:04 pmI assume you essentially want to color code from a Common Ancestor and their descendants This can be done within RM using advanced Groups in RM10 wit the cavaet of anyone belonging to more than one ancestor will be written over with the last "Write". At 8 Gen back and even a relatively small tree -- this might be more likely than one would think
Well, kinda yeah.
My goal (and current manual way) is 8 colors for the 8 great grandparents and all of their direct ancestors. Then 8 other colors for any of their descendants. No colors for spouses. I think this would require 16 different searches/groups in RM. (8 for direct ancestors, 8 more for each sets of descendants (or I guess this is a collateral...I'm just now learning that term)). And yes, the person who has both parents colored would be colored with whatever search/coloring I did last.
I'd prefer that they get colored based on the parent's color who's a "closer" cousin of mine. And I'd prefer to hit F9 in SQLiteSpy a few times over having 16 saved searches and coloring steps in RM. But maybe that's easier and I'll have to settle for it.
"Well, maybe it's easier than this thinking. It's not about multiple relationships with the same person. It's the one relationship of their father to me, and the one relationship of their mother to me, and whichever is closest, then that parent's color should be the child's color. "
In that case, I think it's pretty easy.
I'm assuming that by the father's relationship to you and the mother's relationship to you that you mean the relationship as set by RM's Set Relationship tool. You go through ChildTable and FamilyTable and PersonTable to get the relationship and the color code for each parent. Then you set the child's color code to the color code of the parent who is more closely related to you. If there is only one parent, then use that parent's color.
The worrisome case is that the child might already be color coded. I'm not sure I understand your color coding scheme well enough to know what to do in that case. I fear there could be race conditions about who gets color coded first. And RM's new Set Relationships that supports "spouse of" has the same race conditions that can cause a "spouse of" relationship to take precedence over a blood relationship.
I think you might be able to create each group using SQLite -- then use either the scripts to update color or do with in RM or maybe simply use a CTE for each group and do all within one or two scripts. (the recursive part I have not played with for descendants but it would be based on a hierarchy org chart of all those who report a a manager.) So might be less work to do with group descendants of in RM advance search group.
While this would not do exactly what you are looking for, it might answer the fundamental need. Color code according to consanguinity - one color code set. Use whatever groups you want to filter on with that color coding set. The distance anyone is from you in that group is signified by their color. The closer they are, the stronger the color, the more significant. So, instead of using color to identify both a grandparent's ancestors and descendants and their distance, use the group to filter and dedicate color to distance.
See Color Code by Consanguinity Degree #colorcoding #relationships
Yes, I greatly dislike the "spouse of" thing in RM.
I'm assuming that by the father's relationship to you and the mother's relationship to you that you mean the relationship as set by RM's Set Relationship tool. You go through ChildTable and FamilyTable and PersonTable to get the relationship and the color code for each parent. Then you set the child's color code to the color code of the parent who is more closely related to you. If there is only one parent, then use that parent's color.
Exactly. But no colors for "spouses of".
Seeing the original post's recursive method made me think of how this could be applied to my case. Using that original methodology, my original thinking was:
- Step "a": Clear colors from Colors (the non-numbered color, but could be color3, whatever). Then set colors for each of my 8 great grandparents. RIN XXXX would be color=1, RIN YYYY would be color=2, etc.
- Step "b": Recursively (meaning, multiple presses of F9), for each person who has color=1, color each parent color=1, repeat for colors 2-8.
- Step "c": Color descendants who aren't already colored. For every person who is color=1, set each child to color=9 as long as that child isn't already colored. Repeat for color=2 to child SET color=10, etc through the 8 colors (mapped to colors 9-18 for the children). This would exclude spouses by definition.
BUT, that will just color the children the color of whatever was done last. I'd prefer to step through each child, if only one parent is colored, color the child that color. If both parents are colored, choose the color of the person more closely related, maybe defined as Relate1+Relate2. So, just like @thejerrybryan said.
I think I understand the race condition. I think that race condition would not occur if you just step through each person and then color them based on their parent's color and relationship to me. Maybe "stepping through" isn't possible in SQL, only selecting. I can't think well in SQL, but in other pseudocode:
FOR N=1 to max(RID)
IF parent1.color<>0 AND parent2.color=0
N.color = parent1.color
ELSE IF parent2.color<>0 AND parent1.color=0
N.color=parent2.color
ELSE IF parent1.color<>0 AND parent2.color<>0
IF (parent1.relate1 + parent.relate2) < (parent2.relate1 + parent2.relate2)
N.color=parent1.color
ELSE
N.color=parent2.color
NEXT N
I understand if you SELECT everyone who's color is RED and then set all children color to PINK, then do the same for the other 7 colors, it would be whatever was last written and gives no priority to how closely they are related if both parents were my relation.
Also, beside the priority of which parent is closer, discounting that entire line of thinking, I don't think this can be accomplished in RM groups/search either, as it considers any spouse to be related. So grouping/searching for descendants will include spouses. I don't know how to exclude spouses in RM, which is the whole reason I found this thread! I hate the "spouse of" thing. It should be an option to enable, or a completely separate thing, and if they are blood related to you, that should take priority over "spouse of". Argh!!
If anyone knows how to unselect spouses in group/search "decendants", I'd love to hear how.
Excluding spouses of is relatively easy (now with caveat there could be a secondary relationship). This actually ties into the scripts I began working on last night -- I will share once I finish. However, you gave me another idea to include about Ancestors and descendants thereof. (which would be a separate CTE).
Kevin