Murfey
A transporter for data from Diamond eBIC microscope and detector machines onto the Diamond network.
Who is Murfey?
Murfey, the package, is named after Eliza Murfey, the inventor:
Focusing on the mechanics of the railroad, inventor Eliza Murfey created devices designed to improve the bearings on rail wheels. With sixteen patents for her lubrication system, it was Murfey who designed the packings that would lubricate the axles with oil, aiding in the reduction of derailments caused by seized axles and bearings.
How do I set up a development environment?
We suggest you start with your favourite virtual environment (mamba/conda/python virtualenv/...), then install using the following command.
$ git clone git@github.com:DiamondLightSource/python-murfey.git
$ cd python-murfey
$ pip install -e .[server,developer]
The packages included under the [developer] installation key contain some helpful tools to aid you with developing Murfey further:
bump-my-version- Simplifies version control.ipykernel- Enables interactive code development via Jupyter Notebooks.pre-commit- Allows for the installation and running of hooks to help with linting, formatting, and type checking your code.pytest- Used in conjunction with test functions to evaluate the reliability of your code.
Instructions for setting up the database for Murfey to register files to can be found here.
Finally, you may want to set up an ISPyB mock database server and a Zocalo development environment. The instructions for this are out of scope here.
You can then start the Murfey server with
$ murfey.server
and connect the client with
$ murfey.instrument_server --port 8000
You can also install a client on a remote machine. This machine only needs to have a minimum Python installation and curl. Open the murfey server website in a browser on the client, and navigate to the bootstrap page. Then copy the displayed commands into a command line terminal.
Release files for murfey 0.27.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| murfey-0.27.4.tar.gz | 378.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| murfey-0.27.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 841.3 kB
Release files / murfey-0.27.4.tar.gz
| Download URL | murfey-0.27.4.tar.gz |
|---|---|
| Size | 378.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e696a1ab502df700e03b20912aadd45ca2c3c15ae86ddc7a5e08d8b87aab9266
|
|
BLAKE2b-256 checksum How to use checksums |
e27b71777b3fd8f041b8d5f8333fb6581ade8201f1eae0330d9c55596129898e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / murfey-0.27.4-py3-none-any.whl
| Download URL | murfey-0.27.4-py3-none-any.whl |
|---|---|
| Size | 462.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fcb2f4c03adb648c9e82725bb79bca983387f8b624cbe0f9f8f08239c0867efc
|
|
BLAKE2b-256 checksum How to use checksums |
23e4a78c08829a27c34a7043e5eec467db45f93e4bd9e7397b8228887f21ae35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log
