-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add qc workflow #1240
add qc workflow #1240
Conversation
@cmungall I ran
|
Sigh, I guess these crept in while we wre in the phase where we had no checking of PRs and things were merged in? You you show explanations for each (robot explain) The foodon ones are unusual - envo should not cause foodon to be unsatisfiable, could it be
|
@cmungall I don't know the provenance of how the offenders made it into EnvO. I can create a ticket to focus on fixing these issues. It is also worth noting that |
owltools is in ODK |
@ddooley ^^^ |
do we have a ticket about removing the foodon import currently it's only used in 3 places:
|
@wdduncan I suggest for now we switch off equivalence checking, get this merged, and then make a PR to re-introduce it, which we do as soon as foodon is fixed |
Hmm. the hominy equivalence is wrong - probably intended to be a conjunction, not a disjunction but even so, still not sufficient differentia. I've dropped it and will do new release shortly. |
I have dropped the hominy equivalence; It may be that all the above "no equivalent axioms are allowed" items are eliminated as a result. |
This has become urgent - where do we stand with this? |
From FoodOn's side a refresh of that import should resolve equivalency issue. |
@cmungall I updated the FOODON imports on my machine by running
The number of files changed makes @ddooley and myself hesitant to push these changes to the repo. Also, we noticed that a number of FOODON classes were not properly placed in the ENVO hierarchy (see screenshot). In any case, I ran
Not sure what the best path forward is. One option is to relax the equivalent action check:
merge the PR, and deal with the updates to FOODON in a separate PR. |
This is already a problem: https://www.ebi.ac.uk/ols/ontologies/envo let's not try and solve all problems with this PR. Adding github actions and fixing inconsistencies will be a major step forward. Let's get this merged ASAP then improve imports |
didn't we solve this? Maybe a rebase would fix? In any case, I agree with your strategy. Relax the constraints for now (we effectively have none now), then iterate |
@cmungall Re After relaxing the equivalent classes check and running make test , the following errors were reported:
These duplicate labels are related to synonyms that have a database cross reference to the Do you want me to fix these or relax this check too? |
I think we should fix synonyms as a separate Pr. there is an old ticket
about this
…On Fri, Jan 21, 2022 at 12:47 PM Bill Duncan ***@***.***> wrote:
@cmungall <https://github.com/cmungall> Re After relaxing the equivalent
classes check and running make test , the following errors were reported:
ERROR duplicate_label_synonym garden has_exact_synonym garden
ERROR duplicate_label_synonym ocean has_exact_synonym ocean
ERROR duplicate_label_synonym sea has_exact_synonym sea
ERROR duplicate_label_synonym stream has_exact_synonym stream
ERROR duplicate_label_synonym reservoir has_exact_synonym reservoir
These duplicate labels are related to synonyms that have a database cross
reference to the Geonames:feature. E.g.:
[image: image]
<https://user-images.githubusercontent.com/3186638/150597956-7143e741-72a2-49e0-9070-728265626c02.png>
Do you want me to fix these or relax this check too?
—
Reply to this email directly, view it on GitHub
<#1240 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMMOKWZUG6IFCZVMZGNDDUXHA5JANCNFSM5IDCH3QQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No description provided.