Skip to content

Input tree preprocessing checking #1

Description

@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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions