Thank you so much @novinosrin! I think my attempts to simplify actually made it much LESS clear and I am sorry! I'm attaching my dataset so hopefully it's a little easier to understand. ID=each person's unique ID (note that unlike the example I typed in the beginning, it is not in consecutive order, it's just a random, unique number) case: if this=1, it means that ID matched to two other IDs for whom case=0. My goal is to give that triplet the same value of some new variable (matchvar) as each other. The way to find the two controls that each case matched to is by using the match_1 and match_2 variables. For example, ID 29759649502 has a value of 10000032 for match_1. Its corresponding matched control pair is way down the spreadsheet at ID 28477027301, who also has a value of 10000032 for match_1. ID 29759649502's value for match_2 is 10000033, so its second matched control pair is ID 2490602401 which also has a value of 10000033 for match_2. I tried to paste a bit of my spreadsheet below and bold the relevant rows. Does that help? I am so appreciative of your help!!
ID
case
match_1
match_2
1953457302
0
10000019
1640479605
1
10000019
10000019
2256689601
0
10000021
25051280101
1
10000021
10000021
2490602401
0
10000033
29759649502
1
10000032
10000033
.....
ID
case
match_1
match_2
28477027301
0
10000032
.
......
Hi @Lefty Do not worry about the code/syntax and concept. We are here to help you.
"ERROR: Duplicate key."
means the HASH table has been set with a constraint to have only unique keys, and that was on purpose. But now that my assumption is wrong, I would appreciate if you could post us a more comprehensive sample.
Example, Let me modify your sample from obs1-3 by copying the 1-3 and appending as 4-6
1 . 100000022 0 2 1000024 100000022 1 3 1000024 . 0 4 . 100000022 0 5 1000024 100000022 1 6 1000024 . 0
So here 4-6 is a copy paste of 1-3. So the case combination 1000024 100000022 1 has occurred twice making it a duplicate that wasn't compliant to the constraint set. Not a problem. However, before I modify the code, I would rather like to see to more representative sample. Also, would the above 6 be tagged to the same match_var?
I know it can go back and forth, I'd appreciate your time. Thanks!
@novinosrin wrote:
Hi @Lefty Do not worry about the code/syntax and concept. We are here to help you.
"ERROR: Duplicate key."
means the HASH table has been set with a constraint to have only unique keys, and that was on purpose. But now that my assumption is wrong, I would appreciate if you could post us a more comprehensive sample.
Example, Let me modify your sample from obs1-3 by copying the 1-3 and appending as 4-6
1 . 100000022 0 2 1000024 100000022 1 3 1000024 . 0 4 . 100000022 0 5 1000024 100000022 1 6 1000024 . 0
So here 4-6 is a copy paste of 1-3. So the case combination 1000024 100000022 1 has occurred twice making it a duplicate that wasn't compliant to the constraint set. Not a problem. However, before I modify the code, I would rather like to see to more representative sample. Also, would the above 6 be tagged to the same match_var?
I know it can go back and forth, I'd appreciate your time. Thanks!
@novinosrin wrote:
Hi @Lefty Do not worry about the code/syntax and concept. We are here to help you.
"ERROR: Duplicate key."
means the HASH table has been set with a constraint to have only unique keys, and that was on purpose. But now that my assumption is wrong, I would appreciate if you could post us a more comprehensive sample.
Example, Let me modify your sample from obs1-3 by copying the 1-3 and appending as 4-6
1 . 100000022 0 2 1000024 100000022 1 3 1000024 . 0 4 . 100000022 0 5 1000024 100000022 1 6 1000024 . 0
So here 4-6 is a copy paste of 1-3. So the case combination 1000024 100000022 1 has occurred twice making it a duplicate that wasn't compliant to the constraint set. Not a problem. However, before I modify the code, I would rather like to see to more representative sample. Also, would the above 6 be tagged to the same match_var?
I know it can go back and forth, I'd appreciate your time. Thanks!
@novinosrin wrote:
Hi @Lefty Do not worry about the code/syntax and concept. We are here to help you.
"ERROR: Duplicate key."
means the HASH table has been set with a constraint to have only unique keys, and that was on purpose. But now that my assumption is wrong, I would appreciate if you could post us a more comprehensive sample.
Example, Let me modify your sample from obs1-3 by copying the 1-3 and appending as 4-6
1 . 100000022 0 2 1000024 100000022 1 3 1000024 . 0 4 . 100000022 0 5 1000024 100000022 1 6 1000024 . 0
So here 4-6 is a copy paste of 1-3. So the case combination 1000024 100000022 1 has occurred twice making it a duplicate that wasn't compliant to the constraint set. Not a problem. However, before I modify the code, I would rather like to see to more representative sample. Also, would the above 6 be tagged to the same match_var?
I know it can go back and forth, I'd appreciate your time. Thanks!
... View more