#774 closed defect (fixed)
RasQL scale : the result is no interval
Reported by: | Piero Campalani | Owned by: | Veranika Liaukevich |
---|---|---|---|
Priority: | critical | Milestone: | 9.0.x |
Component: | qlparser | Version: | development |
Keywords: | scale no interval | Cc: | Alex Dumitru, Vlad Merticariu, abeccati |
Complexity: | Medium |
Description
When trying to subset a scaled marray, sometimes there are difficulties and problems I can't really decode:
select scale( c[*:*,24:25,68:68], [0:5,36:38,102:103])[1:3,36,102] from eobstest AS c ==> rasdaman error 201: Exception: The result is no interval.
When using asterisks, the result is given:
select scale( c[*:*,24:25,68:68], [0:5,36:38,102:103])[1:3,*:*,*:*] from eobstest AS c
When I slice out every dimension, it works fine:
select scale( c[*:*,24:25,68:68], [0:5,36:38,102:103])[1,36,102] from eobstest AS c
If I don't slice out everything, and condense the marray, fail again ("The result is no interval").
select avg_cells (scale( c[*:*,24:25,68:68], [0:5,36:38,102:103] )[1:3,36,102]) from eobstest AS c
Change History (9)
comment:1 by , 11 years ago
Component: | undecided → qlparser |
---|
comment:2 by , 11 years ago
I arrived to such queries when trying to deliver a scatterplots of two coverages with different spatial domains / resolutions, aggregating means over a time interval: e.g. compare weekly mean values between two coverages.
(Could be a major
, but I raised the priority due to the upcoming WW Europa Challenge)
comment:3 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 10 years ago
Owner: | changed from | to
---|
comment:5 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
follow-up: 7 comment:6 by , 10 years ago
Thanks Veranika, I will test your fix asap.
NOTE: generally, the ticket reporter himself will be in charge to resolve the ticket.
comment:7 by , 10 years ago
Replying to pcampalani:
NOTE: generally, the ticket reporter himself will be in charge to resolve the ticket.
Oops, I was unaware.
comment:8 by , 10 years ago
Piero there's no such rule for rasdaman.org
In general the reporter will not know the correct resolution of the ticket anyway. The rule typically is 'please reopen if the problem persists'
comment:9 by , 10 years ago
Then I was not aware of this: sorry Veranika.
Thanks Dimitar.
Btw, I checked the fix: we can keep this closed
In which context is this critical?