|
By 212529 - Thursday, July 16, 2015
|
|
appleshaw (16-Jul-2015)
Have you checked the dates, particularly Union Date
Yes, I didn't enter "Union date" under "Unions" tab. Nevertheless, regardless of union date and union type, no union can exist, if one individual is deceased before the other is born. Spotter should definitely recognize this as an error.
|
|
By GenoProSupport - Sunday, July 19, 2015
|
|
Sorry, I did split the thread and those posts came together accidentally. Can you please post a sample .gno file so I can test and make a fix? Thanks.
|
|
By 212529 - Sunday, July 19, 2015
|
File is attached below.
Plus one smaller problem: when union type is not marriage, but e.g. engagement spotter use in problem description marriage instead engagement (see photo).
|
|
By GenoProSupport - Monday, July 20, 2015
|
|
Thanks for the explanation. I did changed the text to be a bit more descriptive, however the underlying problem is the Relation and the Unions may be incoherent. For GenoProX, each Relation will be an event and it will be easier for the Problem Spotter to detect incoherent events (such as someone marrying before being engaged, or a divorce before a marriage, etc)
|
|
By 212529 - Tuesday, July 21, 2015
|
Sorry, I may not be clear enough. Current version of spotter does not recognize following error: Individual A is deceased before individual B is born. Therefore individual A and individual B can not be in union.
Spotter should recognize such error, even when there is no union date.
|
|
By GenoProSupport - Tuesday, July 21, 2015
|
|
Great logic. Thanks. I filed it as a task to Pivotal Tracker (the software we use to keep track of our 'todo' list) as well as I added it to the "suggestions for GenoProX" at http://support.genopro.com/Topic35259.aspx . The Problem Spotter will be built along with GenoProX (not later when the product is ready), so this feature will be available in about 6 months.
|