Register enhancer order-control VEP checkpoint - #542
Open
gonzalobenegas wants to merge 1 commit into
Open
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Register the terminal checkpoint of the issue #517 strict phyloP enhancer experiment with one sequence source per vertebrate order.
The entry uses a 255-base DNA window and adds only Mendelian and Complex Traits development evaluations.
The final export was verified against GCS checksums on September 8.
The research evaluation environment passed 416 tests with five skips using CPU selection for unit-test mocks, plus the separate pinned A10G GPU runtime check.
Its targeted dry-run contains two scoring jobs and two metric jobs, with no checkpoint-download job or unrelated evaluation.
The GPU-visible mock-test limitation is tracked in #544.
Part of #517.