MXCuBE-Web
MXCuBE-Web is the latest generation of the data acquisition software MXCuBE (Macromolecular Xtallography Customized Beamline Environment). The project started in 2005 at ESRF, and has since then been adopted by other institutes in Europe. In 2010, a collaboration agreement has been signed for the development of MXCuBE with the following partners:
MXCuBE-Web is developed as a web application and runs in any recent browser. The application is built using standard web technologies and does not require any third-party plugins to be installed in order to function. Being a web application, it is naturally divided into server and client parts. The communication between the client and server are made using HTTP/HTTPS and web-sockets. It is strongly recommended to use HTTPS, SSL/TLS encrypted HTTP. The traffic passes through the conventional HTTP/HTTPS ports, minimizing the need for special firewall or proxy settings to get the application to work.
The underlying beamline control layer
is implemented using the library mxcubecore
previously known as HardwareRepository.
The mxcubecore library is compatible with
both the MXCuBE-Web and the MXCuBE-Qt applications.
| Data collection | Sample grid |
|---|---|
 |
 |
Latest information about the MXCuBE project can be found on the MXCuBE project webpage.
Technologies in use
The backend is built on the Python Flask web framework, a library called SocketIO is further used to provide a bidirectional communication channel between backend and client. The backend exposes a REST API to the client.
The UI is implemented in HTML, CSS and JavaScript, mainly with the React, Redux, Boostrap, and FabricJS libraries.
Information for developers
Information for users
- User Manual MXCuBE Web
- Feature overview
- If you cite MXCuBE, please use the references:
Oscarsson, M. et al. 2019. “MXCuBE2: The Dawn of MXCuBE Collaboration.” Journal of Synchrotron Radiation 26 (Pt 2): 393–405.
Gabadinho, J. et al. (2010). MxCuBE: a synchrotron beamline control environment customized for macromolecular crystallography experiments. J. Synchrotron Rad. 17, 700-707
1 maintainer
Metadata
1 maintainer
Release files for mxcubeweb 4.784.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mxcubeweb-4.784.0.tar.gz | 90.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mxcubeweb-4.784.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 207.0 kB
Release files / mxcubeweb-4.784.0.tar.gz
| Download URL | mxcubeweb-4.784.0.tar.gz |
|---|---|
| Size | 90.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14915b709fa01375dd85722a955870908a02fa38a508bf9d254e6ac0046b9f30
|
|
BLAKE2b-256 checksum How to use checksums |
492170c86e51056d6256bb13d4f9c0d7cd4d6554eba7ba4259384e49a856fb14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.2 CPython/3.10.21 Linux/6.17.0-1022-azure
|
Release files / mxcubeweb-4.784.0-py3-none-any.whl
| Download URL | mxcubeweb-4.784.0-py3-none-any.whl |
|---|---|
| Size | 116.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c927c3630ef1954c523bce670cef2a69bb9f78f0b1a4686a468862b801c3e1b9
|
|
BLAKE2b-256 checksum How to use checksums |
30b9cd631e88e2c6f82dc6a180ab213a7863e0d1dae963eb288153757be6ac0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.2 CPython/3.10.21 Linux/6.17.0-1022-azure
|
Security for mxcubeweb 4.784.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
