![]() Generally, the links between the nodes are relationships that are known. So, let us assume the (x, y) coordinates of the nodes is known, and is as per the grid shown in the sketch. If the location of the nodes can be determined by some other process or procedure, then we can create this diagram using SGPLOT. Nodes and links count need not be the same. The links are shown as lines with link ids of 1-9. The nodes are shown as circles with node ids of 1-9. Say we want to create this simple diagram sketched on the right that I made from a display on the web. Note: The emphasis is on Simple Diagrams. But you have Base SAS, so let us see what we can do with the SGPLOT procedure and some Data Step coding to create simple diagrams. Many of you may not have a custom tool to create diagrams. Often we need to create some simple diagrams to visualize the connections between different entities such as patients and providers or even a social network. I'll keep everyone posted on visualization efforts.Let us continue with our journey beyond standard plots and charts. I plan to transition to NetJSON to describe this network as it, and the level of detail required, grow. But sometimes it's just a weird mermaid hiccup. In some ways I think this is beneficial, because it forces me to reconsider decisions and often the prettier topology seems the more effective. Not talking about a bug, its just ordered in a way I don't like and I feel forced to redefine the topology to create an easy-to-follow visual. The actual network topology is intermixed with visual data in the source.It doesn't look anything like a standard IT diagram, reducing perceived professionalism and ease of comprehension.I'm happy with it but there are a lot of issues. It would still require the new diagram type as described here, in #806, #867, #1527, etc.Įdit: Additional NetJSON visualizers, would be great to see Mermaid (or a Mermaid utility, rather) on this list one day.įor fun, I've attached a network topology design (pdf) I made in Mermaid. A utility to process NetJSON into Mermaid would be really useful. After all it's a diagramming tool, not a mapping tool. ![]() symbols we all know and love.īut back to my point, it seems the best tool to define networks is the well-established NetJSON, and Mermaid should be used to visually describe them. There's also netjsongraph.js which seems decent although (a) the site hosting the examples,, is down (apparently just for me) and (b) it also seems to be organic-only, and I don't see those fancy router/switch/PC/etc. ![]() I would prefer a non- or semi-hierarchical layout as others discussed. Their docs link to openwisp-network-topology as one implementation, but personally I don't really like the organic layout and it's really lacking the crispness of mermaid and other examples shared here ( is particularly good, and IP addressing individual connections is another awesome feature). However, NetJSON has pretty weak visualization tools. NetJSON describes the actual features of a network, such as "network configuration of devices, monitoring data, routing information, and network topology". I think its important to remember that network topologies are meant to describe networks. Somewhere in the rabbit hole this LibreOffice IT art pack was shared, which is quite stellar actually. I really appreciate you linking those other resources (diagrams.mingrammer, drawthenet).Īs well as the relevant issues linked and the other feature ideas (might be worth opening a new issue). -> trebleFilter -> trebleGain - -> gain - -> recorder - \n\ ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |