Fix hope number for results found

MBoustani commented 7 years ago

In query by list of cities the result shows number of hopes that found segments for it, but currently the number does not match the number of segments found.

MBoustani commented 7 years ago

+18005511300 Matched 3 hops

New York City (2014-05-26) Seattle (2014-06-02)

Seattle (2014-04-28) Los Angeles (2014-05-05)

Seattle (2014-05-26) Los Angeles (2014-06-02)

Seattle (2014-06-02) Los Angeles (2014-10-25)

Los Angeles (2014-04-28) Chicago (2014-05-05)

@wmburke this is result we get currently and I think the number of hope is actually correct. There are 3 unique hopes (NewYork-Seattle, Seattle-LA, LA-Chicago). The number of hope is not considering repetition. Does that make sense?

wmburke commented 7 years ago

This is hard to tell as it currently stands - I think it will be more clear once you reformat it to show the full routes in gray with the hops in black. As max hops is currently defined, it is used to organize the order in which the routes are shown, eg each route has a certain number of hops, the routes with the most hops should be listed first.

Does that make sense?

Wayne Moses Burke, MS Cognizant Engineer Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Mailstop: 168-527 E-mail: Wayne.M.Burke@jpl.nasa.govmailto:Wayne.M.Burke@jpl.nasa.gov

On 06/20/2017 02:34 PM, Mazi Boustani wrote:

+18005511300 Matched 3 hops

New York City (2014-05-26) Seattle (2014-06-02)

Seattle (2014-04-28) Los Angeles (2014-05-05)

Seattle (2014-05-26) Los Angeles (2014-06-02)

Seattle (2014-06-02) Los Angeles (2014-10-25)

Los Angeles (2014-04-28) Chicago (2014-05-05)

@wmburkehttps://github.com/wmburke this is result we get currently and I think the number of hope is actually correct. There are 3 unique hopes (NewYork-Seattle, Seattle-LA, LA-Chicago). The number of hope is not considering repetition. Does that make sense?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/memex-explorer/GeoPath-Clusetring/issues/2#issuecomment-309848445, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAHbFExHd5Fr7-87EQLP6Tw_pjgnSDV1ks5sGBB8gaJpZM4N_59c.

nasa-jpl-memex / GeoPath-Clustering

Fix hope number for results found #2