Skip to content

[DRAFT: Discussion] 2034 v4 particleset execute#2046

Closed
fluidnumericsJoe wants to merge 13 commits into
v4-devfrom
2034-v4-particleset-execute
Closed

[DRAFT: Discussion] 2034 v4 particleset execute#2046
fluidnumericsJoe wants to merge 13 commits into
v4-devfrom
2034-v4-particleset-execute

Conversation

@fluidnumericsJoe

Copy link
Copy Markdown
Contributor
  • Chose the correct base branch (main for v3 changes, v4-dev for v4 changes)
  • Fixes #
  • Added tests
  • Added documentation

This is needed for consistency of grid access independent of whether we
are referencing a scalar or vector field.
This property is needed for determining min/max depth bounds in
particleset.__init__ . With consistency between XGrid and UXGrid, this
getting depth ranges with either grid type can be accomplished with the
same code in particleset.__init__
This commit also cleans up a few sections of init for working with the
new field/fieldset API.
Currently, we don't have support for igrid selection
This prevents errors in the field.eval calls for constant in time fields
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Parcels development Jun 30, 2025
@fluidnumericsJoe fluidnumericsJoe deleted the 2034-v4-particleset-execute branch January 6, 2026 22:17
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.

1 participant