Skip to content

Ensure (ux)fieldset has both UV and UVW for datasets with U, V, and W#2505

Merged
fluidnumerics-joe merged 6 commits intomainfrom
patch/ux-uv-uvw
Feb 23, 2026
Merged

Ensure (ux)fieldset has both UV and UVW for datasets with U, V, and W#2505
fluidnumerics-joe merged 6 commits intomainfrom
patch/ux-uv-uvw

Conversation

@fluidnumerics-joe
Copy link
Contributor

Summary

This branch ensures that FieldSet objects created from datasets containing U, V, and W velocity components have both UV and UVW vector fields available.

Changes

Bug Fix: Missing UV VectorField for 3D velocity datasets

Previously, when a dataset contained all three velocity components (U, V, W), only the UVW VectorField was created. This meant users could not access a 2D UV VectorField for horizontal-only advection without manually creating one.

Now, both UV and UVW VectorFields are automatically created when all three components are present, providing flexibility for both 2D and 3D advection use cases.

@VeckoTheGecko VeckoTheGecko changed the base branch from v4-dev to main February 16, 2026 11:13
@fluidnumerics-joe fluidnumerics-joe merged commit bd60c7c into main Feb 23, 2026
13 checks passed
@fluidnumerics-joe fluidnumerics-joe deleted the patch/ux-uv-uvw branch February 23, 2026 18:10
@github-project-automation github-project-automation bot moved this from Backlog to Done in Parcels development Feb 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants