-
Notifications
You must be signed in to change notification settings - Fork 35
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
How to convert waterfall saved in .npy (kiwiwfrecorder) to image ? #77
Comments
The relevant lines are Lines 106 to 120 in 4f9490e
The .npy files contains:
|
Hey! How do we decode the WF data into a simple waterfall? Very confused here, need to figure out what's actually in the WF data. Doesn't seem to be documented anywhere either. |
There is no kiwiclient code to directly convert waterfall data streamed from a Kiwi to an image file. Note that you can do this with the Kiwi web interface itself: "save waterfall as jpg" in the right-click menu. But I imagine you're probably interested in automating the process using kiwiclient. Most of the pieces of Python code to do it are already in the kiwiclient package. Someone just needs to put it together. There are three issues with generating waterfall image files:
None of the Kiwi API is formally documented. But the Colormap mapping is a complicated topic. The Kiwi code has all sorts of different schemes. On top of that are the various waterfall averaging options. All of this needs to be considered because what kiwirecorder sees is the raw WF data with none of this processing. The Kiwi code does all WF processing on the client-side in Javascript. So you have to decide how much of that you want to replicate. At the very least you need to copy one of the static colormaps from the The |
Fixed, finally! Have a look at the new kiwirecorder waterfall options: --wf-png --wf-auto --mindb --maxdb (and the old --z --speed) |
So I have some data in .npy recorded with kiwiwfrecorder.py
How convert it to image file ?
Any tools or python code or example ?
Thanks in advanced,
The text was updated successfully, but these errors were encountered: