-
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
Ozone#1 MERGED-UV #142
Comments
Hi @sandrocalmanti, I think there's a bug with the data coverage figure:
This is what I'm getting if I hardcode the same colorbar in your figures (don't worry about messy labels for now): fig, axs = plt.subplots(2, 1)
levels = range(0, 10_501, 1_500)
for ax, dim in zip(axs.flatten(), ("longitude", "latitude")):
da = ds_map[varname].sum(dim, keep_attrs=True)
da.plot.contourf(x="time", ax=ax, levels=levels, extend="max") Questions for you:
|
Hi @sandrocalmanti, Besides for the issue in my previous comment, the notebook was already in great shape.
Side node: Make sure you use the same chunking when you run |
Hi @malmans2 very good point with your first comment. It was not clear to me how to handle the colorbar so I didn't notice the problem and the figures just looked wierd to me. We need to rescale with the number of grid points, so we get the average number of observations per grid point over each latitude (or longitude). With this rescaling it becomes evident that the two figures contain essentially the same information. So we can use only the first hoevmoller (time, latitude) which shows the seasonal coverage over the polar regions. Something like the attached NB |
Hi @sandrocalmanti, I made some minor change. It should be in good shape now, but I'll wait for your OK to close this issue. |
Notebook description
Dear @malmans2 ,
this is the first of two upcoming notebooks on Ozone. IT should be a rather simple one.
It has been prepared by a collegue and I have tried clean it up a bit before your revision.
It's WP5
Best!
S.
Notebook link or upload
ozone-MERGED-UV.zip
Anything else we need to know?
No response
Environment
The text was updated successfully, but these errors were encountered: