Papers › Digging Into MUD With Python: mudpy, bdata, and bfit

Digging Into MUD With Python: mudpy, bdata, and bfit

22 Apr 2020arXiv:2004.10395links table onlyarchive 2025-07-28

Derek Fujimoto

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Used to store the results of μSR measurements at TRIUMF, the Muon Data (MUD) file format serves as a useful and flexible scheme that is both lightweight and self-describing. The application programming interface (API) for these files is written in C and FORTRAN, languages not known for their ease of use. In contrast, Python is a language which emphasizes rapid prototyping and readability. This work describes three Python 3 packages to interface with MUD files and analyze their contents: mudpy, bdata, and bfit. The first enables easy access to the contents of any MUD file. The latter two are implemented specifically for the implanted-ion β-detected NMR (β-NMR) experiment at TRIUMF. These tools provide both an API and graphical user interface (GUI) to help users extract and fit β-NMR data.

PaperPDFCode

Code

dfujim/bdata mentioned on GitHub report
dfujim/bfit mentioned on GitHub report
dfujim/mudpy mentioned on GitHub report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections