Skip to content
This repository has been archived by the owner on Aug 9, 2023. It is now read-only.

Clarify what is meant by "Support UGRID" #5

Open
lesserwhirls opened this issue Nov 7, 2018 · 2 comments
Open

Clarify what is meant by "Support UGRID" #5

lesserwhirls opened this issue Nov 7, 2018 · 2 comments
Labels
question Further information is requested

Comments

@lesserwhirls
Copy link
Contributor

As mentioned at the meeting today, we should clarify what is meant by supporting UGRID.

Triangle, quad, hex, meshes? Full 3D unstructured topology?

For sure, support output from FVCOM , ADCIRC, SCHISM. Anything else? Please add pointers to samples here.

@lesserwhirls lesserwhirls added the question Further information is requested label Nov 7, 2018
@yosoyjay
Copy link
Member

yosoyjay commented Nov 7, 2018

In the meeting it was proposed to focus on support for triangular meshes initially because that's the discretization used by the "backbone" models.

However, there are some models such as DELFT3D and SCHISM that allow for hybrid mesh in the horizontal and MPAS uses hexes.

I believe we chose to hold on supporting fully unstructured in 3D.

@lesserwhirls
Copy link
Contributor Author

That's what I recall as well. I've updated #4 with a list of samples to capture.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
Development

No branches or pull requests

2 participants