Glossary

In this page you will find a list of terms used on the Asimovo RoboDevOps platform and their explanation in alphabetical order.

Knowing the meaning behind these expressions are important to fully benefit from the use of the platform and the capabilities it offers.

• Add-On When creating a Workspace you need to choose the ROS and Gazebo version as part of the Platform Configuration. Besides these, you can select some additional software to be added to the configuration. These are called Add-Ons. The Add-Ons on the platform are subdivided into three categories: ROS2 Packages, Data Science and Machine Learning tools.

• Asset

  Assets on the Asimovo platform are used to share various elements of your work. Currently we differentiate 4 types of assets: Robots, Environments, Components and Workspace Assets. Assets are folders (or folder structures) with a Manifest file included in the first folder level.

  Robot assets are any type of robot used in a simulation, while Environment assets are the worlds that are launched. Component assets can be any other software, code or part that are not Robots or Environments. Workspace assets are created from Workspaces for the purpose of sharing them on the Asimovo platform with other users.

  • Complexity: Each asset can contain a tag for complexity. Complexity is measured in ‘low’, ‘medium’ or ‘high’.

  • Creator: The name of the person who created the asset can be added, so later people can sort and filter by their favourite creators.

  • Size: The file size of the asset

• Hardware

  Hardware refers to the choice of computing resources you use to open your workspace. There is a menu approach where you can choose between locally running hardware (your local machine) or a number of different cloud based resources. If you are running a detailed simulation environment we recommend using hardware that includes graphics cards in order to render the environment sufficiently.

• Project An area to work, this can include a project-tool kit, team members, assets/work packages and the ability to share the outputs of the development and testing cycles carried out as a team. Each project has a dashboard overview where you can see the latest changes and comments

• Session When you start a Workspace this triggers the beginning of a session. You have the ability to change the timer so sessions will close after a set time. We put a default 2hour timer on all sessions to prevent people accidentally using up all their simulation credits if they forget to stop and close their simulations. If you are running longer scale testing and simulation works you can manually adjust the session timer to run longer or shorter as desired.

• Simulation Credit Trial accounts and paid subscriptions both come with an allocation of Simulation Credits. If you choose to work in cloud based workspace you will begin to use up your simulation credits. Choosing the right hardware is not only a performance question but also a cost question. Choosing cloud based infrastructure will use up simulation credits on a minute by minute basis. The higher performance the hardware, the more simulation credits will be used per minute. When selecting your hardware you will see how many simulation credits it will use per minute while running. It is important to stop and close your workspace when you are finished.

• Results

  While running a simulation you can save a wide range of data types, including rosbag sensor data, images, videos, text files, logs, and more. This allows you to easily preserve all the valuable information for future use.

• Tag When working in your project and with assets we enable you to add tags. This makes it easier to filter and find the correct files at a later date or when working across complex projects.

• Team Each project has the ability to add team members. When adding someone to your team, you as team owner can allocate different roles and rights. You also have the ability to delete team members at anytime.

  • Role - different roles can be allocated to different team members such as commenter, admin or editor.

  • Team members - are the people you can add to projects and communicate with via your project work and documentation

• Workload

  Anything that we provision on our systems that runs software and consumes computational resources like CPU and memory. An example of this is a running Workspace.

• Workspace This is a local or cloud based integrated development environment. You create or open a workspace when you want to start doing some work. A workspace can be configured with different images, assets and compute resources.

Next tutorial - Home

With the next section of the tutorials you can start discovering the functionalities of the Asimovo RoboDevOps Platform in more detail. You will learn about the Home page of the platform in the next tutorial.