Opened 13 years ago
Closed 13 years ago
#76 closed defect (fixed)
CSV output does not coincide with Hexadecimal output
Reported by: | Owned by: | jwaldman | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | petascope | Version: | 8.2 |
Keywords: | Cc: | Peter Baumann, Dimitar Misev | |
Complexity: | Medium |
Description
bug derived by a discussion on rasdaman-users mailing list http://groups.google.com/group/rasdaman-users/browse_thread/thread/ec621a2755e7605e?hl=en
CSV output does not coincide with Hexadecimal output
Attached the images and the scripts than can reproduce the error
The detailed description of the issue that affects also Petascope are provided at http://groups.google.com/group/rasdaman-users/browse_thread/thread/ec621a2755e7605e?hl=en
Damiano
Attachments (1)
Change History (5)
by , 13 years ago
Attachment: | petascopeIssue.zip added |
---|
comment:1 by , 13 years ago
Cc: | added |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 13 years ago
comment:3 by , 13 years ago
Summary: | Link petascope coverage axes and rasdaman collections. CSV output does not coincide with Hexadecimal output → CSV output does not coincide with Hexadecimal output |
---|
comment:4 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Submitted patch that fixes this.
Note:
See TracTickets
for help on using tickets.
I believe we are seeing a similar issue on our datasets.
We are also using Petascope but the problem is reproduced below in RASQL.
I would expect the second result set to include the data found in the first. Am I missing something?
Cheers,
Pete