Hi,
I'v tested my scenario with mmWave Demo Visualizer and gotten the configure file. But how can I reuse those parameters in mmWave-Studio in order to capture raw data?
Thanks.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I'v tested my scenario with mmWave Demo Visualizer and gotten the configure file. But how can I reuse those parameters in mmWave-Studio in order to capture raw data?
Thanks.
Hi Tom,
I've asked an expert to look into this and we should have an answer for you in the next few days.
Cheers,
Akash
Hi Akash,
What I do really care about is how to reuse paramters built with the Visualizer in mmWaveStudio. Would you please schedule a higher priotiry for that than figuring out the discrepancy between Visualizer and Estimator.
Thanks
Tom
Tom,
The desired value in visualizer actually translate to the closest calculated value of the config. So please check the generated config in the Visualizer and use that as input for the estimator.
Thanks
Yogesh
Yogesh,
Thanks for your replay, but paramters generated with Visualizer will result in errors when working with Visualiser. That's really confusing so that I don't know which one I should trust.
What I acttually want to do is to use the generated parameters with Estimator to capture raw data with the Studio. This can ensure paramters during the algorithm development are synchronized those in the production application.
Thanks
Tom
Hello Tom,
If you are using the Sensing Estimator then you can directly export the parameters as a JSON file. Then you can use this configuration in mmWave Studio by using the import JSON file feature. Please see the Studio user’s guide about the import JSON feature.
The online visualizer sliders are desired input values. The actual derived parameters from the generated cfg will be close to but not exactly the same values as the sliders. Furthermore the discretization used in the SDK demo can vary slightly from what is implemented in mmWave Studio- this is why for some corner cases that approach the bandwidth or timing limits you may see discrepancies in valid/invalid cfg.
Amanda