-
Notifications
You must be signed in to change notification settings - Fork 27
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
filter of an overview gives wrong answer #409
Comments
Looks like a DiskArrays.jl problem to me (otherwise you couldn't use The problem is actually that julia> o[map(!(==(-9999)), o)] # This is what `filter` does underneath
2824-element Vector{Int16}:
-136
-159
-175
-180
-178
-137
-146
⋮
-9999
-9999
-9999
-9999
-9999
-9999
-9999 Where julia> o[broadcast(!(==(-9999)), o)]
2824-element Vector{Int16}:
-136
-159
-175
-180
-178
-137
-146
⋮
-164
-167
-161
-156
-160
-151
-157 |
So this is a DiskArrays.jl issue |
Haha this is my fault we are missing |
Very good. I am still confused, why this only happens on the overviews and not on the band. Because I just looked at the DiskGenerator that is constructed for both and they look very similar.
|
On the band the block looks like the whole axis (938?), so block iterate is the same as normal iterate |
I think |
Always collecting on map for a DiskArray sounds like very dangerous. I opened meggart/DiskArrays.jl#144 so that we can discuss this further there. |
When I use the
filter
function on an overview of a band I still get some of the filtered values.These are not there , when I am first collecting the array and then do the filtering operation. This only happens with an overview that I get from
AG.getoverview
and not from a band directly. An example file is attached. I find it strange, that there seems to be the same amount of values which for me might mean, that the filtering and the accessing is using different code paths.I also see strange behaviour when plotting the data. The overview plotted directly seems to be randomly shifted.
pyramidmiddle.zip
The text was updated successfully, but these errors were encountered: