Welcome to the CNSR Lab Code Base
This repository provides Jupyter notebook templates required to perform analysis on the data created during experiments at the CNSR core facility of Heidelberg University.
Installation
The recommended installation for the cnsr Python package is via Conda:
conda install -c conda-forge cnsr
Usage
After installing cnsr, start JupyterLab either via the command line or via the Jupyter App launcher UI on Windows:
jupyter lab
In the JupyterLab launcher, you will see a shortcut for each analysis task at CNSR. Clicking on this notebook will create a copy of the respective analysis notebook in the current working directory.
Acknowledgments
The conda packaging of this repository was implemented by the Scientific Software Center at Heidelberg University.
Release files for cnsr 0.0.3
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 |
|---|---|---|---|---|
| cnsr-0.0.3.tar.gz | 102.3 kB | Without provenance | Details for cnsr-0.0.3.tar.gz |
Release files / cnsr-0.0.3.tar.gz
| Download URL | cnsr-0.0.3.tar.gz |
|---|---|
| Size | 102.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7adb17787dc6e8596f242a475fdd401e108e4902bc825ec687650aba6917f18
|
|
BLAKE2b-256 checksum How to use checksums |
c5deb0ef57d0d4d82e7d212391e4ae222e67e5bee2367457016ec75806d087c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for cnsr 0.0.3
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.
