Siemens Access-i Interface library
Library for Siemens Access-i MR Scanner Interface to integrate and control the MR Scanner. Based on Version 1.1.2 for NX (Access-i Developer Guide)
Install
This is the easiest way to use the install the library, if you do not need to modify it.
pip install accessi
Siemens Documentation
The library is based on this document: Access-i Dev Guide NX V1.1.2
Usage guide
A sample test suite (tests.py) has been created which demonstrates basic Access-i usage.
The tests.py requires Access-i simulator to be running on the background, on the same local computer.
The tests.py demonstrates most of the implemented methods, as well as receiving images over websocket.
Usage examples
Here are some projects which have used this library:
Access-i Licence for real MR at TechMed (Also works with simulator)
name="UTwente",
start_date="20231102",
warn_date="20251002",
expire_date="20251102",
system_id="152379",
hash="uTwo2ohlQvMNHhfrzceCRzfRSLYDAw7zqojGjlP%2BCEmqPq1IxUoyx5hOGYbiO%2FEIyiaA4oFHFB2fwTctDbRWew%3D%3D",
informal_name="This name shows up on MR computer"
Connection and IP Addresses
The Access-i in TechMed is running on this IP address:
10.89.184.9
Access-i Version: v1
Simulator IP:
127.0.0.1
Access-i Version: v2
In order to connect, the client must have the following networking settings:
Client IP: 192.168.182.20 (Maybe something else works too, have not tried)
Subnet: 255.255.255.0
Gateway: 192.168.182.1
DNS1: 192.168.182.1
Multiple network adapters on the same computer
To be able to use both, Access-i and WAN (external interent) at the same time, some configurations are necessary. These are only compatible with Windows for now.
Find out what is the interface number, which is connected to Access-i:
route print
Using the interface number, create a route:
route add 10.89.184.0 mask 255.255.255.0 192.168.182.20 if 8 -p
Here if 8 is the interface number in this particular case, -p means persistant so it will stay after reboot.
Collaborating
The majority of Access-i functionality is not yet implemented here, if you need more functionality, any additions are accepted.
Metadata
Release files for accessi 0.0.8
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 | |
|---|---|---|---|---|
| accessi-0.0.8.tar.gz | 11.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| accessi-0.0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.3 kB
Release files / accessi-0.0.8.tar.gz
| Download URL | accessi-0.0.8.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3f4b99e93d69f7d51403bb72a1a6ed10c03569b894d4e8df9169dfa9510749e
|
|
BLAKE2b-256 checksum How to use checksums |
6e5baf6882bf995ae46975a2ac839aea3ed38a12b2183bbaea3344eac6243933
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / accessi-0.0.8-py3-none-any.whl
| Download URL | accessi-0.0.8-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c98c0069e00275b113e6477a338baf56a0b09369903fab77e9dd410f88741f5
|
|
BLAKE2b-256 checksum How to use checksums |
2ef86ca727dd5ddce3b37e2917453ffdbd20604e64237a7bfb838a3d82d99026
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for accessi 0.0.8
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.