sdap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SDAP-50) Fix incorrect Hovmoller Implementation
Date Fri, 07 Sep 2018 19:38:00 GMT

    [ https://issues.apache.org/jira/browse/SDAP-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607579#comment-16607579
] 

ASF GitHub Bot commented on SDAP-50:
------------------------------------

jjacob7734 opened a new pull request #28: SDAP-50 Fix incorrect Hovmoller Implementation
URL: https://github.com/apache/incubator-sdap-nexus/pull/28
 
 
   This fixes several problems with the Spark Hovmoller Map algorithms:
   (1) Currently the Hovmoller calculation is averaging latitudes or longitudes within individual
tiles. However, depending on the search domain, unique lats/lons can be in multiple tiles.
   (2) A time stamp can appear multiple times in the JSON response
   (3) Lack of cos(lat) weighting when averaging over latitude
   
   Note that the non-Spark Hovmoller algorithms have these same problems, but are considered
deprecated and have not been fixed in this pull request.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Fix incorrect Hovmoller Implementation
> --------------------------------------
>
>                 Key: SDAP-50
>                 URL: https://issues.apache.org/jira/browse/SDAP-50
>             Project: Apache Science Data Analytics Platform
>          Issue Type: Bug
>          Components: nexus
>            Reporter: Frank Greguska
>            Assignee: Joseph Jacob
>            Priority: Major
>             Fix For: 0.1
>
>
> Currently the Hovmoller calculation is averaging latitudes or longitudes within individual
tiles. However, depending on the search domain, unique lats/lons can be in multiple tiles.
> The algorithm needs to be updated to average all unique (time, lat) or (time, lon) values
regardless of tiles.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message