Free instrument-data tool

XRD data files, parsed and analyzed — free

What .xye, .raw and .brml XRD files are, why vendor formats differ, and how to view/analyze powder diffraction data — upload to Matflow free, or parse in Python.

Formats: .xye / .xy (two/three-column text), Bruker .raw/.brml, Rigaku .txt, PANalytical .xrdml (XML) · For: Materials & solid-state labs

The format

What the format actually is

Where the data hides, and what a naive parser loses.

Every diffractometer vendor exports its own format: Bruker RAW (binary with versioned headers) and BRML (a zip of XML), Rigaku text exports, PANalytical XRDML (XML), and the community-standard .xye (2θ, I, esd — three-column text from GSAS-II).

The physics is universal — intensity vs 2θ (or d-spacing) — but metadata (scan axis, step size, counting time per step, anode material) is inconsistently preserved, which is exactly what you need for proper peak-shape work later.

Analysis workflows (background subtraction, Kα2 stripping, peak fitting, phase ID against a database) usually span one vendor tool plus Excel plus a plotting script — with no provenance connecting them.

Watch out

Vendor quirks that break naive parsers

Each of these has produced a silently wrong number in a real workflow.

Binary RAW headers changed across Bruker versions (DIFFRAC vs classic RAW).
XRDML stores scan metadata richly but is awkward in spreadsheet tools.
.xye loses everything except the numbers — fine for Rietveld, bad for audit.
Open source

Do it yourself in Python

We would rather you succeed with or without us. The open-source path:

For .xye/.xy: numpy.loadtxt is genuinely enough — the format is its own beauty.
xrayutilities and pymatgen both read several vendor formats (including BRML/RAW variants) for quantitative work.
bg subtraction: rolling-minimum or SNIP algorithm; Kα2 stripping via Rachinger or the split-Pearson methods before fitting.
Upload path

What happens if you use Matflow

The parser is only step one — the value is the review and the provenance that follow.

01

Upload on the Ingestion page

Excel, CSV, PDF, SDS images and instrument files are parsed into evidence-tagged rows — the original file is retained as provenance.

02

Review before promotion

Column roles and types are proposed for a reason; correcting a mislabeled column here is the highest-leverage five minutes in the workflow.

03

Promote to a governed dataset

The accepted rows become a versioned dataset any stage can use — every row keeps its source and extraction status.

Docs: ingestion & extraction · column roles · instrument parsers

Stop parsing by hand

Upload your .xye / .xy file to Matflow and it lands as a governed, validated dataset — original file preserved as provenance, every column documented. Free tier, no card.