[ensembl-dev] RegulatoryFeature (and MotifFeature?) not fully qualifying correctly in BaseVepPlugin

[Michael Yourshaw]

In BaseVepPlugin sub _check_types, it appears that if a user specifies ‘RegulatoryFeature’ in feature_types, the fully qualified feature that gets built and added to $wanted is Bio::EnsEMBL::RegulatoryFeature whereas the $type of the feature is Bio::EnsEMBL::Funcgen::RegulatoryFeature. This causes unexpected failure to run. While there is an obvious work-around, it would be nice to take the shortcut.

I haven’t stepped through the code, but it looks like something similar happens with MotifFeature.

ॐ

Michael Yourshaw
UCLA Geffen School of Medicine
Department of Human Genetics, Nelson Lab
695 Charles E Young Drive S
Gonda 5554
Los Angeles CA 90095-8348 USA
myourshaw at ucla.edu
970.691.8299

This message is intended only for the use of the addressee and may contain information that is PRIVILEGED and CONFIDENTIAL, and/or may contain ATTORNEY WORK PRODUCT. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20120112/9ca5671a/attachment.html>