#higraph — Public Fediverse posts

#Higraph progress!

Still got lots to do, but hyperEdges can now be saved & loaded in modified #graphml files. The "model tree" on the left highlights items in the graph on the right.
I can see "minimum viable product"!

The #hyperedge structure is both graphically and algebraically accessible. I'm not aware of anything else that does this, pretty certainly not in #Python
#graphTheory #VisualFormalism

#Higraph progress!

Still got lots to do, but hyperEdges can now be saved & loaded in modified #graphml files. The "model tree" on the left highlights items in the graph on the right.
I can see "minimum viable product"!

The #hyperedge structure is both graphically and algebraically accessible. I'm not aware of anything else that does this, pretty certainly not in #Python
#graphTheory #VisualFormalism

#Higraph progress!

Still got lots to do, but hyperEdges can now be saved & loaded in modified #graphml files. The "model tree" on the left highlights items in the graph on the right.
I can see "minimum viable product"!

The #hyperedge structure is both graphically and algebraically accessible. I'm not aware of anything else that does this, pretty certainly not in #Python
#graphTheory #VisualFormalism

#Higraph progress!

Still got lots to do, but hyperEdges can now be saved & loaded in modified #graphml files. The "model tree" on the left highlights items in the graph on the right.
I can see "minimum viable product"!

The #hyperedge structure is both graphically and algebraically accessible. I'm not aware of anything else that does this, pretty certainly not in #Python
#graphTheory #VisualFormalism

#Higraph progress!

Still got lots to do, but hyperEdges can now be saved & loaded in modified #graphml files. The "model tree" on the left highlights items in the graph on the right.
I can see "minimum viable product"!

The #hyperedge structure is both graphically and algebraically accessible. I'm not aware of anything else that does this, pretty certainly not in #Python
#graphTheory #VisualFormalism

#Higraph update.
My wife has been squashing bugs and added an awesome hierarchical view of the blobs (sets).
#Hyperedges still need work, but this is getting tantalisingly close to a usable tool!

#Python #pyside6

#Higraph update.
My wife has been squashing bugs and added an awesome hierarchical view of the blobs (sets).
#Hyperedges still need work, but this is getting tantalisingly close to a usable tool!

#Python #pyside6

#Higraph update.
My wife has been squashing bugs and added an awesome hierarchical view of the blobs (sets).
#Hyperedges still need work, but this is getting tantalisingly close to a usable tool!

#Python #pyside6

#Higraph update.
My wife has been squashing bugs and added an awesome hierarchical view of the blobs (sets).
#Hyperedges still need work, but this is getting tantalisingly close to a usable tool!

#Python #pyside6

#Higraph update.
My wife has been squashing bugs and added an awesome hierarchical view of the blobs (sets).
#Hyperedges still need work, but this is getting tantalisingly close to a usable tool!

#Python #pyside6

You asked, and here it is: #hyperedges are basically working. 1200 lines of code & changes in 2 weeks - about 50 odd hours of coding. This was not trivial, but hyperedges are a thing.

There are still some features to add (deletion, XML serialisation), and bugs to squash, but the hard work is done.
😁

#Python #Higraph #GraphTheory #PYside6

You asked, and here it is: #hyperedges are basically working. 1200 lines of code & changes in 2 weeks - about 50 odd hours of coding. This was not trivial, but hyperedges are a thing.

There are still some features to add (deletion, XML serialisation), and bugs to squash, but the hard work is done.
😁

#Python #Higraph #GraphTheory #PYside6

You asked, and here it is: #hyperedges are basically working. 1200 lines of code & changes in 2 weeks - about 50 odd hours of coding. This was not trivial, but hyperedges are a thing.

There are still some features to add (deletion, XML serialisation), and bugs to squash, but the hard work is done.
😁

#Python #Higraph #GraphTheory #PYside6

You asked, and here it is: #hyperedges are basically working. 1200 lines of code & changes in 2 weeks - about 50 odd hours of coding. This was not trivial, but hyperedges are a thing.

There are still some features to add (deletion, XML serialisation), and bugs to squash, but the hard work is done.
😁

#Python #Higraph #GraphTheory #PYside6

You asked, and here it is: #hyperedges are basically working. 1200 lines of code & changes in 2 weeks - about 50 odd hours of coding. This was not trivial, but hyperedges are a thing.

There are still some features to add (deletion, XML serialisation), and bugs to squash, but the hard work is done.
😁

#Python #Higraph #GraphTheory #PYside6

This image is of a simulation of a simple directed #hypergraph , but using an n-ary line rather than a set for the #hyperedge

I have written a working #graphTheory editor for binary edges, where nodes are extended to sets (a #Higraph) , and am contemplating the complexity of n-ary edges with increasing apprehension. It requires refactoring just about the entire edge drawing codebase - 100's of changes across ~2000 lines of #Python.
Is it worth it? Please comment/ vote in the poll below

This image is of a simulation of a simple directed #hypergraph , but using an n-ary line rather than a set for the #hyperedge

I have written a working #graphTheory editor for binary edges, where nodes are extended to sets (a #Higraph) , and am contemplating the complexity of n-ary edges with increasing apprehension. It requires refactoring just about the entire edge drawing codebase - 100's of changes across ~2000 lines of #Python.
Is it worth it? Please comment/ vote in the poll below

A #Higraph milestone: Blobs (nodes as sets) now work! Grab a 'parent' blob, and all the children move. Edges connect anywhere on the blob, and default to be orthogonal to the point of contact. graphML read and write working.

Now on to proper hyperedges!

#Python #Pyside6 #Qt #GraphTheory

A #Higraph milestone: Blobs (nodes as sets) now work! Grab a 'parent' blob, and all the children move. Edges connect anywhere on the blob, and default to be orthogonal to the point of contact. graphML read and write working.

Now on to proper hyperedges!

#Python #Pyside6 #Qt #GraphTheory

A #Higraph milestone: Blobs (nodes as sets) now work! Grab a 'parent' blob, and all the children move. Edges connect anywhere on the blob, and default to be orthogonal to the point of contact. graphML read and write working.

Now on to proper hyperedges!

#Python #Pyside6 #Qt #GraphTheory

A #Higraph milestone: Blobs (nodes as sets) now work! Grab a 'parent' blob, and all the children move. Edges connect anywhere on the blob, and default to be orthogonal to the point of contact. graphML read and write working.

Now on to proper hyperedges!

#Python #Pyside6 #Qt #GraphTheory

A #Higraph milestone: Blobs (nodes as sets) now work! Grab a 'parent' blob, and all the children move. Edges connect anywhere on the blob, and default to be orthogonal to the point of contact. graphML read and write working.

Now on to proper hyperedges!

#Python #Pyside6 #Qt #GraphTheory

Hi #Mathstodon - a #GraphTheory question:
Given the following visual set containment, I can obtain the total containment of every item as a list (text on the left). This intuitively seems sufficient information to derive the containment graph (almost a tree - n7 breaks that).
Are there any 'standard' techniques to apply to this?

Boosts, partial ideas, discussion all welcome.
#Higraph

Hi #Mathstodon - a #GraphTheory question:
Given the following visual set containment, I can obtain the total containment of every item as a list (text on the left). This intuitively seems sufficient information to derive the containment graph (almost a tree - n7 breaks that).
Are there any 'standard' techniques to apply to this?

Boosts, partial ideas, discussion all welcome.
#Higraph

@MrBerard #Higraph editor question:
So far, it has been possible to round trip models from my tool into yEd and back. I'm now developing more higraph specific functionality that they don't explicitly support. But the graphML spec has a very _similar_ idea (nested graphs). Is it worth the effort to save higraphs in an "approximately round-trippable" format, or just leave yEd behind?
Thoughts welcome!

If I did everything right, I have a public alpha release of my graph (nodes and edges) editor
With source and windows binary !
(I hope)
It's a rolling chassis, to explore the design patterns for the ultimate goal of a #higraph editor.

#Python #PySide6 #graphTheory

https://github.com/ghillebrand/qtPyGraphEdit/tree/v0.0.0-alpha

If I did everything right, I have a public alpha release of my graph (nodes and edges) editor
With source and windows binary !
(I hope)
It's a rolling chassis, to explore the design patterns for the ultimate goal of a #higraph editor.

#Python #PySide6 #graphTheory

https://github.com/ghillebrand/qtPyGraphEdit/tree/v0.0.0-alpha

I was looking for an icon for the Version 00 release of my #Higraph tool, and remembered that my 1999 version had one.
I had to fire up a #WIndows98 VM, and access the files via IE5 and XAMPP on my PC, but here it is. Zipfile with full system is there for your download pleasure!

#retrocomputing

https://isijingi.co.za/wp/2025/07/14/a-blast-from-the-past-1999-version-of-higraph/