Subcategories

• Installation

  Installing and deploying the VisionAppster platform in various environments

  2
  Topics
  3
  Posts

  M

  I noticed that in online documentation (APIs -> Client APIs -> Remote object system -> Callback as function arguments) might have some outdated information. I was able to figure out, that app creates api function with signature sum: (a: int, b: int, success: (int) -> void, error: (int) -> void) -> void instead of sum: (callback: (int) -> void, a: int, b: int) -> void So in that case example would be POST /myobject/functions/sum HTTP/1.1 Host: localhost:2015 Client-ID: R4Nd0M Source-ID: 30 Content-Type: application/json Content-Length: 15 [1,2,314,315]
• Engine

  Configuring, running and connecting to the VisionAppster Engine

  3
  Topics
  15
  Posts

  

  @ms I came back to this when running release tests with our new release. The simplest thing you can do is to explicitly disconnect the ctrl object on error: async function test() { let ctrl; // move declaration here try { const va = typeof window === "object" ? VisionAppster : // Browser require("visionappster"); // Node.js const inputs = [ await va.Image.fromUrl('image.jpg') ]; ctrl = new va.RemoteObject("http://localhost:2015/apis/com.myapps.testapp/1"); const api = await ctrl.connect(); await api.sendImage.async(...inputs); console.log('Success.'); } catch { console.error("Failed."); ctrl.disconnect(); // add this } } It is hard to do this automatically because JS is a garbage-collected language with no destructors. When the app on the server side is brought down, its control channel remains because no one called disconnect() on the client side. The JS runtime can keep the old instance alive arbitrarily long. Since there is a reference to the WebSocket instance, the connection will remain active as well. Now, when you create a new RemoteObject instance, it shares an existing connection by default (you are using the default mechanism). This time however the existing connection is defunct. The old server-side object does not exist any more although there is a new one in the same URL. The channel sharing mechanism could be improved to take the remote object ID into account, but that would be a rather invasive change now. The work-around is quite simple and I hope it will work for you for the time being. We'll come back to this during the next release cycle. -Topi-
• Builder

  The IDE for building vision apps

  9
  Topics
  36
  Posts

  B

  @Topi Yeah, that's too bad... I'll try the Linux binary in a VM, or try remoting into my Windows machine.
• Tools

  Using and creating vision tools

  3
  Topics
  11
  Posts

  

  We are welcoming all feedback related to the upcoming Python API. What kind of an API would you want to see? Which libraries should be included? NumPy and OpenCV will be included, but which other libraries would you like to have? Here's a sneak peek of what is coming out: import visionappster as va class Binarize: """Binarizes an image using a static gray-level threshold. """ def level_min(self): return 0 def process(self, inputs: {'image': va.int32, 'level': {'type': va.int32, 'min': lambda: self.level_min(), 'max': 255, 'default': 127}}, outputs: {'image': {'type': va.Image, 'imageType': 'raw'}}) -> va.int32: # Implementation here: read inputs and write to outputs return va.SUCCESS tools = [Binarize]