-
Notifications
You must be signed in to change notification settings - Fork 18
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
Multiple possible axis matches found - mapCube "time" axis error with >1 InDims("time") and OutDims("time") #60
Comments
The issue seems to be the following: cta.time == cpr.time # Returns true
unique([cta.time, cpr.time]) # Returns a vector with both axes so although both time axes are the same, a call to |
I don't think, that defining an isequal method is going to change anything, because |
We would have to also implement a custom hash function because we already have the custom isequal function in Axes.jl 281.
See this julia issue for a more in depth discussion |
I was about to suggest exactly the same right now... |
After defining Base.hash(ax::CubeAxis{<:Any,S}, h::UInt) where S = hash(S, hash(ax.values, h)) @noralinscheid s example works as expected. Does anyone want to make a PR or shall I do it? |
I am having issues with applying mapCube on several cubes, when specifying more than one (identical) input axis InDims("time") and an OutDims("time"). Each input cube contains one time axis and they are identical. When using "lon" or "lat" axes instead this issue does not occur. If OutDims is not "time", the function also runs through. Prescribing a new time axis in OutDims circumvents the problem. So it seems quite specific to converting two InDims("time") to a single OutDims("time").
Error message:
on
[90b8fcef] YAXArrayBase v0.2.1
[c21b50f5] YAXArrays v0.1.2
[30363a11] NetCDF v0.11.3
[359177bc] ESDL v0.9.0
https://github.com/esa-esdl/ESDL.jl.git#master
The text was updated successfully, but these errors were encountered: