Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add psd_pipeline_sim application #572

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JohnMoon-VTS
Copy link
Contributor

When trying to use Holoscan as an SDR framework (like GNU Radio or REDHAWK), there are a few missing pieces such as a generic IQ file reader application and simple blocks like FFT and PSD. It also lacks some support for VITA 49.

We'd like to add an application which takes in file data, does some signal processing, and outputs VITA 49 spectral data packets.

In the future, we plan on adding a VITA 49 ingest operator which leverages ANO, but for now, the file-based simulation is helpful.

One challenge we encountered in developing this pipeline is how to handle metadata flow between operators. In this case, we've dropped a shared data structure in operators/psd, but this doesn't seem like the right way to do it. Coming from GNU Radio, there's the concept of stream tags which could be helpful here. Does Holoscan have any equivalent? This would make it much easier to make generic, share-able blocks.

When trying to use Holoscan as an SDR framework (like GNU Radio or
REDHAWK), there are a few missing pieces such as a generic IQ file
reader application and simple blocks like FFT and PSD. It also lacks
some support for VITA 49.

Add an application which takes in file data, does some signal
processing, and outputs VITA 49 spectral data packets.

In the future, we plan on adding a VITA 49 ingest operator which
leverages ANO, but for now, the file-based simulation is helpful.

Signed-off-by: John Moon <[email protected]>
@JohnMoon-VTS
Copy link
Contributor Author

Thanks to @dylan-eustice for some advice offline about using Holoscan's metadata flow! I've updated to use that instead which obviated the need for the ugly shared data structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant