Deepomatic Platform
  • Overview
  • Release notes
    • January 2025
    • November 21, 2024
    • October 17, 2024
    • September 19, 2024
    • July 18, 2024
    • June 27, 2024
    • May 23, 2024
    • April 18, 2024
    • March 21, 2024
    • February 22, 2024
    • January 18, 2024
    • December 13, 2023
    • October 26, 2023
    • July 20, 2023
    • June 29, 2023
    • May 29, 2023
    • April 27, 2023
    • March 30, 2023
    • February 17, 2023
    • January 19, 2023
    • December 22, 2022
    • November 18, 2022
    • October 19, 2022
    • September 19, 2022
    • July 27, 2022
    • June 26, 2022
    • May 17, 2022
    • April 13, 2022
    • March 17, 2022
    • February 10, 2022
    • December 21, 2021
    • October 26, 2021
  • Getting started
  • ADMIN & USER MANAGEMENT
    • Invite and manage users
      • Invite group of users at once
      • SSO
        • Azure Active Directory
  • Deepomatic Engage
    • Integrate applications
      • Deepomatic vocabulary
      • Deepomatic connectors
        • Set-up
        • Camera Connector
        • Work Order Connector
      • API integration
        • Authentication
        • Errors
        • API reference
          • Work order management
          • Analysis
            • Guide field workers
            • Perform an analysis
            • Correct an analysis
          • Data retrieval
          • Endpoints' list
      • Batch processing
        • Format
        • Naming conventions
        • Processing
        • Batch status & errors
      • Data export
    • Use the mobile application
      • Configure a mobile application
      • Create & visualize work orders
      • Complete work orders
      • Offline experience
    • Manage your business operations with customisable solutions
      • Roles
      • Alerting
      • Field services
        • Reviewing work orders
        • Exploring work orders
        • Grouping work orders
        • Monitoring assets performance
      • Insights
  • Security
    • Security
    • Data Protection
Powered by GitBook
On this page
  • Errors about environment variables
  • Error 11001: getaddrinfo failed
  • Setup a proxy
  • What is the difference between input_fps and skip_frames?

Was this helpful?

  1. Deepomatic CLI

FAQ

Last updated 15 days ago

Was this helpful?

Errors about environment variables

An environment variable is a variable that is defined in the terminal and used by the executable afterwards. In the context of Deepomatic CLI there is one environment variables used:

  • DEEPOMATIC_API_KEY is used to interact with trained models and to send images or JSON to Deepomatic Studio.

If you get the following error, please check that your DEEPOMATIC_API_KEY is set and is the one from the right organization.

deepomatic.api.exceptions.ClientError: Bad status code 401 with body b'{"detail":"No such profile user."}'

Error 11001: getaddrinfo failed

You get this error because Deepomatic CLI cannot reach the Deepomatic endpoints. Most of the times this is the consequence of a Proxy that has not been setup.

Setup a proxy

The easiest way to do it is to simply pass the proxy parameters as an environment variable. You will need:

  • proxyserver: the proxy server address.

  • proxyport: the proxy server port.

  • user: your proxy user login identifier.

  • password: your proxy authentication password.

export https_proxy="http://user:password@proxyserver:proxyport"
$Env:https_proxy="http://user:password@proxyserver:proxyport"

The Deepomatic CLI uses only secured https connection. As such, you just need to setup the https_proxy environment variable.

If you're running inferences on your local infrastructure you might want to take a look at how to Configure Docker to use a proxy server.

What is the difference between input_fps and skip_frames?

If your camera has an original frame rate of 30fps, and you want to run inferences at 3 fps, the options input_fps and skip_frames can both enable you to do it, with input_fps=3 or skip_frames=2 .

input_fps uses the fps of the input automatically detected to force a new fps. It is simple to use, but requires that the original fps detected is correct. In most cases, it will work fine, but sometimes the FPS automatically detected in the video isn't reliable as it is encoded in the file header.

For example, in .avi videos, duplicate frames are represented by an instruction to repeat the previous frames and are skipped by the library OpenCV, which only reads frames with real data.

Another case in which input_fps may not be the best option, is when the original fps is not a multiple of the input_fps . In this case, we recommend to use skip_frames

skip_frames allows you to skip a fixed number of frames and analyze only 1 frame every N frames. It is independent of the original fps detected, and requires you to calculate the value desired.

skip_frames = original_fps / input_fps -1

Find how to get the API Key value here: Setup your Deepomatic API Key