feature: timing diagram
See original GitHub issueThis is a feature Request for a new chart type “Timing Diagram”.
“A digital timing diagram is a representation of a set of signals in the time domain. A timing diagram can contain many rows, usually one of them being the clock. It is a tool that is commonly used in digital electronics, hardware debugging, and digital communications.” - via wikipedia
image CC-BY-SA-3.0 based on image by garrett-mcclure via electronics.stackexchange.com
This chart type should support the following features:
- x-axes: normal number but also timing-series.
- y-axes can only have values
false/true
or0/1
. - The area underneath each “1” signal can be filled with a color (in red above).
- every signal (y-axes) has a baseline (same as “0”) (in green above).
- It should be possible to use this chart-type as a subplot.
- series can have different names, colors …
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Timing Diagram - an overview | ScienceDirect Topics
Timing diagram is used to show interactions when a primary purpose of the diagram is to reason about time; it focuses on conditions...
Read more >What is Timing Diagram? - Visual Paradigm
Timing diagrams focus on conditions changing within and among lifelines along a linear time axis. Timing Diagrams describe behavior of both individual ...
Read more >Timing Diagram syntax and features - PlantUML
PlantUML Timing diagram syntax: Timing diagrams are not fully supported within PlantUML. This is a draft version of the language can be subject...
Read more >Timing Diagram Tutorial - Lucidchart
Timing diagrams show how long each step of a process takes. Use them to identify which steps of a process require too much...
Read more >UML Timing Diagrams - Overview of Graphical Notation
Timing diagrams focus on conditions changing within and among lifelines along a linear time axis. Timing diagrams describe behavior of both individual ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m thinking of merging all new trace type request like this one in https://github.com/plotly/plotly.js/issues/2221 until we start work on them.
Sounds ok @alexcjohnson ?
I’ve seen plenty of charts like this with some of the signals analog. Wouldn’t need to be included from the outset but we shouldn’t preclude it.
This could of course be created already using one subplot and one trace for each signal, but I can see the argument for making it a single trace: it would have better performance, much cleaner API, and the interactions could be tailored to this use case.