PyrootCK
Improving PyROOT for better productivity.
Collection of utilities are organized into subpackages::
-
mathutils:asymvar: class for variable with asymmetric-error, inspired fromuncertainties.ufloat.Eff,EffU,EffU_unguard: functions to compute efficiencies with Clopper-Pearson uncertainty.weighted_average,weighted_harmonic_average: when a simple average is not enough.combine_fully_correlated,combine_uncorrelated,combine_BLUE: for combining multiple observables with uncertainty into one, given choices of correlation. For BLUE (Best Linear Unbiased Estimator), see Valassi, 2013.
-
iouilsimport_treeto quickly loadTTreefrom (multiple)TFileoverloaded for different source types (local, ganga, eos, xrootd, ...).
-
tmvautilsTMVA_Adapterto help setupTMVA.Readervariables, and returnTTreeof mva-response weights.
As well as miscellaneous monkey-patching on ROOT and uncertainties
for more methods::
-
ROOT:- Misc conversion to/from
ROOT(TH,TGraph,RooWorkspace,RooFitResult,...) andpandas(Series,DataFrame). TFile.slice_treeto extractTTreeinto smaller one.TTree.dropto make index-unique TTree.TH1.vlookup,TH2.vlookup: like in Microsoft Excel, to retrive value in a bin given point(s) on the axis.TMultiGraph.brazillian: for the upper limits plot.
- Misc conversion to/from
-
uncertainties:- class
var, based on ufloat but ready-made for statistical (Poisson) error. - Additional methods on
ufloat:rerr,upperlim,low,high,interval,rounding_PDG - More methods involving error tag:
tags,get_error,get_rerr
- class
See the docstring from module index for more details.
Installation
It's available on pip: pip install pyrootck
Dependency: uncertainties, pandas, root_numpy, pyroot_zen, PythonCK
Disclaimer
This packacge was written and used during my PhD in 2013-2017 at EPFL (Lausanne) and LHCb collaboration (CERN), for the work in Z->tau tau cross-section measurement and H->mu tau searches at LHCb (8TeV).
I hope it can be of a good use for future analysis...
Metadata
Release files for PyrootCK 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 | Provenance | Actions |
|---|---|---|---|---|
| PyrootCK-1.0.1.tar.gz | 1.2 MB | Without provenance | Details for PyrootCK-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| PyrootCK-1.0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for PyrootCK-1.0.1-py2.py3-none-any.whl |
Total release size: 1.3 MB
Release files / PyrootCK-1.0.1.tar.gz
| Download URL | PyrootCK-1.0.1.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
81788497961a98c24722bd93ab3e152ab26d104e7117b9104205fa228b34a5d9
|
|
BLAKE2b-256 checksum How to use checksums |
49ba04f51a37be7edd1d8fc8b022e868abbb24069874f6fe413ac0b3da79ab45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / PyrootCK-1.0.1-py2.py3-none-any.whl
| Download URL | PyrootCK-1.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 54.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4c11c0e4ad15a19516ab94d2cb0e29b02e610e437d34531b4c2e793ad4efad6d
|
|
BLAKE2b-256 checksum How to use checksums |
034ad48b23be0eb104e49e16049bae027639fb6f728bb304ee3e75bc83ab623a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for PyrootCK 1.0.1
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.