Skip to content
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

DO NOT MERGE: Remove GARD - Build #682

Closed
wants to merge 1 commit into from
Closed

Conversation

joeflack4
Copy link
Contributor

Build for:

@joeflack4 joeflack4 marked this pull request as draft October 21, 2024 19:48
@joeflack4 joeflack4 changed the title Remove GARD - Build DO NOT MERGE: Remove GARD - Build Oct 21, 2024
@joeflack4 joeflack4 self-assigned this Oct 21, 2024
@joeflack4 joeflack4 added the build Mostly for build PRs: when changes only to data files post `build-mondo-ingest`; no code changes label Oct 21, 2024
@joeflack4 joeflack4 mentioned this pull request Oct 21, 2024
9 tasks
@joeflack4 joeflack4 requested a review from twhetzel October 22, 2024 01:17
Copy link
Contributor Author

@joeflack4 joeflack4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Feels like a surprisingly low amount of files changed, but I suppose that is mostly due to the removal of GARD.

Copy link
Contributor Author

@joeflack4 joeflack4 Oct 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New file in this build, FYI.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing this out. New or deleted files under lexmatch/split-mapping-set are not concerning since these split-mapping-set files are just subsets of the overall lexmatch files and some variance would be expected between runs. E.g. one run may have a new closematch entry that then creates a new file in lexmatch/split-mapping-set.

@@ -217,7 +217,7 @@ MONDO:0007060 skos:exactMatch OMIM:102530 spermatogenic failure 6 semapv:Unspec
MONDO:0007061 skos:exactMatch OMIM:102590 semapv:UnspecifiedMatching
MONDO:0007062 skos:exactMatch OMIM:102650 adactylia, unilateral semapv:UnspecifiedMatching
MONDO:0007064 skos:exactMatch OMIM:102700 severe combined immunodeficiency, autosomal recessive, t cell-negative, B cell-negative, nk cell-negative, due to adenosine deaminase deficiency semapv:UnspecifiedMatching
MONDO:0007066 skos:exactMatch OMIM:102800 adenosine triphosphatase deficiency, anemia due to semapv:UnspecifiedMatching
MONDO:0007066 skos:exactMatch OMIM:102800 semapv:UnspecifiedMatching
Copy link
Contributor

@twhetzel twhetzel Oct 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated to this PR, however this OMIM entry, without a label, has been moved to a new entry, https://www.omim.org/entry/102800, so this should not show up as an exactMatch.

OMIM ticket monarch-initiative/omim#157

Copy link
Contributor

@twhetzel twhetzel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for running a feature build for this related code change. I think this looks ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Mostly for build PRs: when changes only to data files post `build-mondo-ingest`; no code changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants