The goal of this project is to make a programming language align with human perception at best, while being powerful with the help of Python, its backend.
Compatibility:
- Python 3.11
- Chrome browser (Grapycal is laggy on Safari; FireFox is not tested.)
Visit our wiki page for documentation.
# Requires python 3.11
pip install grapycal grapycal-builtin
grapycal # Grapycal will open at localhost:9001If you have any questions or ideas to share, feel free to join the Discord server.
Grapycal is still in its early stage. Any contribution is welcome! Currently, most of our efforts are on the backend (the core of Grapycal) and extensions (nodes with various functionalities), but it's also helpful to improve the frontend and the documentation.
To contribute, please refer to the Contribution Guide to get started. The Project Board contains the current plans for Grapycal and is a good place to start.
Feel free to join the Discord Server to discuss with us.
-
Interactive: On the GUI, users can run different parts of the graph in arbitrary order, watch variables in real-time, and easily track the active node while the program runs.
-
Dynamic: Grapycal allows users to modify the running graph for instant changes in its behavior. That includes adjusting parameters, adding or removing nodes from a workflow, and terminating a loop.
-
Extendable: Grapycal provides a set of API for creating custom nodes for arbitary domain, such as deep learning, robotics, or music synthesis.
-
Collaborative: Custom nodes definitions can be shared as Python packages. Thus, nodes for various domains can be mixed in a graph to form a powerful tool or a creative artwork (I’ll create some examples when I have time). What’s more, Grapycal supports real-time collaboration, allowing a group of people to work on the same graph over the Internet.
Grapycal is not (yet):
-
Fast: Grapycal is yet another layer of abstraction on top of Python. Some overhead is introduced for its interactivity and dynamics. However, the overhead would be relatively small if the graph doesn’t run at a high frequency ( less than ~1000 node runs per second ). For example, if your program mainly computes with C extensions (such as NumPy) or uses GPU heavily (such as deep learning tasks), there will be little impact on performance.
-
Stable: Grapycal is not heavily tested to ensure the graph always runs as expected.
In our daily lives, countless ideas emerge in our minds, only to be dismissed because the perceived cost of realizing them is too high. Over time, sadly, we tend to forget our inherent creativity.
The mission of Grapycal is to push more ideas over the line to be worthy of trying out.
Grapycal is helpful for conducting experiments, including training AI, physical simulations, data analysis, computer art, and more. These experiments require repeated parameter adjustments, swapping certain components of models, while simultaneously observing the phenomena generated by different parameters. We then use human judgment combined with domain knowledge to deduce the best model or other conclusions.
In this back-and-forth process between humans and machines, using traditional Python execution methods or Jupyter notebooks can be cumbersome. Therefore, we need the higher interactivity provided by Grapycal.
Grapycal and its dependences consist of the following 6 packages:
-
Grapycal/backend: Included in this repo, including the backend code of the Grapycal main application
-
Grapycal/frontend: Included in this repo, including the frontend code of the Grapycal main application
-
Topicsync and ObjectSync: Backend dependencies. Python packages.
-
topicsync-client and objectsync-client: Frontend dependencies. npm packages.
Grapycal is inspired by these amazing projects. Also take a look at them
-
Unity shader graph
-
Blender node editor
These tools or libraries help Grapycal a lot:
