Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement API for FieldSet, Field, ScalarField, VectorField etc #1848

Open
erikvansebille opened this issue Feb 11, 2025 · 4 comments
Open
Assignees
Labels

Comments

@erikvansebille
Copy link
Member

No description provided.

@fluidnumerics-joe
Copy link

Hey all, with this API settling in, should we discuss concrete tasks to adapt to the new fieldset and field . I suppose something similar to @willirath 's trimmed down implementation would be appropriate but it's possible I missed some conversations around this. @VeckoTheGecko , what do you think ?

@VeckoTheGecko
Copy link
Contributor

VeckoTheGecko commented Feb 17, 2025

@fluidnumerics-joe I think that this is important to discuss. Just tuning back into parcels dev over the next couple days - I want to get a grasp on xgcm to (a) make sure I haven't missed anything and (b) see if there are any ideas that can help guide our development.

At this point, I'm not sure what those concrete tasks would look like (since its dependent on what I discover this week from xgcm). Do you have any thoughts on it from your side?

@fluidnumerics-joe
Copy link

I started to get some things out of my head here : Parcels v4

@willirath has a good start (IMO) of a trimmed down FieldSet in main...v/mvp-dependency-discovery . Would it make sense to build off of the work in this branch ?

@willirath
Copy link
Collaborator

I'm not too proud of thev/mvp-dependency-discovery branch :) But something along these lines should be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Status: In review
Development

No branches or pull requests

4 participants