[jira] [Work logged] (SDAP-196) Account for time when finding closest match

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SDAP-196?focusedWorklogId=276481&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276481 ]

ASF GitHub Bot logged work on SDAP-196:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Jul/19 05:18
            Start Date: 15/Jul/19 05:18
    Worklog Time Spent: 10m 
      Work Description: fgreg commented on pull request #70: SDAP-196: Account for time when finding closest match
URL: https://github.com/apache/incubator-sdap-nexus/pull/70
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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


Issue Time Tracking
-------------------

    Worklog Id:     (was: 276481)
    Time Spent: 20m  (was: 10m)

> Account for time when finding closest match
> -------------------------------------------
>
>                 Key: SDAP-196
>                 URL: https://issues.apache.org/jira/browse/SDAP-196
>             Project: Apache Science Data Analytics Platform
>          Issue Type: Improvement
>          Components: nexus
>            Reporter: Frank Greguska
>            Assignee: Frank Greguska
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> [https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms_spark/Matchup.py#L467-L484]
>  
> As you can see, we do only take into account spatial distance, not time distance. This would be where we need to modify the code to also take into account time distance when trying to find the closest match.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)