Navigation

    VisionAppster.com

    VisionAppster Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    VisionAppster Engine and python implementation on Windows

    Tools
    2
    2
    46
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      luqt123 last edited by

      Hi,
      I want to run my application on the VA engine, however my project uses PYTHON tools described in:
      C:\Users\<user>\VisionAppster\plugins\tool
      The project runs in the VA builder. When I package and install the app on localhost:2015 and try to run it error pops out saying
      Error: Unable to start analysis engine.
      There is no implementation available for "com.acme.python/0/PerspectiveTransformation".
      I tried to put the mytoolplugin.py to C:\Windows\ServiceProfiles\LocalService\VisionAppster\plugins\tool, and then run it again but still the same error.
      also adding mytoolplugin.py to the app resources doesn't solved the issue...

      Kind regards,
      Lukas

      Topi 1 Reply Last reply Reply Quote 0
      • Topi
        Topi @luqt123 last edited by

        In a local development environment, Python tools are loaded from your plugins/tool directory, which you have correctly done. Such local plugins aren't however automatically included in created packages because there is no reliable way to find out what is actually needed by the Python code.

        To create a package that contains a Python tool you need to copy the *toolplugin.py file to the analysisapp/ directory of your project. See here for an example. The example contains .tool files, but toolplugin.py files work as well.

        One more thing: it is a good idea to register your Python tools with the name of your component as the namespace. That is, if you use "com.acme.python/0" as the namespace, that should also be the full component ID of your component. Importing stuff from other components won't work properly otherwise.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Forum Terms of Use and Privacy Policy