Skip to main content

mapyde v0.5.0

MaPyDe stands for MadGraph-Pythia-Delphes which is a utility that allows one to run all of the various HEP toolings or chain them together and perform a quick analysis with the results, such as running CERN ATLAS SimpleAnalysis or pyhf.


Mapyde logo
CI/CD CI - Test CI - Docker Docs
Docs doc Zenodo
Package PyPI - Downloads PyPI - Version PyPI platforms Conda-Forge
Meta GitHub - Discussion GitHub - Issue License - Apache 2.0

Docker Images

Docker images are made available in our container registry.

docker pull ghcr.io/scipp-atlas/mapyde/madgraph
docker pull ghcr.io/scipp-atlas/mapyde/delphes
docker pull ghcr.io/scipp-atlas/mapyde/pyplotting

If you want to run on a machine with an NVidia GPU and use it for limit setting with pyhf, then there's a container for that too:

docker pull ghcr.io/scipp-atlas/mario-mapyde/pyplotting-cuda

Running

Everyone is centralized around the concept of providing a user configuration file that references a template. By default, defaults.toml is used (if not specified). These configuration files significantly control how to run or execute the various steps in the chain of mapyde. Use the command line interface to get started:

# display the help
mapyde --help

# open Textual TUI
mapyde --tui

# display the prefix path for data cards shipped with mapyde
mapyde --prefix cards

# parse and display the config
mapyde config parse user.toml

# run all steps
maypde run all user.toml

# run only madgraph
mapyde run madgraph user.toml

# display the help for running
mapyde run --help

Configuration Details

There are a lot of different configuration options one can specify. For right now, the user is asked to look at defaults.toml, run mapyde config parse user.toml, open a discussion, or look at the source code.

MadGraph

Produces a hepmc file. You can:

  • specify process, param, and run cards
    • define particle masses in config file
    • define additional kinematic cuts to apply at parton level
  • specify pythia card
  • define center of mass energy

Delphes

Run a parameterized detector simulation, outputting a ROOT file. You can:

  • specify Delphes card

Analysis

Analyze the Delphes output, which could be user-provided analysis code. There are some scripts already provided for you:

  • scripts/Delphes2SA.py will make an ntuple that can be parsed by SimpleAnalysis for limit setting.
  • scripts/SimpleAna.py will make a generic "flat" ntuple in a ROOT file.
  • scripts/muscan.py will use pyhf to perform a mu-scan and compute upper-limits for a public likelihood injected with results from SimpleAnalysis.

Metadata

Release files for mapyde 0.5.0

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

Source distribution (sdist)

Source distribution for mapyde 0.5.0
File Size Uploaded Provenance
mapyde-0.5.0.tar.gz 294.0 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 687.5 kB

Release files / mapyde-0.5.0.tar.gz

Download URL mapyde-0.5.0.tar.gz
Size 294.0 kB
Tags Source
SHA-256 checksum
How to use checksums
61075fc0cb8336ee1334372270baa56634ad7e13a075c7397d7511f370959201
BLAKE2b-256 checksum
How to use checksums
b6a3bfcb5ac3c0c18e7ec98b114f9c36325a8af52a50be2a7759d0fb075dd764
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/4.0.1 CPython/3.11.4

Release files / mapyde-0.5.0-py3-none-any.whl

Download URL mapyde-0.5.0-py3-none-any.whl
Size 393.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dd362aa313e5885f6d1b5bcca0e69eba426eb9ca81bd81c2d69ab1d05af476a4
BLAKE2b-256 checksum
How to use checksums
a22b0fc702fa152d513c3fa6a6736da55d192f1c8f95efd0f7ccb86cc79e39d2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/4.0.1 CPython/3.11.4

Security for mapyde 0.5.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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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