Skip to main content

AnalysisToolbox

Maintenance DOI

The AnalysisToolbox set of Python tools for statistically analyzing correlated data. This includes aspects of lattice QCD applications related to QCD phenomenology.

We advertise briefly here some features of the AnalysisToolbox:

  • General mathematics: Numerical differentiation, convenience wrappers for SciPy numerical integration and solving IVPs.
  • General statistics: Jackknife, bootstrap, Gaussian bootstrap, error propagation, various information criteria, Bayesian model averaging, estimation of integrated autocorrelation time, error ellipses, Kolmogorov-Smirnov tests, and curve fitting with and without Bayesian priors. We stress that our math and statistics methods are generally useful, independent of physics contexts.
  • General physics: Unit conversions, critical exponents and temperatures for various universality classes, physical constants, framework for spin models.
  • QCD physics: Hadron resonance gas model, ideal fermion gas, HotQCD equation of state, and the QCD beta function. These methods are useful for QCD phenomenology, independent of lattice contexts.
  • Lattice QCD: Continuum-limit extrapolation, SU(3) gauge fields, reading in gauge fields, and the static quark-antiquark potential. These methods rather target lattice QCD.

In any of the above cases, after installing the AnalysisToolbox, you can easily incorporate its features in your own Python scripts like any other library. Some simple examples are in the tutorial. A realistic use-case that weaves the AnalysisToolbox into a lattice QCD workflow can be found in this data publication. More information can be found in the documentation.

To use the AnalysisToolbox, make sure you have Python 3.9+. You should then be able to conveniently install it using

pip install latqcdtools

If you would like alternative ways to set up the AnalysisToolbox, please see the documentation.

Besides this basic install, there is a latexify() command you can use when plotting to make your plot font match typical LaTeX documents. In order for this command to work, you need to have LaTeX installed on your system. The easiest is to install texlive-full, but if that is not possible, it may be enough to install texlive-mathscience in addition to the basic stuff.

Getting started and documentation

To acquaint yourself with the AnalysisToolbox, you can start by having a look at the tutorial, which walks through some scripts in the examples directory. You can also look at some of the scripts in the applications and testing directories.

To learn about the code in more detail, especially learning how to contribute, please have a look the documentation.

Getting help and bug reports

Open an issue, if...

  • you have troubles running the code.
  • you have questions on how to implement your own routine.
  • you have found a bug.
  • you have a feature request.

If none of the above cases apply, you may also send an email to clarke(dot)davida(at)gmail(dot)com.

Contributors

D. A. Clarke, L. Altenkort, H. Dick, K. Ebira, J. Goswami, O. Kaczmarek, G. Liu, L. Mazur, H. Sandmeyer, M. Sarkar, C. Schmidt, H.-T. Shu, T. Ueding

Crediting AnalysisToolbox

If you used this code in your research, your teaching, or found it generally useful, please help us out by citing

@inproceedings{Altenkort:2023xxi,
    author = "Altenkort, Luis and Clarke, David Anthony and Goswami, Jishnu and Sandmeyer, Hauke",
    title = "{Streamlined data analysis in Python}",
    eprint = "2308.06652",
    archivePrefix = "arXiv",
    primaryClass = "hep-lat",
    month = "8",
    year = "2023"
}

Acknowledgments

  • We acknowledge support by the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation) through the CRC-TR 211 'Strong-interaction matter under extreme conditions'– project number 315477589 – TRR 211.
  • This work was partly performed in the framework of the PUNCH4NFDI consortium supported by DFG fund "NFDI 39/1", Proj.No. 460248186 (PUNCH4NFDI).
  • DAC acknowledges helpful discussions with C. DeTar, X.-Y. Jin, S. Lahert, G. P. LePage, and C. Rohde.

Metadata

Release files for latqcdtools 1.3.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for latqcdtools 1.3.4
File Size Uploaded
latqcdtools-1.3.4.tar.gz 117.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for latqcdtools 1.3.4
File Interpreter ABI Platform
latqcdtools-1.3.4-py3-none-any.whl Python 3 none any Details

Total release size: 254.1 kB

Release files / latqcdtools-1.3.4.tar.gz

Download URL latqcdtools-1.3.4.tar.gz
Size 117.9 kB
Tags Source
SHA-256 checksum
How to use checksums
2d23c13dfbcdb2ebbb113858265de13b0278b6d3f8f0ac2645f79f93ebebfcbc
BLAKE2b-256 checksum
How to use checksums
1e0ae124aa705ec86ebfcc12a56f7604833f989abd7baa5792fabb3a484ba559
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.5

Release files / latqcdtools-1.3.4-py3-none-any.whl

Download URL latqcdtools-1.3.4-py3-none-any.whl
Size 136.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
41e2ea30d8670837036ec2424a49bda83be6b3916594bd1bc32c81f27088160a
BLAKE2b-256 checksum
How to use checksums
2e5c6cd25c6d027ddc95136aca11535d43ee572eb599be1c349d9331cc00138f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.5

Release history Release notifications | RSS feed

This release

1.3.4 This release

2 release files

1.3.3

2 release files

1.3.2

2 release files

1.3.1

2 release files

1.3.0

2 release files

1.2.4

2 release files

1.2.3

2 release files

1.2.2

2 release files

1.2.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page