The plebeian Graph Library

The plebeian Graph Library: A WebGL based network visualisation and diagnostics package - Published in JOSS (2024)

https://github.com/range-et/pgl

Science Score: 100.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 1 DOI reference(s) in JOSS metadata
  • Academic publication links
  • Committers with academic emails
    1 of 3 committers (33.3%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
    Published in Journal of Open Source Software

Keywords

data-visualization graph graph-theory visualization webgl

Scientific Fields

Engineering Computer Science - 33% confidence
Last synced: 4 months ago · JSON representation ·

Repository

The Plebeian Graph Library: A WebGL based network visusalisation and diagnostics package

Basic Info
Statistics
  • Stars: 4
  • Watchers: 1
  • Forks: 0
  • Open Issues: 1
  • Releases: 0
Topics
data-visualization graph graph-theory visualization webgl
Created almost 4 years ago · Last pushed over 1 year ago
Metadata Files
Readme Contributing License Code of conduct Citation

README.md

Introduction

The Plebeian Graph Library (PGL) is a library designed to facilitate the visualization of large-scale network data (Network X line plotting in Javascript/Typescript). Leveraging the power of WebGL, PGL offers an efficient and interactive solution for visualizing network data in web browsers (Tested on Firefox, Edge and Chrome). Whether dealing with local datasets or data retrieved from APIs, PGL provides a versatile platform for conducting extensive network simulations, physical modeling, and immersive visualizations. With a rich set of features including graph condensation based on selected criteria, randomized edge pruning in highly connected graphs, and support for diverse visualization techniques like network diffusions and Kamada Kawai layouts, and edge bundling, PGL empowers users to gain valuable insights from complex network structures.

Notes on terminology

It can be a bit confusing especially when working with Nodes/Edges/Vertices/Lines in this library (Also in general in working with graphs). Hence the terminology that I've followed here is as following:

  • Nodes (The library and the class is called _Node so as to not confuse with NodeJS ) and Edges make up a graph.
  • Vertices and Lines make up the 3d visualization side of a graph.
  • Nodes are the abstract idea, vertices are what's visualized
  • Edges are the abstract idea , lines are what's visualized. Lastly, there are a few helper classes like points and lines. Points are essentially vectors and are used for displacement and also for describing a place in relation to the global coordinate system. Line are an array of points that get translated into lines using one of the visualization methods. Points can have different visualizations like boxes, billboarded planes and cylinders etc.

Semantics of the Package

Existing network visualization libraries like NetworkX dictated the semantics of the graph library and borrowed some of the semantic ideas from three JS. The process is to define a Graph Object made of nodes and edges. Then modify this graph based on some set of properties. Then update the relevant settings. And lastly, to visualize the nodes, either as point clouds, boxes or cylinders, and to draw out the edges (bundled or not) lines. Here is an illustrated walkthrough of a simple set-up given a predefined set of “nodes” and “edges”.

Documentation

The documentation for the package is available at documentation

General setup of the package

Apart from the graph class all the methods are stored in variables. These variables (For example SampleData) would have a function attached to it that returns a value, or in some cases you can pass in values to do stuff (like displacing the graph etc). I mostly did this for the sake of speed to develop - at some point shall be wrapping them up as classes.

An example of rendering a basic graph

The general idea of drawing a basic graph is outlined above. To recap all the basic steps:

  • Get a graph (either generate it or get one using the sample data)
  • Create a graph drawing window (this is essentially a three js canvas)
  • Then add the elements like the nodes of the graphs using one of the many drawing options

```javascript // import the library import * as PGL from "plebeiangraphlibrary";

async function createVisualization() { // Load up the ZKC dataset const zkcSimulated = await PGL.SampleData.LoadZKCSimulated();

// Attach the renderer to a div which is on an HTML that the script is linked too const canvas = document.getElementById("displayCanvas"); // These are some basic options to set up a graph drawing object. Please refer to the documentation for more options const graphDrawerOptions = { graph: zkcSimulated, width: 800, height: 700, canvas: canvas, };

// Initialize a graph with these settings const graph3d = new PGL.GraphDrawer.GraphDrawer3d(graphDrawerOptions); await graph3d.init();

// Create the 3d elements for the graph // first describe a global scaling factor const bounds = 1; // Create all the geometry associated with node elements const nodeVisualElements = PGL.ThreeWrapper.DrawTHREEBoxBasedVertices( zkcSimulated, bounds, 0xffffff, 5 ); // add the node geometry to the scene graph3d.addVisElement(nodeVisualElements); // then create all the geometry associated with the edge elements const edgeVisualElements = PGL.ThreeWrapper.DrawTHREEGraphEdgesThick( zkcSimulated, bounds, 0xffafcc, 0.02 ); // add the edge geometry to the scene graph3d.addVisElement(edgeVisualElements);

// by default the camera revolves around the graph, trigger the animation call function animate() { requestAnimationFrame(animate); graph3d.rendercall(); }

animate(); }

createVisualization(); ```

Usage / Installation

Install it from the npm repository. Note that this method needs a npm folder to be set up with a build tool like parcel to package the visualizations

npm i plebeiangraphlibrary There is a boiler plate example of this in repository

Or head over to the GitHub, download the pgl_module.js Builds file and then start using it as a standalone module.

More examples

More examples are available at Examples Check them out as a demonstration of some of the features of the library.

Integrations

The plebeian Graph Library (PGL) is built on top of the ThreeJS library, seamlessly integrating its rich functionalities into a comprehensive and powerful toolset for large-scale graph data visualization. By leveraging the foundation provided by ThreeJS, PGL inherits a wide range of features, including advanced shading techniques, texture mapping capabilities, and much more. These powerful rendering capabilities enable PGL to create visually stunning and immersive graph visualizations, adding depth and realism to the representation of complex network structures. With its symbiotic relationship with ThreeJS, PGL empowers users to go beyond traditional graph visualizations, unlocking a world of possibilities for exploration and analysis.

Benchmarking

A performance benchmark conducted against D3, an industry-standard visualization library, showcases PGL's capabilities. In this test involving approximately 5000 nodes and 200000 edges, D3-based SVG graphs only achieved a frame rate of 1.5 frames per second, bottoming at a frame every two seconds with a maximum of 12 frames per second. In contrast, PGL maintained a minimum of 52 frames per second and averaging 58 frames per second under similar conditions. This benchmark, performed on both Firefox and Chrome browsers (with negligible differences in performance) on a computer with an Nvidia RTX 2080 GPU, highlights PGL's superior performance and efficiency in rendering complex network visualizations. The benchmarking files are available under benchmarking for the D3 project and the PGL example can be accessed under Examples / 3_LargePointCloud.html

Contributing

Contributions are welcome to the plebeian Graph Library (PGL)! Whether you're fixing a bug, adding a feature, improving documentation, or spreading the word, your contribution is valuable. Here's how you can get involved:

  • Reporting Issues: If you encounter any bugs or issues, please report them in the Issues section of our GitHub repository. Provide as much detail as you can, including steps to reproduce the issue.

  • Submitting Changes:

    • Fork the repository on GitHub.
    • Clone your forked repository to your local machine.
    • Create a new branch for your feature or bug fix.
    • Make your changes and test them.
    • Commit your changes and push them to your fork.
    • Submit a pull request back to the main repository. In your pull request, describe the changes and link to any relevant issues.
  • Seeking Support: If you have questions or need help integrating PGL into your project, feel free to reach out on the GitHub issues page, I shall be more than happy to help out there.

  • Improving Documentation: Good documentation is crucial for any project. If you see an area that needs improvement or have ideas for new content, don't hesitate to reach out and open an issue.

Also remember to check out the contributions file where there are more details on how to contribute to the project.

Remember to follow our Code of Conduct to ensure a welcoming and inclusive environment for everyone

Acknowledgements

This library was sponsored by the Geometry Lab under the Laboratory for Design Technologies at the Graduate School of Design, Harvard University. Many thanks to Andrew Witt for guiding this project. This project was developed by : Indrajeet Haldar

Owner

  • Name: Indrajeet Haldar
  • Login: range-et
  • Kind: user
  • Location: Cambridge, MA

JOSS Publication

The plebeian Graph Library: A WebGL based network visualisation and diagnostics package
Published
April 25, 2024
Volume 9, Issue 96, Page 5887
Authors
Indrajeet Haldar ORCID
Graduate School of Design, Harvard University, USA
Editor
Mark A. Jensen ORCID
Tags
Visualisation Graphs Networks

Citation (CITATION.cff)

cff-version: "1.2.0"
authors:
- family-names: Haldar
  given-names: Indrajeet
  orcid: "https://orcid.org/0000-0001-8395-6056"
doi: 10.5281/zenodo.10871132
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Haldar
    given-names: Indrajeet
    orcid: "https://orcid.org/0000-0001-8395-6056"
  date-published: 2024-04-25
  doi: 10.21105/joss.05887
  issn: 2475-9066
  issue: 96
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 5887
  title: "The plebeian Graph Library: A WebGL based network
    visualisation and diagnostics package"
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.05887"
  volume: 9
title: "The plebeian Graph Library: A WebGL based network visualisation
  and diagnostics package"

GitHub Events

Total
  • Watch event: 2
Last Year
  • Watch event: 2

Committers

Last synced: 5 months ago

All Time
  • Total Commits: 72
  • Total Committers: 3
  • Avg Commits per committer: 24.0
  • Development Distribution Score (DDS): 0.056
Past Year
  • Commits: 0
  • Committers: 0
  • Avg Commits per committer: 0.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Indrajeet i****8@g****m 68
Indrajeet Haldar i****8@g****m 3
Daniel S. Katz d****z@i****g 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 4 months ago

All Time
  • Total issues: 5
  • Total pull requests: 1
  • Average time to close issues: 3 months
  • Average time to close pull requests: about 12 hours
  • Total issue authors: 2
  • Total pull request authors: 1
  • Average comments per issue: 0.8
  • Average comments per pull request: 0.0
  • Merged pull requests: 1
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 1
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 1
  • Pull request authors: 0
  • Average comments per issue: 0.0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • abhishektiwari (3)
  • RedWilly (1)
Pull Request Authors
  • danielskatz (2)
Top Labels
Issue Labels
Pull Request Labels

Packages

  • Total packages: 2
  • Total downloads:
    • npm 1 last-month
  • Total dependent packages: 0
    (may contain duplicates)
  • Total dependent repositories: 0
    (may contain duplicates)
  • Total versions: 6
  • Total maintainers: 1
npmjs.org: plebiangraphlibrary

A NetworkX like package for graphs in javascript

  • Versions: 5
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Downloads: 0 Last month
Rankings
Downloads: 6.2%
Forks count: 14.9%
Stargazers count: 16.1%
Average: 23.8%
Dependent repos count: 33.7%
Dependent packages count: 48.0%
Maintainers (1)
Last synced: 4 months ago
npmjs.org: plebeiangraphlibrary

A NetworkX like package for graphs in javascript

  • Versions: 1
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Downloads: 1 Last month
Rankings
Dependent repos count: 33.1%
Average: 40.1%
Dependent packages count: 47.1%
Maintainers (1)
Last synced: 4 months ago

Dependencies

.github/workflows/draft-pdf.yml actions
  • actions/checkout v3 composite
  • actions/upload-artifact v1 composite
  • openjournals/openjournals-draft-action master composite
benchmark/package-lock.json npm
  • 265 dependencies
benchmark/package.json npm
  • parcel ^2.11.0 development
  • d3 ^7.8.5
package-lock.json npm
  • 615 dependencies
package.json npm
  • @parcel/packager-ts ^2.9.1 development
  • @parcel/transformer-typescript-tsc ^2.9.1 development
  • @parcel/transformer-typescript-types ^2.9.1 development
  • @types/three ^0.136.1 development
  • express ^4.18.2 development
  • jest ^29.7.0 development
  • jest-image-snapshot ^6.4.0 development
  • jsdoc ^4.0.2 development
  • parcel ^2.9.1 development
  • pixelmatch ^5.3.0 development
  • pngjs ^7.0.0 development
  • puppeteer ^21.7.0 development
  • shelljs ^0.8.5 development
  • typedoc ^0.24.8 development
  • typescript ^5.1.3 development
  • three ^0.141.0