Skip to content
This repository has been archived by the owner on Sep 25, 2023. It is now read-only.

[QST] KalmanFilter and ParticleFIlter CuPy and cuSignal application opportunities #353

Open
apiszcz opened this issue Apr 19, 2021 · 4 comments
Assignees
Labels
? - Needs Triage Need team to review and classify inactive-30d inactive-90d question Further information is requested

Comments

@apiszcz
Copy link

apiszcz commented Apr 19, 2021

  • Stonesoup is a python framework for state estimation and tracking using Kalman and Particle filters.
  • Typically stonesoup measurements are iterated over for evaluation.
  • Is there any possibility that CuPy or cuSignal projects would be interested in review of Stonesoup to provide or implement/prototype recommendations for GPU acceleration options?

The measures.py file contains the Mahalanbois class that consumes a significant time in my profiling of the framework.
https://github.com/dstl/Stone-Soup/blob/main/stonesoup/measures.py

image

@apiszcz apiszcz added ? - Needs Triage Need team to review and classify question Further information is requested labels Apr 19, 2021
@awthomp
Copy link
Member

awthomp commented Apr 19, 2021

Hey @apiszcz -- Thanks for the question, and I'm always happy to chat about the future direction of cuSignal. Do you have any specific functions from Stonesoup that you'd like to see GPU accelerated? I know you mentioned that measures takes a lot of time; what specifically would you like to see us accelerate first?

You might also want to browse the documentation of another RAPIDS library, cuml, as it supports various distance metrics: https://docs.rapids.ai/api/cuml/stable/api.html#metrics-regression-classification-and-distance

@awthomp awthomp self-assigned this Apr 19, 2021
@apiszcz
Copy link
Author

apiszcz commented Apr 19, 2021

I reviewed those metrics, they are great, however I did not locate, Mahalanobis or SquaredGaussianHellinger,

@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
? - Needs Triage Need team to review and classify inactive-30d inactive-90d question Further information is requested
Projects
Status: No status
Development

No branches or pull requests

2 participants