MiLoMerge
A package to merge bins together in such a way that the separability between distributions is minimally lossless. The ROC and LOC curves defined in the paper above are also included as functions in this package. It is fully Pythonic, with full interoperability with Numpy.
This package is derived from the findings of Maximizing Returns: Optimizing Experimental Observables at the LHC, which should be cited should the package be used.
Installation
Through pip
MiLoMerge is available in pip, and soon to conda, and can be installed as below:
pip install MiLoMerge
Manual Installation
Download the .tar.gz installation available at https://spin.pha.jhu.edu/ and run the following command in the MiLoMerge directory:
pip install .
Getting Started
To use MiLoMerge, import the package within your file, and generate distributions to merge. The documentation, alongside useful examples and tutorials, is available at the homepage.
Metadata
Release files for MiLoMerge 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| milomerge-1.0.1.tar.gz | 22.4 kB | Details |
Release files / milomerge-1.0.1.tar.gz
| Download URL | milomerge-1.0.1.tar.gz |
|---|---|
| Size | 22.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60b25bdb6f9703059b8608f2958aa36e97d5f4e0ff6c19b29f37bb27ed179f08
|
|
BLAKE2b-256 checksum How to use checksums |
6b1147c6a4e0c48a24f33fd9222a847f5584c69dc278950e35e6f93f57e01c5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 22, 2026.
Transparency log