np_workflows
This package contains all the Python code required to run Mindscope Neuropixels experiments.
Experiment workflows and related tasks are coordinated by Jupyter notebooks maintained here: https://github.com/AllenInstitute/np_notebooks
Running the notebooks requires a Python environment with:
- Python >= 3.11
- np_workflows
- Jupyter / JupyterLab
git clone https://github.com/AllenInstitute/np_notebooks
conda create -n workflows python=3.11
pip install np_workflows
pip install jupyterlab
Keep the np_workflows package up-to-date by running pip install np_workflows -U before each use
To develop this package git clone then pdm install
NP. rig setup
.venv is currently used, with PDM to update packages before each experiment:
- install JupyterLab desktop (Win 64-bit)
- clone
np_notebooks(notnp_workflows)cd c:\Users\svc_neuropix\Documents\github & git clone https://github.com/AllenInstitute/np_notebooks - find the path to python.exe 3.11.*, or install it manually
- create a new venv in the
np_notebooksdir:cd np_notebooks & path-to-python.exe -m venv .venv - activate venv:
.venv\scripts\activate(terminal should now report(np_notebooks-3.11)) - install PDM in venv:
path-to-python.exe -m pip install pdm - install
np_notebooksrequirements:pdm install - in JupyterLab, set the default to Python environment to use
c:\Users\svc_neuropix\Documents\github\np_notebooks\.venv\scripts\python.exe - open up any workflow in the
np_notebooksdir and check that the initial cell with imports works
Metadata
Release files for np-workflows 1.6.103
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 | |
|---|---|---|---|---|
| np_workflows-1.6.103.tar.gz | 46.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| np_workflows-1.6.103-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 117.9 kB
Release files / np_workflows-1.6.103.tar.gz
| Download URL | np_workflows-1.6.103.tar.gz |
|---|---|
| Size | 46.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9627812c6bdd9018244081d93400feea12074f449410ad1a74fd3338d5829304
|
|
BLAKE2b-256 checksum How to use checksums |
96ef49e2f1cc7f26c3d94b9ad8a64d55011db5e733a33ce22daf137a8a458f44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / np_workflows-1.6.103-py3-none-any.whl
| Download URL | np_workflows-1.6.103-py3-none-any.whl |
|---|---|
| Size | 71.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3cdcc863d454132910b35a847cbea379282b235f121a85ee391710c53bd5fc09
|
|
BLAKE2b-256 checksum How to use checksums |
a95abffa1a10a9c197b890b54361aa734049ac412b4311ae8ce368c0fb5e3913
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for np-workflows 1.6.103
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.