Fix EPO-Extended low-coverage species classification#1164
Open
twalsh-ebi wants to merge 1 commit into
Open
Conversation
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.
Requirements
Description
ensembl-webcode PR 1158 updated the web code to support
EPO_EXTENDEDalignments.However, the code setting
$is_low_coverage_specieswas in need of an update to reflect changes in the web code since the switch fromEPO_LOW_COVERAGEtoEPO_EXTENDED, in order to ensure that the species production name is used when accessing packedALIGNMENTSmetadata.This PR would implement that update, fetching the production name using the species URL accessed via
$object->speciesand using that to access relevantALIGNMENTSmetadata.Views affected
This affects EPO-Extended alignment views, particularly those with a text alignment slice table.
Example:
Possible complications
None expected, as this change is in a section of code specific to
EPO_EXTENDEDandEPO_LOW_COVERAGEalignments.Merge conflicts
None detected.
Related JIRA Issues (EBI developers only)