MAST → IMAS IDS (imas-python + UDA) → NetCDF, versioned in object store (VirtualiZarr + icechunk)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 32/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- python
- Domain
- data-engineering
Research direction
Start in the dedicated fds/mast-imas-ingestion repository, since the core FDS issue contains no implementation files or tests. Review how the repository handles the MAST-to-IMAS mapping, NetCDF generation, and VirtualiZarr/icechunk object-store stages. Done means a working end-to-end demonstration plus notes on viability, gaps, and production recommendations.
Written by the indexing model from the issue text.
Description
Summary
Track the work led by Khalid (@ds2718) to demonstrate an end-to-end ingestion path for MAST data into IMAS IDSs and a chunked, versioned object-store representation.
Scope
- IDS mapping via UDA — use
imas-pythonwith the UDA backend to map MAST data into IMAS IDSs on the fly. - NetCDF generation — produce NetCDF outputs of the mapped MAST data using Imas-python.
- Virtual, versioned storage — use VirtualiZarr + icechunk to provide chunked, versioned representations of these datasets in an object store.
Deliverables
- A working demonstration of the pipeline (MAST → imas-python+UDA → IDS → NetCDF → VirtualiZarr/icechunk in object store).
- Notes / findings on viability, gaps, and recommendations for productionising.
Code home
Implementation lives in the dedicated ingestion repo: fds/mast-imas-ingestion (https://git.ccfe.ac.uk/fds/mast-imas-ingestion).
This issue stays here in the core FDS repo for tracking for now.
Milestone
Targeted for v0.1 — Ingestion & IMAS (due 2026-09-30).
Migrated from the internal tracker, where it was #14, opened 2026-06-22.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 26m
- Merged PRs (30d)
- 24
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ukaea/fds
-
performance
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
api architecture feature metadata priority: high
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
architecture metadata priority: medium
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
enhancement fair-compliance metadata priority: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Consume external provenance: inverse PROV mapping to register upstream inputs + create a Collection Openapi fair-compliance feature metadata priority: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100