Skip to content

Adding gff support for NearestExonJB plugin - #856

Open
jamie-m-a wants to merge 1 commit into
Ensembl:postreleasefix/116from
jamie-m-a:feature/NearestExonJB_gff_update
Open

Adding gff support for NearestExonJB plugin#856
jamie-m-a wants to merge 1 commit into
Ensembl:postreleasefix/116from
jamie-m-a:feature/NearestExonJB_gff_update

Conversation

@jamie-m-a

Copy link
Copy Markdown
Contributor

Summary

This PR allows NearestExonJB to retrieve exon locations from a tabix-indexed GFF3 file:
--plugin NearestExonJB,gff3=/path/to/genes.gff.gz

It also adds parent_only=1, which excludes exons from readthrough transcripts, artifact genes, and unsupported GFF gene-parent types.

To test...

Use this variant:
1 1243545 . G A

Compare the database-backed plugin:
--plugin NearestExonJB,intronic=1

with the GFF-backed plugin:
--plugin NearestExonJB,gff3=Homo_sapiens.GRCh38.116.chr.gff.gz,intronic=1,parent_only=1

Using the release 116 GFF, both modes should annotate the same transcripts and exon boundaries:

ENST00000330388.2 ENSE00001299832+7+end+109
ENST00000468365.1 ENSE00001882488+7+end+287
ENST00001086007.1 ENSE00001299832+7+end+109
ENST00001145430.1 ENSE00001299832+7+end+109
ENST00001086006.1 ENSE00004705606+393+end+91 ENSE00001311835+409+start+152

The other transcripts should have nothing.

@likhitha-surapaneni
likhitha-surapaneni self-requested a review August 13, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant