Input tree preprocessing checking

[parisakianmajd]

/Dropbox/Euler-Runs/challenges/k95m00-names.txt => needs only 1 fix, but so far no solutions Issue: User misspelled a concept in two ways such that one input taxonomy has in fact two roots; and so the articulations that are affect likely all become inconsistent "en groupe"; fix: correct spelling error => now two internally coherent taxonomies that are consistent; lesson: have the ability to check for coherence/proper spelling in each input taxonomy.
⇒ new feature request: check T1, T2 for “tree-ness” property → preprocessor prior to the main Euler TAP solving call that makes sure this (and other) properties are guaranteed on the input

[nfranz]

Thanks, Parisa. Good to see these issue wandering over from Bitbucket. Has Issue #20 there been addressed?