Skip to content

EWALD Documentation

EWALD package icon

Experimental WAXS Analysis for Lattice Determination

Package icon

The EWALD package icon shown on this site was generated with help from a large language model.

EWALD is a Qt6 scientific workbench for GIWAXS/WAXS analysis. It brings detector-image import, calibration-aware q-space correction, ROI and peak fitting workflows, mathematical reciprocal-space conventions, lattice and structure-candidate ranking, CIF generation, and GIWAXS simulation into one project-based desktop interface. The simulation workflow compares experimental scattering targets against solved or generated CIF structures, including residual difference maps for judging fit quality.

Quick start

  1. Open Installation.
  2. Launch ewald and create or open an .ewld project.
  3. Open the workflow pages in sequence:
  4. Data Loading
  5. User Interface Overview
  6. ROI Tools
  7. Peak Identification
  8. Peak Fitting
  9. Mathematical Foundations
  10. Structure Analysis

What EWALD is for

  • Correct and inspect detector images in q<sub>xy</sub> and q<sub>z</sub>.
  • Build ROI definitions for lineout and azimuthal workflows.
  • Integrate peaks and fit q<sub>xy</sub>, q<sub>z</sub>, and azimuthal traces.
  • Follow documented derivations for q-space mapping, reciprocal lattices, Bragg conditions, ROI integrations, peak fitting, and simulation residuals.
  • Rank lattice candidates in Structure Analysis and compare with GIWAXS simulations.
  • Generate pole figures and export simulation/analysis outputs.

Main workflow

The standard workflow is:

  1. Create or open an .ewld project.
  2. Import .tif/.tiff data (single files or folders).
  3. Load correction assets (PONI, MASK) and confirm image correction state.
  4. Work in Data Viewer and define ROIs.
  5. Use Peak Identification and Peak Fit to produce peak centers and metrics.
  6. Import fitted peaks into Structure Analysis and evaluate candidate structures.
  7. Run or refine GIWAXS simulation as needed.
  8. Export outputs for downstream reporting and reuse.

Documentation map

Getting started

If this is your first run:

User Guide

Tutorials

Use these for task-based workflows:

Developer

Scope notes

EWALD is actively developed. This documentation marks each feature as:

  • Implemented where workflows are currently wired.
  • Experimental where behavior may change in near-term releases.
  • Planned for work not yet in the active user path.

Where a feature is not yet implemented, the docs call it out directly in its topic.

Local sample data and generated outputs are not committed to the repository. Project-specific datasets should live under the ignored example/projects/ tree without changing the Git checkout.