Add stopgap fix for Stockholm format alignment export #1050
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.
Description
Because of a bug in the Stockholm alignment writer in BioPerl 1.6.x, homologue alignment downloads in Stockholm format have sequence identifiers that run on into the accession field:
This prevents the alignment from being loaded into (for example) Biopython, making it more difficult to process downloaded Stockholm files automatically.
This bug was fixed in bioperl-live PR 122, so code incorporating a bugfix is available in the event of an upgrade to BioPerl 1.7.0+.
In the meantime, this PR corrects the issue by fixing the generated Stockholm alignment string. As an illustration:
This makes it easier for Compara team members to test — and Ensembl users to work with — downloaded Stockholm files.
Views affected
This affects export of Stockholm format alignments of homologues.
To see the effect of this PR, try previewing or downloading Stockholm alignments for the following two examples:
Possible complications
As these changes only have an effect on the
GS
lines of Stockholm-format alignments in which the sequence identifier runs on into the accession field, no complications are expected.Merge conflicts
None detected.
Related JIRA Issues (EBI developers only)
N/A