Warning: This feature is a work in progress in 2.8+. Expect stuff to be broken and breakages during usage.
-- zeffii
This node encapsulates several selected nodes (Ctrl+G) into a single node, similar to a shadertree node group.
There are two parts to this node,
- (Monad) the outer node shell "Monad", this Node is dynamically defined with new properties and sockets whenever required by the Tree inside.
- (Tree) the internal node tree, with its own input and output nodes. Interaction with the input and output nodes will update the "Monad" shell.
When editing the Tree you can
- rearrange sockets
- rename sockets
- set slider limits
- change socket types
Parameters
----------
The UI hints at a few fundamental features of the Monad:
- Vectorize , Vectorize with Split
- Loop n times
*Vectorize*
tries to match incoming datastreams by repeating data in those sockets that don't have the same number of internal lists.
*Vectorize with Split*
The more complicated this gets, the harder it is to explain in text. Please see some examples below.
*Loop n times*
This can be used for repeatedly applying an effect to a mesh, the number of iteration is currently only configurable via the node UI - it's too easy to accidentally grind your computer to a halt if that was set dynamically via an input socket.
- currently you must connect all named sockets,
- the input and output nodes must be fully connected and the arrangement/order of sockets must be consistent
connected like this::
start yes no
_____________ _____________ _____________
|_input_node _| |_output node_| |_output node_|
| verts o =------ ---------= o verts | --------= o edges |
| edges o =-------- -------= o edges | ------= o faces |
| faces o =---------- -----= o faces | ----= o verts |
| - - | - |
|_____________| |_____________| |_____________|
Inputs and Outputs
------------------
Are entirely defined by the Tree that Monad encapsulates
Example of usage
----------------
The github issue tracker has many issues (question and answers) regarding this node, it's a good place to start.
I suggest reading this: https://github.com/nortikin/sverchok/issues/863
@@ -134,7 +134,6 @@ It can be good idea to store as a preset (and maybe share) the following things:
* Scripted node, or "Mesh Expression" node, or one of other nodes that use
Blender's text blocks as settings. Such nodes are stored together with
corresponding text.
* Group (monad) node. It is saved with all contents.
* Several linked nodes, that do some completed thing, for later usage "as-is".
* Several linked nodes, that are "sort of going to be needed in this
combination often", so that later you can start with this preset and add some
...
...
@@ -385,14 +384,6 @@ Relax, most of these warnings can be ignored, unless the Tree fails to import, t
By all means if you like using this feature, file issues in `this thread <https://github.com/nortikin/sverchok/issues/422>`_. The best way to solve issues is to share with us a screenshot of the last few lines of the error if we need more then we will ask for a copy of the `.blend`.
Groups Panel
============
Crete a node group (Monad) from selection.
It can have vectorized inputs, adding or removing sockets.
Sverchok groups is a beta feature, use a your own risk and please report bugs. Also while it is in beta old node groups may break.
