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

Create warning for interpolation from geodata #148

Open
krober10nd opened this issue Nov 30, 2020 · 3 comments
Open

Create warning for interpolation from geodata #148

krober10nd opened this issue Nov 30, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@krober10nd
Copy link
Collaborator

  • Altering user geodata may have been downsampled to fit in RAM and it's best to probably just interpolate directly from the DEM.
m = interp(m,'DEM.nc'); 
@HamishB
Copy link

HamishB commented Dec 4, 2020

just to note, I tried changing the hardcoded AVAILABLE_MEMORY=4 GB size in geodata.m to 100 GB on our big-memory workstation but was still getting downsampling stride messages. Maybe that was just because the DEM is much finer resolution than the minimum element size; is it supposed to be like that?

@krober10nd
Copy link
Collaborator Author

yes. If the DEM is much finer than the minimum element size, then there's little point in reading in everything. I guess we could put some more advanced up and down sampling methods.

@krober10nd
Copy link
Collaborator Author

Just to note: I would strongly recommend not interpolating from the geodata object and instead using the original NetCDF file with msh.interp.

Building a mesh from a geodata object is fine, but interpolation is more critical to get right and sensitive to downsampling.

@krober10nd krober10nd added the enhancement New feature or request label Feb 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants