Forum rss-feed

Forum

Developers: frequency as primary input?

Most Recent

written by: geert

If you only need frequency data, it perfectly makes sense to make it a vector input. It's what I did in the CV calibration agent I've been working on:
https://github.com/Eigenlabs/EigenD-Contrib/blob/master/cv_calibration/cv_calibration_plg.py

Hope this helps,

Geert

written by: NothanUmber

Sun, 21 Oct 2012 20:20:54 +0100 BST

In most examples I found, frequency input was using merge policy in a bundle with key input being the primary input.
After listening to the DevCon videos again: Jim told us that correlation does come at a hefty price.
So: Does anything speak against not using a bundle and use frequency as the only fastpath input (it is a filter that replaces frequency data, I don't need to know the key position for the calculation).
How would the slot config look like then for the frequency input, Aniso with vector policy?


written by: NothanUmber

Sun, 21 Oct 2012 20:28:10 +0100 BST

Thanks, this looks like what I need!


written by: geert

Sun, 21 Oct 2012 20:40:27 +0100 BST

If you only need frequency data, it perfectly makes sense to make it a vector input. It's what I did in the CV calibration agent I've been working on:
https://github.com/Eigenlabs/EigenD-Contrib/blob/master/cv_calibration/cv_calibration_plg.py

Hope this helps,

Geert



Please log in to join the discussions