Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/labrad/pylabrad

python interface for labrad
https://github.com/labrad/pylabrad

Last synced: 2 months ago
JSON representation

python interface for labrad

Host: GitHub
URL: https://github.com/labrad/pylabrad
Owner: labrad
Created: 2013-07-16T22:08:52.000Z (almost 11 years ago)
Default Branch: master
Last Pushed: 2022-07-05T02:13:12.000Z (almost 2 years ago)
Last Synced: 2024-03-26T02:48:12.716Z (3 months ago)
Language: Python
Homepage:
Size: 7 MB
Stars: 49
Watchers: 32
Forks: 31
Open Issues: 78
Metadata Files:
- Readme: README.md

Lists

awesome_photonics - labrad

README

# pylabrad

![Python Version](https://img.shields.io/badge/python-3.7+-blue.svg)
[![PyPI](https://img.shields.io/pypi/v/pylabrad.svg)](https://pypi.python.org/pypi/pylabrad)

pylabrad is an interface to the LabRAD system in python with support for both clients and servers.
For general information about the LabRAD system/protocol see [the labrad repository](https://github.com/labrad/labrad) and associated [wiki](https://github.com/labrad/labrad/wiki).
For help getting started and understanding pylabrad take a look at the [wiki](https://github.com/labrad/pylabrad/wiki).

## Manager Compatibility

As of version 0.96.0, pylabrad is no longer compatible with the Delphi labrad manager available from Sourceforge.
Instead, use the new [scalabrad manager](https://github.com/labrad/scalabrad).
The user interface for the manager and node along with the registry editor and grapher is now [web-based (scalabrad-web)](https://github.com/labrad/scalabrad-web).

## Node Server

In addition to the basic labrad client/server support, this package also includes a tool called the "node" server in the `labrad.node` package.
This server just runs other labrad servers, allowing you to start and stop them by sending labrad requests to the node.
By running node servers on one or more machines connected to labrad, you can remotely control which labrad servers are running on those machines.
This can be very useful in distributed setups.
For more information, including required configuration in the LabRAD registry (to, e.g., define directories containing servers),
see the [node docstring](https://github.com/labrad/pylabrad/blob/master/labrad/node/__init__.py).
The node module is executable, so you should launch it with `python -m labrad.node`.
To see documentation of the available command-line parameters run `python -m labrad.node --help`.

## Contributing

For instructions on how to contribute to pylabrad, see [contributing.md](https://github.com/labrad/labrad/blob/master/contributing.md).

## Tests

New code should have tests, and changes to existing code should not break existing tests.
To run the test suite, you'll need to have `pytest` installed, then run `py.test` from the command line when in the pylabrad directory.

## Building and Updating

Packages for pylabrad are distributed through [PyPI](https://pypi.python.org/pypi/pylabrad).
The best way to install pylabrad is using pip: `pip install pylabrad`.
If installing using git and including in `PYTHONPATH`, note that versions 0.95.0 or later require the `futures` python package.

For contributors who need to build and upload new packages, do the following:

* **Tag the release.** Create a git tag with the version number, e.g. `git tag 1.0.0`.
You'll also want to push this tag to make it official: `git push origin 1.0.0`.
* **Build packages.** Make sure you have a clean local tree (no pending changes beyond the tag) and then build the packages: `source dist_build.sh`.
Packages will be built in the `dist/` directory and you should take a look to make sure the version number was found properly.
* **Upload to PyPI.** Run the provided script to upload packages: `source dist_upload.sh`.
This requires the `twine` package to ensure that the connection to PyPI is secure, so you may need to install it locally first: `pip install twine`.
Of course, you'll need a PyPI account that has permissions to update the pylabrad package.

## Migration note

This repo was moved from the martinisgroup organization.
To tell git to pull updates from the new location, you'll
want to update the 'origin' remote in your local repository.
Use `git remote -v` to see the names and urls for all remotes
you have defined, then `git remote set-url` to update the url,
changing the organization to labrad:

```
$ git remote -v
origin [email protected]:martinisgroup/pylabrad (fetch)
origin [email protected]:martinisgroup/pylabrad (push)

$ git remote set-url origin [email protected]:labrad/pylabrad
```

## Credits

```
unwrap.py from http://www.wave.co.nz/~glyn/
```