You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During Emma intership, the visualisation was a tool and works well.
During Caroline intership, the visualisation become a real visualisation and work well on her setup.
But on a production Galaxy instance, Biopython is needed but seems not available
Module blastvisu_mako:68 in render_body view
>> from Bio.Blast import NCBIXML
ImportError: No module named Bio.Blast
So, we will need to find a way:
install Biopython
use an alternative to parse the xml file
The text was updated successfully, but these errors were encountered:
I guess you need to have this installed into the Galaxy venv to make it work. @guerler is it possible to have a requirement tag inside the visualisation.xml file? This way we could hook up arbitrary dependencies in visualisations.
Indeed, my next move will be to install Biopython in the Venv. But I was surprise because the user galaxy can access to the lib Biopython installed on the cluster.
I haven't search so much.
And sure, it would be great if there is a system of tool dependenties.
During Emma intership, the visualisation was a tool and works well.
During Caroline intership, the visualisation become a real visualisation and work well on her setup.
But on a production Galaxy instance, Biopython is needed but seems not available
So, we will need to find a way:
The text was updated successfully, but these errors were encountered: