marga_pulseq
Pulseq interpreter for vnegnev's MARcos fpGA (MARGA)
Usage:
TO INSTALL: this interpreter can be installed from PyPl with pip install marga_pulseq
To import the package: import marga_pulseq.interpreter
Create interpreter with marga_pulseq.interpreter.PSInterpreter. Run PSInterpreter.interpret() to get output array and dictionary. Specify a log path to log errors, warnings, and progress.
Arguments
rf_center (float): RF center (local oscillator frequency) in Hz.
rf_amp_max (float): Default 5e+3 -- System RF amplitude max in Hz.
grad_max (float): Default 1e+6 -- System gradient max in Hz/m.
gx_max (float): Default None -- System X-gradient max in Hz/m. If None, defaults to grad_max.
gy_max (float): Default None -- System Y-gradient max in Hz/m. If None, defaults to grad_max.
gz_max (float): Default None -- System Z-gradient max in Hz/m. If None, defaults to grad_max.
clk_t (float): Default 1/122.88 -- System clock period in us.
tx_t (float): Default 123/122.88 -- Transmit raster period in us. Will be overwritten if the PulSeq file includes a "tx_t" in the definitions.
grad_t (float): Default 1229/122.88 -- Gradient raster period in us. Will be overwritten if the PulSeq file includes a "grad_t" in the definitions.
tx_warmup (float): Default 500 -- Warmup time to turn on tx_gate before Tx events in us. Will be overwritten if the PulSeq file includes a "tx_warmup" in the definitions.
tx_zero_end (bool): Default True -- Force zero at the end of RF shapes
grad_zero_end (bool): Default True -- Force zero at the end of Gradient/Trap shapes
log_file (str): Default 'ps_interpreter' -- File (.log appended) to write run log into
log_level (int): Default 20 (INFO) -- Logger level, 0 for all, 20 to ignore debug.
Outputs
dict: tuple of numpy.ndarray time and update arrays, with variable name keys
dict: parameter dictionary containing raster times, readout numbers, and any file-defined variables
Metadata
Release files for marga-pulseq 0.2.2
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 | Actions |
|---|---|---|---|---|
| marga_pulseq-0.2.2.tar.gz | 12.9 kB | Without provenance | Details for marga_pulseq-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| marga_pulseq-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for marga_pulseq-0.2.2-py3-none-any.whl |
Total release size: 25.5 kB
Release files / marga_pulseq-0.2.2.tar.gz
| Download URL | marga_pulseq-0.2.2.tar.gz |
|---|---|
| Size | 12.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
154773fa311571f8178a45d65a294d7f18acb842a2f1626aeda10a2761c7632f
|
|
BLAKE2b-256 checksum How to use checksums |
6a9b338e9bd98d0715b14a9df3b4f159779c071079e60b339a3876229b09ec91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Release files / marga_pulseq-0.2.2-py3-none-any.whl
| Download URL | marga_pulseq-0.2.2-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f28417aeea08cb8e8c3d4fd4c9e6dd1b72c4754d19ba53ca52090d0cfcd08a6
|
|
BLAKE2b-256 checksum How to use checksums |
4fd331f9dc2bd9990bb70ed6d165290d3ee165023a99c1d0a2c0f7c59edbd1c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for marga-pulseq 0.2.2
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.