-
Notifications
You must be signed in to change notification settings - Fork 17
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
dim handling issues #18
Comments
Thank you very much for your investigations. I will start on fixes for each point and raise new issues for each individually, and then link those back here. |
All three of these points ended up being addressed through the response to issue #19, and so this can now be closed. |
Closing |
tennlee
pushed a commit
that referenced
this issue
Jun 24, 2024
tennlee
pushed a commit
that referenced
this issue
Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I did some testing of dim handling using
mse
from main in a jupyter notebook.Here is some code and problems I found.
mse(fcst, obs, reduce_dims=[])
returns a single value (i.e. reduces all dimensions). It would be preferable if it reduced no dimensions.mse(fcst, obs, preserve_dims=['source', 'date', 'stn'])
returns a single value (i.e. reduces all dimensions) rather than an array with all dimensions preserved. Same asmse(fcst, fcst, preserve_dims=fcst.dims)
mse
says, for 'preserve_dims', that "the forecast and observed dimensions must match precisely". This can be removed as it works perfectly fine if they don't match (using usual xarray broadcasting) and I don't think it is even desirable that fcst and obs have matching dimensions.The text was updated successfully, but these errors were encountered: