-
Notifications
You must be signed in to change notification settings - Fork 118
Wave source hierarchy browser #216
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
Comments
After speaking with @azonenberg I will post some commercial examples as well. Here is Cadence's Visualization tool showing a quite busy setup with SPICE data: |
Anybody have a screenshot of VCS for reference? The only ones I have are full of customer data and I can't share. |
Maybe these are from VCS? openhwgroup/cvfpu#24 (comment) |
azonenberg
added a commit
that referenced
this issue
Aug 26, 2024
azonenberg
added a commit
that referenced
this issue
Aug 26, 2024
azonenberg
added a commit
that referenced
this issue
Aug 26, 2024
azonenberg
added a commit
that referenced
this issue
Aug 26, 2024
…ragging, preventing a drag from starting. See #216.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to support sources with a lot of channels, it is inevitable that glscopeclient will have to offer some sort of interface to select and add a lot of channels at once. Right now this is done by the "Add" menu, which works pretty well for a few channels commonly used on analog scopes.
The most extreme examples I can think of are SPICE simulations which can easily have thousands of nets in the results,
I made an example SPICE waveform here: lots-of-inverters.tar.zst. It contains a 300MB SPICE simulation of some hundred inverters in a 2-level hierarchy.
Some inspiration from GTKwave here:

Other simulation tools usually have something similar, a type of "filesystem" folder/trace structure that allows navigation. Some viewers have a flat hierarchy but allowing you to filter.
For VCD and FST the folder-hierarchy maps really well as they are hierarchical anyway. For SPICE data they are more implicit, like this:
The text was updated successfully, but these errors were encountered: