Skip to content

Instantly share code, notes, and snippets.

@nperree-dstl

nperree-dstl/SensorManagementTutorial1-old.ipynb

Last active July 5, 2021 14:35
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save nperree-dstl/28caf233dc9dd8e84eb4b88b3b77d0f2 to your computer and use it in GitHub Desktop.
Save nperree-dstl/28caf233dc9dd8e84eb4b88b3b77d0f2 to your computer and use it in GitHub Desktop.
Download ZIP
Sensor Management Tutorial 1 (old)
Display the source blob
Display the rendered blob
Raw
SensorManagementTutorial1-old.ipynb
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@apiszcz
Copy link

apiszcz commented Feb 22, 2021

This looks great, detailed and will take me some time to review.

  1. Sensor manager, is there a possibility of measuring the resources of the tracker to maintain real time updates with varying numbers of targets? (latency of tracker in milliseconds)
  2. Interested in understanding the impact of tracking parameters, approaches, (JPDA...) on different configurations.

Plot Graph A and B remind me of what I was creating last year.
image

@apiszcz
Copy link

apiszcz commented Feb 23, 2021 •
edited

Resource measures/thoughts

  1. CPU FLOPS/etc required for a range of target set sizes
  2. Memory required, data structures, state, etc. Sizing for 1, 10, 100, 1000, 10000, ... targets
  3. Real time ratio, for each given target set size how do each of the methods under consideration maintain tracking with respect to real time, 0.1x (10 times slower than real time), 10x 10 times faster, for each target set size.
  4. Consider performance counters for measures
    https://pypi.org/project/python_papi/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment