How to make a knowledge graph

0 votes
asked May 10 in Question / help by WaltHaas (120 points)

I'm trying to learn to use Blender which is complex software with many internal interactions.  To the frustrated student, it seems as if everything affects everything else.  To make life more difficult, basic words like "geometry" are often used to describe two or more different concepts with just enough similarity to be confusing.  So, as a good student, I'm taking notes in an effort to sort out what interacts with what.  Conceptually this seems like a knowledge graph. Plantuml doesn't have an explicit knowledge graph type, so I've been trying to fake it by using a state diagram.  In some ways an ER diagram or mind map might seem like a more logical base but the graph of Blender internal interactions is messier than that.  So far what I have come up with to start is:

title = Render Baking
Blender 4.1
May 10 2024
hide empty description
state Properties as "= Properties"
url of Properties is [[]]
state "Shader editor" as shader
state shader as "= Shader Editor"
url of shader is [[]]
state Outliner as "= Outliner"
url of Outliner is [[]]
Properties --> Scene : has property
state Scene
Scene -->render : has function
state "Render engine" as render
state Cycles
render --> Cycles : has engine
state "Render Baking" as bake #yellow
url of bake is [[]]
note right of bake
  FIXME indicate that if the
  object uses multires, select
  bake with multires
end note
Cycles --> bake : has function
state Mesh
bake --> Mesh : requires
state t <<choice>>
state Target
shader --> node : contains
state "Image texture node" as node
  node : node must be the active\nnode in the shader editor
  node : \nimage must be defined and refer\nto an existing or new image
note left of node
  FIXME margin
end note
state "Color Attributes" as attributes
Target --> t
t --> node : Image texture node
t --> attributes : Color attributes
bake --> Target : requires
state "UV map" as map
object --> map : has
bake --> map : requires
state "source object" as object
object : must be the active object\nand render must be enabled
Outliner --> object : has object
object --> Mesh : has
state Material
Mesh --> Material : requires
Properties --> Material : has property

leading to this:

I'm looking for suggestions to improve this.  In particular there are three top level abstractions indicated with bold type, and the diagram would be more readable if they could be hoisted to the top.  Ideas are welcome.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:

[Antispam2 Feature: please please wait 1 or 2 minutes (this message will disappear) before pressing the button otherwise it will fail](--------)
To avoid this verification in future, please log in or register.