-
Notifications
You must be signed in to change notification settings - Fork 15
opening soil moisture dataset - new "integer division or modulo by zero" error #444
Comments
@HelenClifton, @kbernat if I use the same constraint parameters in 1.0.0.dev1, the error does not occur. Instead, nothing will be displayed. It seems that when the dataset is opened via OPeNDAP with region (72, 8, 85,17), the Latitude should not disappear because resolution is 1440/360 = 4 grid cells per degree, therefore new lat dim size should be (17 - 8) * 4 = 36 cells. Lon size is correct with (85 - 72) * 4 = 52 cells. Chris, I guess the bug is somewhere downstream of
|
set_workspace_resource() call raised exception: "The indexing operation you are attempting to perform is not valid on netCDF4.Variable object. Try loading your data into memory first by calling .load()."
|
no some data it works, on some it does not :/ - working on it. |
I compared SST (which works perfect) and SOILMOISTURE, the one obvious difference is that
|
@forman @mzuehlke @JanisGailis imho the problem lies somewhere in subset operation or any other harmonization/normalization part.
|
@JanisGailis @kbernat In my first comment above I wrote
Any subset operation should be aware of that. It is also fully in line with CF. |
Looking at the |
I'll look into it. I remember that there was something with us using a polygon that made things tricky, but I don't remember what exactly it was. |
@forman Can you point me in the right direction regarding where it is in the CF conventions? I can not find anything regarding directionality of the latitude vector, it just talks about endorsing the usage of 'degrees_north' as the unit, and it doesn't say anything regarding if the counting should start at the North or at the South pole. Maybe this is what you mean, that it is not specified => legal. |
Heh. I had made a test for inverted dimensions, but the test was wrong (the same as nominal). When I fixed the test it now fails in spatial attribute adjustment thing. On it. |
Both mentioned by me data sources uses units degrees_north, It means that one is wrong. |
@kbernat as mentioned be @forman earlier the direction of the axis can be increasing or decreasing. |
@mzuehlke thanks! I really expected to see.. hmm.. degree_south :) in case of descending order. Now it's clear for me! |
Can someone verify if it works as expected with the GUI now, after the spatial_subset fix? |
@kbernat was in the process of using the |
@kbernat any progress on this issue ? |
@mzuehlke need bit more time to verify it. At the moment my Cate Desktop from git does not recognize cate webservice anymore.. |
Confirmed it is fixed in cate 1.0.0-dev.3 |
Expected behavior
Running either use case 6 happy path and use case 2 happy path
Opening dataset
esacci.SOILMOISTURE.day.L3S.SSMV.multi-sensor.multi-platform.COMBINED.03-2.r1
Actual behavior
Dataset downloads then there is an error when it is opened

use case 6
use case 6 Traceback:
sm traceback.txt
use case 2

Traceback:
sm traceback 2.txt
Steps to reproduce the problem
use case 6
steps to reproduce uc6.docx
use case 2
steps to reproduce - uc 2.docx
Notes
Thought to be different to #326 because here only sm and sm_uncertainty varaiables are selected.
Champion users should decide whether this dataset should be in the whitelist
Specifications
cate-0.9.0-dev.7
Windows 7 Professional
The text was updated successfully, but these errors were encountered: