Skip to content

Update G2P plugin docs - #977

Open
dglemos wants to merge 2 commits into
Ensembl:postreleasefix/116from
dglemos:update_g2p_plugin_docs_e116
Open

Update G2P plugin docs#977
dglemos wants to merge 2 commits into
Ensembl:postreleasefix/116from
dglemos:update_g2p_plugin_docs_e116

Conversation

@dglemos

@dglemos dglemos commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Update the plugin docs to reflect the latest G2P options update in the following PR Ensembl/VEP_plugins#844

./vep -i variations.vcf --plugin FunMotifs,/path/to/funmotifs/blood.funmotifs_sorted.bed.gz,fscore,dnase_seq</p><p>Parameters Required:</p><p>[0] : FunMotifs BED file
[1]+ : List of columns to include within the output (e.g. fscore, skin, contactingdomain)</p><p></pre></p></p></div></td><td><div class="vdoc_dtype_count" style="white-space:normal;float:left;padding:2px 6px;cursor:default;background-color:#DAA520">Motif</div></td><td>-</td><td>Ensembl</td></tr>
<tr id="G2P" class="bg2 plugin_row" data-category="phenotype_data_and_citations"><td><div style="font-weight:bold"><a rel="external" href="https://github.com/Ensembl/VEP_plugins/blob/release/[[SPECIESDEFS::ENSEMBL_VERSION]]/G2P.pm">G2P</a></div><div style="margin-top:6px"><small>gene2phenotype</small></div></td><td><p> An Ensembl VEP plugin that uses G2P allelic requirements to assess variants in genes
<tr id="G2P" class="bg2 plugin_row" data-category="phenotype_data_and_citations"><td><div style="font-weight:bold"><a rel="external" href="https://github.com/Ensembl/VEP_plugins/blob/release/[[SPECIESDEFS::ENSEMBL_VERSION]]/G2P.pm">G2P</a></div><div style="margin-top:6px"><small>gene2phenotype</small></div></td><td><p> An Ensembl VEP plugin that uses G2P (www.ebi.ac.uk/gene2phenotype) allelic requirements to assess variants in genes

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to add a hyperlink here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added the link

the value of 0 forces variants with no frequency data to be
included as this is considered equivalent to having a frequency
of 0. Set to 1 (or any value higher than <kbd>af</kbd>) to exclude them.</p><p><tr class="bg1"><td><pre>types</pre></td><td>SO consequence types to include. Separate multiple values with <kbd>&</kbd> (splice_donor_variant, splice_acceptor_variant, stop_gained,
<ul><li><kbd>topmed</kbd> - TOPMed (available for GRCh37 and GRCh38).</li><li><kbd>uk10k</kbd> - ALSPAC, TWINSUK (available for GRCh37 and GRCh38).</li><li><kbd>gnomADe</kbd> & <kbd>gnomADe_r2.1.1</kbd> & <kbd>gnomADe_v4.1</kbd> - gnomADe:AFR, gnomADe:ALL, gnomADe:AMR, gnomADe:ASJ, gnomADe:EAS, gnomADe:FIN, gnomADe:NFE, gnomADe:OTH, gnomADe:SAS (for GRCh37 and GRCh38 respectively).</li><li><kbd>gnomADg</kbd> & <kbd>gnomADg_v3.1.2</kbd> & <kbd>gnomADg_v4.1</kbd> - gnomADg:AFR, gnomADg:ALL, gnomADg:AMR, gnomADg:ASJ, gnomADg:EAS, gnomADg:FIN, gnomADg:NFE, gnomADg:OTH (for GRCh37 and GRCh38 respectively).&nbsp; Need to use <kbd>af_from_vcf</kbd> parameter to use this option. </p><p><tr class="bg1"><td><pre></li></ul><p> only_vcf_freq</pre></td><td>set to 1 to only use frequency from vcf files, can only be set if af_from_vcf is set. N/B - frequency information may be lost if this option is used </p><p><tr class="bg2"><td><pre>types</pre></td><td>VEP SO consequence terms to include. Separate multiple values with <kbd>&</kbd>. This option replaces the default list. By default, the plugin uses:

@likhitha-surapaneni likhitha-surapaneni Jul 27, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a minor comment, there is an extra space before only_vcf_freq

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VEP -> Ensembl VEP

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

inframe_insertion, inframe_deletion,missense_variant,
coding_sequence_variant, start_lost,transcript_ablation,
transcript_amplification, protein_altering_variant)</p><p><tr class="bg2"><td><pre>log_dir</pre></td><td>write stats to log files in log_dir
transcript_amplification, protein_altering_variant</p><p><tr class="bg1"><td><pre>add_types</pre></td><td>VEP SO consequence terms to append to the default types list. Separate multiple values with <kbd>&</kbd>.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VEP -> Ensembl VEP

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

Matching is case-insensitive.
Empty submitter names are not supported.</p><p><tr class="bg1"><td><pre>filter_consequence_match</pre></td><td>to only report variants where the VEP predicted consequence matches the G2P variant consequence term (GenCC term).
Accepted values are:
<ul><li>broad: includes 'almost always', <kbd>probable</kbd> and <kbd>possible</kbd> matches</li><li>strict: includes 'almost always' and <kbd>probable</kbd> matches&nbsp; This option is only supported with G2P input files.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the formatting as expected foralmost always ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@likhitha-surapaneni likhitha-surapaneni left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

3 participants