mat_ret
Unified retrieval and property mapping for materials databases, with a PyQt6 GUI for materials search, structure viewing, and XRD generation.
Supported Databases
- Materials Project
- JARVIS
- AFLOW
- Alexandria
- Materials Cloud
- MPDS
- OQMD
- OPTIMADE providers (registry search)
Installation
Install as package:
pip install .
Install editable for development:
pip install -e .
Install editable with test dependencies:
pip install -e ".[dev]"
Quick Start
- Configure API keys (
MP_API_KEY,MPDS_API_KEY) via environment variables orconfig.py. - Run examples:
python example_fetch.py
python example_single_fetch.py
- Use the Python API:
from mat_ret.api import fetch_all_databases
results = fetch_all_databases(
formula="MgO",
limit_per_database=3,
mp_api_key="YOUR_MP_KEY",
mpds_api_key="YOUR_MPDS_KEY",
)
print(results["materials_project"][0])
Unified Retrieval & Filtering
fetch_all_databases is a single entry point across every supported database.
It accepts a formula or an element system, a database subset, a shared
SearchFilters object (applied server-side where supported, post-fetch
otherwise), parallel fetching, opt-out CIF writing, a retrieve_all
mode (each database is queried up to a safety cap rather than a fixed limit), and
optional cross-database de-duplication.
from mat_ret.api import fetch_all_databases
from mat_ret.search import SearchFilters
filters = SearchFilters(
band_gap_min=1.0, band_gap_max=3.0,
is_stable=True,
include_elements=["O"], # must contain oxygen
exclude_elements=["Pb"], # must not contain lead
crystal_system="cubic",
)
# Element-system search across a subset of databases, in parallel, merged.
unified = fetch_all_databases(
elements=["Fe", "O"],
databases=["materials_project", "jarvis", "oqmd"],
filters=filters,
parallel=True,
save_cif=False,
merge_duplicates=True, # returns a unified, de-duplicated envelope
mp_api_key="YOUR_MP_KEY",
)
for material in unified["materials"]:
print(material["formula"], material["source_databases"])
print(unified["metadata"]) # counts, databases queried, dedup totals
# retrieve_all=True fetches as many matches as each database returns (slower).
everything = fetch_all_databases(formula="MgO", retrieve_all=True)
Every result dict carries unified keys including formula, elements,
num_elements, num_sites, and source_database, so filters and storage
queries work consistently across all databases.
Direct Client Usage
You can call specific clients from mat_ret.databases directly:
from mat_ret.databases import MaterialsProjectClient
client = MaterialsProjectClient(api_key="YOUR_MP_KEY")
results = client.get_structures("MgO", limit=1)
if results:
entry = results[0]
print(entry["material_id"])
OPTIMADE Search
When OPTIMADE is selected in the GUI, providers are shown as a tree. Select the parent to toggle all providers or select individual providers. The search filter applies to each provider, and limit is applied per provider.
Running in a Virtual Environment
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
GUI
mat_ret includes a PyQt6 desktop GUI.
Launch GUI
mat-ret-gui
# or
python -m mat_ret.gui
GUI Features
- Database selection and API key controls
- OPTIMADE provider tree with per-provider toggles
- Formula search (e.g.,
Fe2O3,LiFePO4) across selected databases - Element-set search via periodic-table picker icon next to the search box
- Chemsys text format:
Fe-O,Li-Fe-O - Element mode uses contains-all semantics
- Unsupported providers/databases are skipped with explicit status messages (e.g., OQMD)
- Chemsys text format:
- Search filters (electronic, energetic, structural, composition, mechanical, magnetic) applied across all databases, including must-contain / exclude element filters
- "Retrieve all matches" toggle to fetch as many results as each database returns (up to a safety cap) instead of a fixed per-database limit
- Incremental results display (each database appears as it completes) with an optional Merge duplicates across databases view
- Results table and JSON views
- Structure viewer with CIF export
- File menu exports (JSON/CSV)
- Stored-materials browser with formula / source / crystal-system / band-gap / element / energy-above-hull filters (SQLite, MongoDB, or file backends)
- Tools menu:
- XRD Generator
XRD Generator
Open Tools -> XRD Generator... in the GUI.
Capabilities:
- Input sources:
- Any CIF file from disk
- Currently selected structure from the main results window
- Radiation presets from pymatgen (including
CuKa,CuKa1,CuKa2, etc.) - Optional custom wavelength (Angstrom)
- Scan controls:
2theta min,2theta max,2theta step - Profile controls:
StickGaussianLorentzianPseudo-Voigt(witheta)
- Peak broadening width control (
FWHM, degrees in 2theta) - Peak finder controls using SciPy:
- minimum height
- prominence
- minimum distance
- minimum width
- theoretical peak match tolerance
- Interactive plot view + peak table
- Exports:
- plot (
PNG,SVG,PDF) - profile/stick CSV
- peaks CSV
- plot (
Defaults:
- Radiation:
CuKa(1.54184 A) - Scan range:
5to90deg (2theta), step0.02 - Profile:
Pseudo-Voigt - FWHM:
0.15deg - Eta:
0.5
Detailed XRD notes are in doc/XRD_GENERATOR_GUIDE.md.
XRD API
from mat_ret import XRDConfig, generate_xrd_pattern_from_cif
cfg = XRDConfig(
radiation="CuKa",
two_theta_min=5.0,
two_theta_max=90.0,
two_theta_step=0.02,
profile="pseudo_voigt",
fwhm=0.15,
)
result = generate_xrd_pattern_from_cif("example.cif", config=cfg)
print(result.wavelength, len(result.peaks))
Tests
Run XRD tests:
pytest tests/test_xrd.py
Run all tests:
pytest
Project Structure
mat_ret/
├── src/mat_ret/
│ ├── api.py
│ ├── databases.py
│ ├── property_mapping.py
│ ├── xrd.py
│ └── gui/
│ ├── main.py
│ ├── main_window.py
│ ├── workers.py
│ ├── utils.py
│ └── widgets/
│ ├── database_selector.py
│ ├── results_view.py
│ ├── structure_viewer.py
│ └── xrd_generator_window.py
├── tests/
│ └── test_xrd.py
├── doc/
│ ├── PROPERTY_MAPPING_GUIDE.md
│ └── XRD_GENERATOR_GUIDE.md
├── README.md
├── pyproject.toml
└── requirements.txt
Contributing
Issues and pull requests are welcome: https://github.com/Aadhityan-A/mat_ret
Metadata
Release files for mat-ret 0.4.0
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 |
|---|---|---|---|---|
| mat_ret-0.4.0.tar.gz | 136.1 kB | Without provenance | Details for mat_ret-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mat_ret-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for mat_ret-0.4.0-py3-none-any.whl |
Total release size: 269.6 kB
Release files / mat_ret-0.4.0.tar.gz
| Download URL | mat_ret-0.4.0.tar.gz |
|---|---|
| Size | 136.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1199d51d0d21deefb7fc1613e94462f90214c78753c45ec1e1dde18e58c45fc
|
|
BLAKE2b-256 checksum How to use checksums |
afce0a55a6d4349ef0adc0a101b3bbe5585656be6bd8b068429d0c9547305dd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / mat_ret-0.4.0-py3-none-any.whl
| Download URL | mat_ret-0.4.0-py3-none-any.whl |
|---|---|
| Size | 133.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
afe8ccd323aa46a8e1b90ef7fb6bb17646f6438f08bae0e6567194326a3adc68
|
|
BLAKE2b-256 checksum How to use checksums |
f86fd3281f2537f50bf007b9b15482205361d5fbc27fa0f604dcc02997ed84c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for mat-ret 0.4.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.