NQRduck Module: Spectrometer Simulator
This module is a part of the NQRduck project. It is a submodule of the spectrometer module for the NQRduck project. It is designed to be used with the NQRduck project.
The module is used to simulate magnetic resonance experiments. It is based on the Bloch simulator by C. Graf [2].
Installation
Requirements
The requirements for the module are handled by the pyproject.toml file. The user needs to install the NQRduck core. The simulator module uses the nqr-blochsimulator project for simulation of the bloch equation. This module is automatically installed when installing the simulator module.
Setup
To install the module you need the NQRduck core. You can find the installation instructions for the NQRduck core here.
Ideally you should install the module in a virtual environment. You can create a virtual environment by running the following command in the terminal:
python -m venv nqrduck
You can install this module and the dependencies by running the following command in the terminal after cloning the repository and navigating to the root directory of the project:
pip install .
Alternatively you can install the module via PyPI:
pip install nqrduck-spectrometer-simulator
Usage
The pulse sequence is graphically programmed using the nqrduck-pulseprogrammer within the NQRduck program under the 'Spectrometer' tab.
Notes
The simulator is only usable for Nuclear Quadrupole Resonance (NQR) experiments. It is not intended for Nuclear Magnetic Resonance (NMR) experiments at the moment. This is because the signal equation is different for NMR and NQR. The current implementation does not include the (permanent) $B_0$ field or the z-gradient. I hope to implement NMR simulations in the future.
Additionally this simulator has only been verified for one sample (BiPh3 at 300K). The simulator should therefore be used with caution and the results should be verified with a real spectrometer.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for nqrduck-spectrometer-simulator 0.0.6
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 | |
|---|---|---|---|---|
| nqrduck_spectrometer_simulator-0.0.6.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nqrduck_spectrometer_simulator-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.3 kB
Release files / nqrduck_spectrometer_simulator-0.0.6.tar.gz
| Download URL | nqrduck_spectrometer_simulator-0.0.6.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b633fb75e29be0ff5ec9975230350def4749edca3ccbcfc08ff9c40b0a081b84
|
|
BLAKE2b-256 checksum How to use checksums |
63736c8bf790a8579a1eb672eabea62c1a59a09a11816463945615b972cce6a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Release files / nqrduck_spectrometer_simulator-0.0.6-py3-none-any.whl
| Download URL | nqrduck_spectrometer_simulator-0.0.6-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63ece004e5ced5de749448500249029562afa8828deb9740f39bfea6182ebb91
|
|
BLAKE2b-256 checksum How to use checksums |
8818f2906ca2047868e502e8a1c808401a4fd38a7f6b1e3ab8d0222901997947
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Security for nqrduck-spectrometer-simulator 0.0.6
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.