HoloWizard
HoloWizard is a collection of software tools for phase retrieval in the setting of near-field holographic microscopy and tomography. It is developed at DESY, Hamburg in the group X-Ray Nanoscience and X-Ray Optics. The software is designed to cover all steps in experimental/algorithm development:
- The Forge generates datasets within given variation bouds either for testing new algorithms or provide training data sets for ML applications
- The Core implements the ASRM algorithm, our phase retrieval engine. It includes also all neccessary auxillary functions to load and preprocess single holograms/diffraction patterns.
- The Pipe enables the online and offline batch processing of holo tomograms, i.e. the phase retrieval of individual projections(along with all preprocessing steps) and the computation of the tomographic volume from the retrieved projections.
- The Livereco module can show online reconstructions of single projections during an experiment i.e. for finding a suited region of interest. It can be integrated in existing experimental control software.
Table of Contents
Installation
Python Environment
Create a new environment with python 3.11., i.e. with mamba
$ mamba create -p <path_to_env> python=3.11
Activate enviroment
$ mamba activate <path_to_env>
Install package
$ pip install holowizard --no-cache
INFO: The option --no-cache should help to resolve some dependencies issues.
Tools
The Core
To create examples, open a terminal and run
$ holowizard_core_create_examples <directory>
The Pipe
Setting Up an Instance
We provide a CLI command to initialize everything:
$ holowizard_pipe_start beamtime.name=YOUR_BEAMTIME_NAME beamtime.year=YEAR_OF_BEAMTIME
This command sets up the pipeline. You can override any other configuration value using Hydra’s override syntax:
👉 Hydra Override Syntax Documentation
If the startup is successful, you’ll see output like:
INFO: Uvicorn running on http://MY_IP_ADDRESS:MY_PORT (Press CTRL+C to quit)
Click the address to open a browser window showing that holopipe is running.
Visit: http://MY_IP_ADDRESS:MY_PORT/dashboard for useful runtime information.
Add a scan with default parameters.
You can submit scans using a simple curl POST request:
curl -X POST \
-H "Content-Type: application/json" \
-d '{ "a0": 1.0,
"scan_name": "nano145014_s7_1_tum",
"holder": 220,
"base_dir": "holopipe",
"reconstruction": "wire",
"find_focus": "wire",
"energy": 17.0
}' \
http://MY_IP_ADDRESS:MY_PORT/api/submit_scan
If you are on the same machine as the server is running you can use the python script:
holowizard_pipe_reconstruct_scan --help # will tell you all important parameters
Required Parameters
name: Folder name of the current scanholder: Height of the holderenergy: Scan energy in keV
Optional Parameters
a0: Optional numeric parameter; if not provided, it will be computed automaticallyreconstruction: Instruction set for reconstruction —wire(default) orspiderfind_focus: Instruction set to find focus —wire(default) orspiderbase_dir: Root directory for output files (default:holopipe)
Parameter Optimization
To performe parameter optimization go to http://MY_IP_ADDRESS:MY_PORT/parameter. Here you can set all parameter for all stages. To test them click Reconstruct. If the parameters work well, you can save them to the current beamtime folder using the Save as at the lower left.
If you want to reconstruct the whole scan you can click Submit All after chosing the Options. If you select Custom it will take the parameters from the left.
Other changes during beamtime
If you change the detector or anything else like removing tasks adapt parameters the full config files are located in the beamtime/processed/holowizard_config/folder. Changes here will reflect onto future curl requests!
The Forge
This framework can be used to generate large datasets of simulated holograms of randomly sampled objects.
Create New Dataset
Open a terminal and create a new config file with
$ holowziard_forge_create_testconfig <args>
| Argument | Description | Position |
|---|---|---|
name |
Name of the new config file (without file name extension) | 1 |
--output_dir |
Output directory | optional |
--override |
Overrides existing configuration file | optional |
The config file can then be customized and used to create a new dataset with
$ holowizard_forge_generate_data <args>
| Argument | Description | Position |
|---|---|---|
config |
Path to the custom configuration file. | 1 |
output_dir |
Output directory where the generated data is stored. | 2 |
num_samples |
Number of data samples that should be generated. | 3 |
--override |
Override the output folder if it already exists. | optional |
Output Structure
output/
└── train.hdf5
└── train.json
The file train.hdf5 contains the training data
The file train.json contains the config parameters which have been used for the training data creation.
Developer Info
Add new Parameters
To add a new parameter, add it to the default configuration holowizard/forge/configs/default.json.
The Livereco
Start the online reconstruction server with
$ holowizard_livereco_server_start
Citations
Artifact-suppressing reconstruction method:
- URL: https://opg.optica.org/oe/fulltext.cfm?uri=oe-32-7-10801&id=547807###
- DOI: 10.1364/OE.514641
@article{Dora:24,
author = {Johannes Dora and Martin M\"{o}ddel and Silja Flenner and Christian G. Schroer and Tobias Knopp and Johannes Hagemann},
journal = {Opt. Express},
keywords = {Free electron lasers; Holographic microscopy; Imaging techniques; Phase shift; X-ray imaging; Zone plates},
number = {7},
pages = {10801--10828},
publisher = {Optica Publishing Group},
title = {{Artifact-suppressing reconstruction of strongly interacting objects in X-ray near-field holography without a spatial support constraint}},
volume = {32},
month = {Mar},
year = {2024},
url = {https://opg.optica.org/oe/abstract.cfm?URI=oe-32-7-10801},
doi = {10.1364/OE.514641},
abstract = {The phase problem is a well known ill-posed reconstruction problem of coherent lens-less microscopic imaging, where only the squared magnitude of a complex wavefront is measured by a detector while the phase information of the wave field is lost. To retrieve the lost information, common algorithms rely either on multiple data acquisitions under varying measurement conditions or on the application of strong constraints such as a spatial support. In X-ray near-field holography, however, these methods are rendered impractical in the setting of time sensitive in situ and operando measurements. In this paper, we will forego the spatial support constraint and propose a projected gradient descent (PGD) based reconstruction scheme in combination with proper preprocessing and regularization that significantly reduces artifacts for refractive reconstructions from only a single acquired hologram without a spatial support constraint. We demonstrate the feasibility and robustness of our approach on different data sets obtained at the nano imaging endstation of P05 at PETRA III (DESY, Hamburg) operated by Helmholtz-Zentrum Hereon.},
}
Model-based autofocus:
- URL: https://opg.optica.org/oe/abstract.cfm?doi=10.1364/OE.544573
- DOI: 10.1364/OE.544573
@article{Dora:25,
author = {Johannes Dora and Martin M\"{o}ddel and Silja Flenner and Jan Reimers and Berit Zeller-Plumhoff and Christian G. Schroer and Tobias Knopp and Johannes Hagemann},
journal = {Opt. Express},
keywords = {Image analysis; Image metrics; Imaging systems; Phase retrieval; X-ray imaging; Zone plates},
number = {4},
pages = {6641--6657},
publisher = {Optica Publishing Group},
title = {Model-based autofocus for near-field phase retrieval},
volume = {33},
month = {Feb},
year = {2025},
url = {https://opg.optica.org/oe/abstract.cfm?URI=oe-33-4-6641},
doi = {10.1364/OE.544573},
}
Further links
https://helmholtz.software/software/holowizard
https://connect.helmholtz-imaging.de/solution/71
https://connect.helmholtz-imaging.de/blog_gallery/blogpost/10
Metadata
Release files for holowizard-livereco-client 3.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| holowizard_livereco_client-3.0.6.tar.gz | 276.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| holowizard_livereco_client-3.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 557.9 kB
Release files / holowizard_livereco_client-3.0.6.tar.gz
| Download URL | holowizard_livereco_client-3.0.6.tar.gz |
|---|---|
| Size | 276.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2841e66d307e362b3528a84ad00e2cd0fcad68bc1dadeae997e3e271bf028148
|
|
BLAKE2b-256 checksum How to use checksums |
46e70855996b6f55f316e6674bb9f25b149b76a745114f5c934263c1011c72b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 13, 2026.
Transparency logRelease files / holowizard_livereco_client-3.0.6-py3-none-any.whl
| Download URL | holowizard_livereco_client-3.0.6-py3-none-any.whl |
|---|---|
| Size | 281.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23b474df822c4cb844a0a6292bc6c007d25922c1ab19026d11bda3e9b264b50e
|
|
BLAKE2b-256 checksum How to use checksums |
24c6a06ed488be1d39dc7756a6f44c90d2923afefa6fee9e51678b05b2fa56aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 13, 2026.
Transparency log