-
Notifications
You must be signed in to change notification settings - Fork 4
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
Run "Filtering on CPUs versus GPUs" with data from pangeo catalog #5
Comments
This looks amazing @leticiafabre! Regarding your question - yes, in general it is best to select the region first before computing. But it depends how you wrote your code. If you wrote the code in xarray and only do the computation (or plotting) at the end, then you are already essentially slicing your region before computing. |
Yay, nice work @leticiafabre! 🎉 Have you played around with the filter scale: making it smaller and larger? You could also plot the difference SSH - filtered SSH, which will give you the small scales only (while the filtered SSH gives you the large scales). |
Thanks @paigem and @NoraLoose! I will try change the filter scale and plot the difference SSH - filtered SSH. |
@leticiafabre look at those pretty plots - yay! 🎉 Another thing you could try is to label the x- and y-axis with longitude and latitude values (rather than nlon and nlat, which are just grid indices).
Correct, the minimum scale is the grid scale. |
The POP model doesn't make it super straightforward to plot with lat/lon rather that nlat/nlon. Feel free to give it a try, but we can also make a note to discuss this more during our Zoom call tomorrow! 😊 |
Looks awesome @anaclarabmariani 🎉 I have two small comments:
before you save the figure, and play around with the value for
|
|
I am running this example but loading the NCAR data from pangeo catalog. Insted of filtering SST I filtered SSH just to test something different. That is what I got until now:
I think the next step is to select the area before filtering to save computional effort(?)
The text was updated successfully, but these errors were encountered: