Peak finder
You can use this notebook to find peaks in your data.
Getting everything set up
uv
If you downloaded or cloned this repository, simply run:
uv sync
To set up your virtual environment. You can also add the dependencies listed in pyproject.toml to an existing project's environment.
Run the notebook from Visual Studio Code by selecting the peak-finder .venv as the environment for the kernel or run Jupyter Lab with
uv run jupyter-lab peak-finder.ipynb
uvx
If you just have a copy of the notebook and want to run Jupyter Lab with the required dependencies but without installing anything run
uvx --from jupyterlab --with ipympl,matplotlib,numpy,pandas,scipy jupyter-lab peak-finder.ipynb
Conda (Anaconda or Miniconda)
To create a conda environment with Jupyter Lab and all dependencies, run:
$ conda env create -f environment.yml
Run Jupyter Lab with
$ conda activate peak-finder
$ jupyter lab peak-finder.ipynb
and load the notebook, or run the notebook from e.g. Visual Studio Code while selecting the peak-finder conda environment.
Running the notebook
At the bottom of the notebook you will find this line:
find_peaks("example-datafile.csv")
Change example-datafile.csv to point at your data file or just run the notebook with the example data. You should see something like this:
You can zoom into parts of your dataset and tweak the settings until you're satisfied with the detected peaks.
Metadata
Release files for peak-finder-notebook 1.1.0
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 | |
|---|---|---|---|---|
| peak_finder_notebook-1.1.0.tar.gz | 62.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| peak_finder_notebook-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 126.0 kB
Release files / peak_finder_notebook-1.1.0.tar.gz
| Download URL | peak_finder_notebook-1.1.0.tar.gz |
|---|---|
| Size | 62.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
183ff3a503e744d8933672858411a378ff4014d69756929f447ad5900c22069e
|
|
BLAKE2b-256 checksum How to use checksums |
5b274cd62afa385014977c3613e6e33b7cb35b8f49d06c519295c58046e601ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.12 {"installer":{"name":"uv","version":"0.10.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / peak_finder_notebook-1.1.0-py3-none-any.whl
| Download URL | peak_finder_notebook-1.1.0-py3-none-any.whl |
|---|---|
| Size | 63.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b54ea96748c80b986b4ecb5a48ffe91b057a155b862af429a7ab48b0db9e37c9
|
|
BLAKE2b-256 checksum How to use checksums |
4c5633d4be3260ba92ab94e5c6a2705424018090531d55c303258b72dc90410c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.12 {"installer":{"name":"uv","version":"0.10.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for peak-finder-notebook 1.1.0
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.