covmatic-robotmanager

Name	covmatic-robotmanager JSON
Version	0.0.6 JSON
	download
home_page
Summary	Covmatic Robot Manager is a robotic arm manager for action requested by other robots
upload_time	2023-08-09 12:33:18
maintainer
docs_url	None
author
requires_python	>=3.7
license
keywords	automation biology lab robotics
VCS
bugtrack_url
requirements	No requirements were recorded.
Travis-CI	No Travis.
coveralls test coverage	No coveralls.

# RobotManager
Manager code for EVA robot from Automata.

## Warning
**This is a development program and not ready for production-use.
This is part of a project in development.**

## Table of Contents
* [Introduction](#introduction)
* [Installation](#installation)
* [Setup](#setup)
* [Calibration](#calibration)
* [Execution](#execution)
* [Testing](#testing)

## Introduction

The *covmatic-robotmanager* comes with two scripts callable in a command shell:
- *robotmanager-calibrator* is a helper program useful to save precise and repeatable calibrations.
- *robotmanager-server* is the main server that listen for actions to do;

Source code is on [ASST Bergamo Est repository](https://github.com/ASST-Bergamo-Est/covmatic-robotmanager)

## Installation

You can [install the Covmatic LocalWebServer via `pip`](https://pypi.org/project/covmatic-robotmanager):
```
<python> -m pip install covmatic-robotmanager
```
Where `<python>` should be changed for the Python instance you wish to install the Robotmanager onto. We will be following this convention for all the next instructions.

## Setup
To set up the Robotmanager application, run
```
<python> -m covmatic_robotmanager.setup
```
This will create a desktop link and open in a text editor the file `.covmatic/robotmanager.conf` in your user home directory.
The configuration file should contain at least two parameter:
- *eva-ip*: this is the IP address of the Automata EVA robot;
- *eva-token*: this is the token used to authenticate with the EVA robot; create one token in the *Profile* Eva page.
Below an example of *robotmanager.conf* file:
```
eva-ip=192.168.1.1
eva-token=abcdefghijklmnrstuvwxyz
```

Please pay attention to any message regarding if the installed script are inside *PATH* directory;
if you see these messages than you will not be able to start the *server* and the *calibrator* using the short commands
below, but instead you should locate the script installation directory to launch them.

## Calibration

Robotmanager-server uses pre-calibrated positions in order to know where to position the robot.

All the position are stored in a *.covmatic/positions.json* file in your home directory.

The data organization has these objects:
- a main **HOME** position which is the general home where the robot should stay waiting for operations and where it will return after each operation.
- a **target robot** intended as a machine or entity to reach (e.g. a pipetting robot)
- a **slot** intended as a part of a *target robot* to be reached (e.g. SLOT 1 of a pipetting robot)

The calibration flow should be as follows:

1. First of all launch the calibrator in a command line with:
```
robotmanager-calibrator
```

2. Then calibrate the general *HOME* position:

1. when asked for target insert *HOME*
2. move manually the robot by pressing the *teach* button on the robot head
3. when ready, press *Enter* and then ***s*** to save the position as home
4. press _q_ to quit the program.

3. Calibrate the *HOME*, *DECK* and *HMAX* position for each target robot:
For proper movement each *target robot* needs these point calibrated in order:
1. **HOME** is the starting position that Eva will go to before entering the target robot.
Eva should move freely between *HOME*s positions.
2. **DECK** is a position where the gripper touches the deck of the target robot.
This value is used to calculate heights of labware.
3. **HMAX** is the maximum height reachable, calibrated with the Eva arm in the highest possibile position.

To calibrate a position in a target robot you need to follow this sequence for each position:
1. launch the *robotmanager-calibrator* script
2. insert the *target robot* name (e.g. OT1)
3. insert the *slot name* (e.g. HOME, DECK, HMAX, or anything used by protocols as SLOT1, SLOT2 etc.)
4. follow the instruction of the calibrator (it will ask you to move the robot manually if the position is not found
or to load a previously saved position)
5. make any necessary adjustment with the keyboard (see the screen instructions)
6. when ready you can test the saved position by pressing *w* and if necessary make any adjustment
7. when the position is good press *s* to save and *q* to quit

After defining the three basic positions (HOME, DECK, HMAX) for a target robot you can define any other position for a target robot.
The Eva will use this data to calculate and execute a safe trajectory to pick up or drop off a plate.

## Execution

Covmatic Robotmanager server will listen for request from ***covmatic-robotstation*** package running on each target robot.
When a *pick* and *drop* or a *transfer* action are queued for a same plate name then the EVA robot will execute the plate transfer.

In case of error (e.g. plate not grabbed) every action related to that plate will be aborted.

## Testing

The Covmatic Robotmanager comes with a handful of tests to check that the code is doing as expected.
It has been developed using a Test Driven Development approach.
To execute tests and coverage report just launch:
```
hatch run cov
```

Raw data

            {
    "_id": null,
    "home_page": "",
    "name": "covmatic-robotmanager",
    "maintainer": "",
    "docs_url": null,
    "requires_python": ">=3.7",
    "maintainer_email": "",
    "keywords": "automation,biology,lab,robotics",
    "author": "",
    "author_email": "Agostino Facotti <agostino.facotti@asst-bergamoest.it>",
    "download_url": "https://files.pythonhosted.org/packages/be/1a/f56aa46b6572a5b11f547aaaa1a909eee818112c5bae3ab6f86796689738/covmatic_robotmanager-0.0.6.tar.gz",
    "platform": null,
    "description": "# RobotManager\nManager code for EVA robot from Automata.\n\n## Warning\n**This is a development program and not ready for production-use.\nThis is part of a project in development.**\n\n## Table of Contents\n* [Introduction](#introduction)\n* [Installation](#installation)\n* [Setup](#setup)\n* [Calibration](#calibration)\n* [Execution](#execution)\n* [Testing](#testing)\n\n## Introduction\n\nThe *covmatic-robotmanager* comes with two scripts callable in a command shell:\n- *robotmanager-calibrator* is a helper program useful to save precise and repeatable calibrations.\n- *robotmanager-server* is the main server that listen for actions to do;\n\nSource code is on [ASST Bergamo Est repository](https://github.com/ASST-Bergamo-Est/covmatic-robotmanager)\n\n\n## Installation\n\nYou can [install the Covmatic LocalWebServer via `pip`](https://pypi.org/project/covmatic-robotmanager):\n```\n<python> -m pip install covmatic-robotmanager\n```\nWhere `<python>` should be changed for the Python instance you wish to install the Robotmanager onto. We will be following this convention for all the next instructions. \n\n## Setup\nTo set up the Robotmanager application, run\n```\n<python> -m covmatic_robotmanager.setup\n``` \nThis will create a desktop link and open in a text editor the file `.covmatic/robotmanager.conf` in your user home directory.\nThe configuration file should contain at least two parameter:\n- *eva-ip*: this is the IP address of the Automata EVA robot;\n- *eva-token*: this is the token used to authenticate with the EVA robot; create one token in the *Profile* Eva page.\nBelow an example of *robotmanager.conf* file:\n```\neva-ip=192.168.1.1\neva-token=abcdefghijklmnrstuvwxyz\n```\n\nPlease pay attention to any message regarding if the installed script are inside *PATH* directory; \nif you see these messages than you will not be able to start the *server* and the *calibrator* using the short commands\nbelow, but instead you should locate the script installation directory to launch them.\n\n## Calibration\n\nRobotmanager-server uses pre-calibrated positions in order to know where to position the robot.\n\nAll the position are stored in a *.covmatic/positions.json* file in your home directory.\n\nThe data organization has these objects:\n- a main **HOME** position which is the general home where the robot should stay waiting for operations and where it will return after each operation.\n- a **target robot** intended as a machine or entity to reach (e.g. a pipetting robot)\n- a **slot** intended as a part of a *target robot* to be reached (e.g. SLOT 1 of a pipetting robot)\n\nThe calibration flow should be as follows:\n\n1. First of all launch the calibrator in a command line with:\n   ```\n   robotmanager-calibrator\n   ```\n\n2. Then calibrate the general *HOME* position:\n\n   1. when asked for target insert *HOME*\n   2. move manually the robot by pressing the *teach* button on the robot head\n   3. when ready, press *Enter* and then ***s*** to save the position as home\n   4. press _q_ to quit the program.\n\n3. Calibrate the *HOME*, *DECK* and *HMAX* position for each target robot:\n   For proper movement each *target robot* needs these point calibrated in order:\n   1. **HOME** is the starting position that Eva will go to before entering the target robot.\n         Eva should move freely between *HOME*s positions.\n   2. **DECK** is a position where the gripper touches the deck of the target robot.\n      This value is used to calculate heights of labware.\n   3. **HMAX** is the maximum height reachable, calibrated with the Eva arm in the highest possibile position.\n   \n   To calibrate a position in a target robot you need to follow this sequence for each position:\n   1. launch the *robotmanager-calibrator* script\n   2. insert the *target robot* name (e.g. OT1)\n   3. insert the *slot name* (e.g. HOME, DECK, HMAX, or anything used by protocols as SLOT1, SLOT2 etc.)\n   4. follow the instruction of the calibrator (it will ask you to move the robot manually if the position is not found\n   or to load a previously saved position)\n   5. make any necessary adjustment with the keyboard (see the screen instructions)\n   6. when ready you can test the saved position by pressing *w* and if necessary make any adjustment\n   7. when the position is good press *s* to save and *q* to quit\n\nAfter defining the three basic positions (HOME, DECK, HMAX) for a target robot you can define any other position for a target robot.\nThe Eva will use this data to calculate and execute a safe trajectory to pick up or drop off a plate.\n\n## Execution\n\nCovmatic Robotmanager server will listen for request from ***covmatic-robotstation*** package running on each target robot.\nWhen a *pick* and *drop* or a *transfer* action are queued for a same plate name then the EVA robot will execute the plate transfer.\n\nIn case of error (e.g. plate not grabbed) every action related to that plate will be aborted.\n\n## Testing\n\nThe Covmatic Robotmanager comes with a handful of tests to check that the code is doing as expected. \nIt has been developed using a Test Driven Development approach.\nTo execute tests and coverage report just launch:\n```\nhatch run cov\n```\n",
    "bugtrack_url": null,
    "license": "",
    "summary": "Covmatic Robot Manager is a robotic arm manager for action requested by other robots",
    "version": "0.0.6",
    "project_urls": {
        "Homepage": "https://github.com/ASST-Bergamo-Est/covmatic-robotmanager",
        "Source": "https://github.com/ASST-Bergamo-Est/covmatic-robotmanager"
    },
    "split_keywords": [
        "automation",
        "biology",
        "lab",
        "robotics"
    ],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "5bdfffb68cc83af0798e4e257d334671c4f2f7c225db058455422bf024794fc8",
                "md5": "d3730c64761c59a70775f1611fbd0dea",
                "sha256": "a98f570f37f057ec4d663e9c878f1122558a4331ccfcf7a8c423b588e635ba9e"
            },
            "downloads": -1,
            "filename": "covmatic_robotmanager-0.0.6-py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "d3730c64761c59a70775f1611fbd0dea",
            "packagetype": "bdist_wheel",
            "python_version": "py3",
            "requires_python": ">=3.7",
            "size": 50263,
            "upload_time": "2023-08-09T12:33:17",
            "upload_time_iso_8601": "2023-08-09T12:33:17.195416Z",
            "url": "https://files.pythonhosted.org/packages/5b/df/ffb68cc83af0798e4e257d334671c4f2f7c225db058455422bf024794fc8/covmatic_robotmanager-0.0.6-py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "be1af56aa46b6572a5b11f547aaaa1a909eee818112c5bae3ab6f86796689738",
                "md5": "680368bc26307c52a1ee544b0429e2a1",
                "sha256": "bd85898baf26107df45734fb7f204203d6a2f575411e07ca675437b5a3216165"
            },
            "downloads": -1,
            "filename": "covmatic_robotmanager-0.0.6.tar.gz",
            "has_sig": false,
            "md5_digest": "680368bc26307c52a1ee544b0429e2a1",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": ">=3.7",
            "size": 48703,
            "upload_time": "2023-08-09T12:33:18",
            "upload_time_iso_8601": "2023-08-09T12:33:18.667424Z",
            "url": "https://files.pythonhosted.org/packages/be/1a/f56aa46b6572a5b11f547aaaa1a909eee818112c5bae3ab6f86796689738/covmatic_robotmanager-0.0.6.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2023-08-09 12:33:18",
    "github": true,
    "gitlab": false,
    "bitbucket": false,
    "codeberg": false,
    "github_user": "ASST-Bergamo-Est",
    "github_project": "covmatic-robotmanager",
    "travis_ci": false,
    "coveralls": false,
    "github_actions": true,
    "lcname": "covmatic-robotmanager"
}