-
Notifications
You must be signed in to change notification settings - Fork 128
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
Fix translate #1109
Closed
Closed
Fix translate #1109
Conversation
This file contains 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
…re type source for vcf and alignment mode. Fixes nextstrain#1108 by moving the warning about padding outside of translate_vcf_feature where the feature name is also available and does not need to be passed on to translate_vcf_feature
jameshadfield
added a commit
that referenced
this pull request
Dec 4, 2023
This check is already in place for non-VCF inputs, and my guess is it was omitted here as the TB pipeline's GFF file didn't include a 'source' annotation. I don't think 'source' is actually a valid GFF ID and I suspect we've just been applying the INSDC/GenBank term to GFF files, but it is one of the two fields parsed by `load_features` and there are GFF files in Nextstrain build pipelines which use it. Modifying the underlying `load_features` would be a better solution, but that's a bigger project for another day. We additionally update the error message to use the same feature name we export. Closes #591 Supersedes #1109
jameshadfield
added a commit
that referenced
this pull request
Dec 4, 2023
This check is already in place for non-VCF inputs, and my guess is it was omitted here as the TB pipeline's GFF file didn't include a 'source' annotation. I don't think 'source' is actually a valid GFF ID and I suspect we've just been applying the INSDC/GenBank term to GFF files, but it is one of the two fields parsed by `load_features` and there are GFF files in Nextstrain build pipelines which use it. Modifying the underlying `load_features` would be a better solution, but that's a bigger project for another day. We additionally update the error message to use the same feature name we export. Closes #591 Supersedes #1109
jameshadfield
added a commit
that referenced
this pull request
Dec 5, 2023
This check is already in place for non-VCF inputs, and my guess is it was omitted here as the TB pipeline's GFF file didn't include a 'source' annotation. I don't think 'source' is actually a valid GFF ID and I suspect we've just been applying the INSDC/GenBank term to GFF files, but it is one of the two fields parsed by `load_features` and there are GFF files in Nextstrain build pipelines which use it. Modifying the underlying `load_features` would be a better solution, but that's a bigger project for another day. We additionally update the error message to use the same feature name we export. Closes #591 Supersedes #1109
jameshadfield
added a commit
that referenced
this pull request
Dec 11, 2023
This check is already in place for non-VCF inputs, and my guess is it was omitted here as the TB pipeline's GFF file didn't include a 'source' annotation. I don't think 'source' is actually a valid GFF ID and I suspect we've just been applying the INSDC/GenBank term to GFF files, but it is one of the two fields parsed by `load_features` and there are GFF files in Nextstrain build pipelines which use it. Modifying the underlying `load_features` would be a better solution, but that's a bigger project for another day. We additionally update the error message to use the same feature name we export. Closes #591 Supersedes #1109
Thanks for this @andreott, and sorry it slipped through the cracks for so long. The underlying issue has been addressed by #1348. Please see comment #1348 (comment) for more details. |
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.
Description of proposed changes
Fixes #591 in translate.py by perfoming the check for feature type source for vcf and alignment mode.
Fixes #1108 by moving the warning about padding outside of translate_vcf_feature where the feature name is also available and does not need to be passed on to translate_vcf_feature
Related issue(s)
Fixes #591
Fixes #1108
Testing
What steps should be taken to test the changes you've proposed?
If you added or changed behavior in the codebase, did you update the tests, or do you need help with this?
I ran it on my vcd input data and it worked. Should not effect any other code parts
Checklist