Opened 8 years ago

Closed 8 years ago

#1220 closed defect (duplicate)

WCPS1.5_Inconsistence in parsing float scalar and float expression

Reported by: Bang Pham Huu Owned by:
Priority: major Milestone: 10.0
Component: petascope Version: development
Keywords: wcps 2.0, error parsing scalar with float Cc: Dimitar Misev, Vlad Merticariu
Complexity: Medium

Description

With WCPS query 1.5, using float scalar t(4.8)

for c in (eobstest) return encode(max(c[t(4.8),Lat(20.5:35.1), Long(10.5:75.3)]), "csv")

which will translate to Rasql

SELECT encode( max_cells(c[4,-29:100,81:109]) , "csv" ) FROM eobstest AS c

and returns {1105}

while float expression, example (5 - 0.2)

for c in (eobstest) return encode(max(c[t(5 - 0.2),Lat(20.5:35.1), Long(10.5:75.3)]), "csv")

will returns error

petascope.wcps2.error.managed.processing.InvalidDateTimeSubsetException : 

Invalid subsetting coordinates: 5 - 0.2:5 - 0.2 for axis t.

with "+", "*", "/" with float, e.g (3 + 2.2)

for c in (eobstest) return encode(max(c[t(3 + 2.2),Lat(20.5:35.1), Long(10.5:75.3)]), "csv")

will throw another error

ows:Exception exceptionCode="RasdamanRequestFailed">
<ows:ExceptionText>
Error evaluating rasdaman query: 'SELECT encode( max_cells(c[3 + 2.2,-29:100,81:109]) , "csv" ) FROM eobstest AS c
</ows:ExceptionText>
</ows:Exception>
<ows:Exception exceptionCode="RuntimeError">
<ows:ExceptionText>
org.odmg.QueryException : Execution error 390 in line 1, column 27, near token [: Minterval dimension specifications must be either of type interval or integer.
</ows:ExceptionText>
</ows:Exception>

Change History (1)

comment:1 by Bang Pham Huu, 8 years ago

Resolution: duplicate
Status: newclosed

the problem of this ticket which combines from:

+ ticket:1219 - change the correct way to handle "time" value (i.e: 5 - 2 will be valid binary expression).

and

+ ticket:1239 - calculate the expression in slicing/trimming expression. (i.e: 3 + 2.2 will be calculated to t(5.2) and convert to a integer in grid axis, same as 5 - 2: t(3)).

Then I will close this ticket here.

Note: See TracTickets for help on using tickets.