Hi All,

Development of node Editor has appeared to have stalled.
In the interest in pushing things along, I am going to post a series of proposals for new nodes that I believe would have great utility.

I'm afraid that I lack the skills to actualise the proposed nodes myself. I'm hoping that the interest of some of you coding geniuses might be piqued.

If anyone else harbours dreams of missing nodes, please add to this thread.

All the best
James
https://www.instagram.com/nodeology/

Image Sampler Node.

This node would have an input for a ptArray and an Output of a numArray.
The info panel would have a field for entering the url of image to import.

The point array input may be a regular grid or an offset grid for greater control;
the number of points in the array determining the length of the numArray output.
At each point the greyscale value would be sampled and output as a numArray
between 0,255 (8bit)

These values could be reconfigured to fall within any range with “reRange” node,
and could then be the "radius" input for "circle" node, (like shown) or the "index"
input for the "setStyle" node for colorising.
Alternatively, the image may be a bump map and the numArray be z values of a
terrain surface loft.

In terms of how to approach such a task, I would say that the existing heightMap
& rasterImage scripts by Max would be a good starting point.


James
https://www.instagram.com/nodeology/

Step Node

Here I'm not proposing a new node, so much as, new option for the "knob" widget.

There are a lot of instances where it is desirable to dial through number at a
set increments, eg 15 degrees steps of rotation.
One example that arises often is for only even or only odd numbers.

The work-around for achieving this result is not difficult, but it is clumsy compared to
having the graduations builtin.

James
https://www.instagram.com/nodeology/

subD Classic Node

Ultimately this is a proposal for a new mode for the subD node,
though in the interim it could be a separate node.

The node would be analogous to Max's SubdivClassic script.
One big advantage of the facetted output of SubdivClassic is that,
it is the basis for a panelling system with "Flow" node.



James
https://www.instagram.com/nodeology/

Voronoi Node

The node would have 2 inputs: a series of points and a boundary curve and
output a noronoi pattern.

This would be analogous to Max's Voronoi script (http://moi.maxsm.net/item/48), however the options of
"Corners" and "Spacing" would not need to be included because there are already
nodes that can perform these functions.


James
https://www.instagram.com/nodeology/

PS for further background to Max's Voronoi script see this forum thread:
http://moi3d.com/forum/index.php?webtag=MOI&msg=7177.1

Hello James
For the repository
Have you some lights about some Arrays yet existing nodes that I have not yet described ?
Because I am in total dark about that!
http://moiscript.weebly.com/arraysext.html

Idem for these sections! Basics2 ( Loops) - Vectors - and some little dark black holes! :)

James...your contributions are always...AMAZING!!!

Congrats!!!

Delaunay Node

Node has a input for points and generates an output of connection lines as a Delaunay Triangulation.


James
https://www.instagram.com/nodeology/

It's the grouping for these nodes that give a simulation of a Delaunay function
or the Delaunay node is a new function node itself ?

Pilou,

>> It's the grouping for these nodes that give a simulation of a Delaunay function
or the Delaunay node is a new function node itself ? <<

The proposed new node is the one titled "Delaunay" in my earlier post.
The other nodes only show how the point input may be generated.

As I understand it, the Delaunay triangulation is a precursor to generation of voronoi
diagram and hence should be solvable. However unlike the voronoi points that are
restrained to 2D plane, Delaunay triangulation would ideally operate on points in 3d space.
Hopefully this would not make the task much more onerous.

James
https://www.instagram.com/nodeology/

so who is coding nodes (except Max, r2d3, Karsten...

Because I am really stuck on my repository for understand "this node made what ?" ! :)
I make an s o s ! :)

80% are done but the 20 % missing is total fog! :)

So help ! ... _ _ _ ... :)

Spiral Node

This would be fairly low down in the order, given until Michael post of today,
I had not even thought about the need for a spiral node. Defining a spiral with
a set of points with locations determined by a bit of trigonometry is not difficult,
it would nevertheless be worth having a dedicated node since being an existing
UI function should be relatively straightforward to transpose the code into a node.




James
https://www.instagram.com/nodeology/

I suppose existing spiral scripts could be converted into nodes.
- Brian

James,

For testing purposes:

Insert the Spiral.txt code on Curves2.js after the Helix Node.

This will add a Spiral Node to the Curves2 listing.

Added a spiraltest.nod for testing.

Waiting to see some nodeology art with this new node...

Wayne

Nobody for my SOS ? Encalaminated in the Sargasso Sea! :)

You will can see easily what are the "holes" !

http://moiscript.weebly.com/biblio-elephant.html

Wayne,

Thank you so much for your spiral node contribution.
It works perfectly....& multi-processing too!
Great Work.

>> Waiting to see some nodeology art with this new node... <<

I have uploaded a new pattern transition Animation to instagram
utilising your new node: https://www.instagram.com/p/B5QySEDJTIl/

Thanks again,
James
https://www.instagram.com/nodeology/


UPDATED:

PS If I could be so bold as to suggest an improvement, it would be
to remove the "Reverse" checkbox and instead allow negative "Turns" inputs,
with line of code asking something like:
"if turns < 0, then reverse = true, else reverse =false:
turns = abs(turns);"

In this way transitions can go from spiralling in one direction to the other.

A problem that arises with a number of nodes when dialling from a negative number to a positive number (or vice versa) is that a zero input will not be accepted and so an extra line of code would be useful:
"if turns == 0, then turns = 0.001;"

Unfortunately I'm not a coder, so obviously I am not stating that these are 2 lines of javascript, but rather, only their intent.

James,

The nodeology art looks great! The reverse direction should be a easy change.
The division by zero goes off into infinity. It also will be addressed.

Thank you for testing.

Wayne

James,

Updated the Spiral Node for reverse direction (0 or 1). Could you provide more information on the error you are getting with the negative values?

Are you able to enter the same information on the MOI UI for the flat helix without error? This node is using the MOI API for the helix / flat spiral.

Wayne

Wayne,

>> Could you provide more information on the error you are getting with the negative values? <<

I'm not getting an error message, however the spiral disappears for any "Turns" value less than 0.01 or negative. This is logical for the MoI3d UI but less so for NE particularly with multiprocessing applications.

Have a look at the attached .nod file. It might better explain my meaning from earlier suggestion of improvement to spiral node. Firstly, dial through the GREEN knob from min-max.

In the upper example the spiral disappears when the knob for "Turns" input is dialled below 0.01, whereas the lower example works throughout the range from -5to5 with the addition of a rather clumsy workaround.

It is perhaps not that straightforward, but if you look at the math & compare nodes on the lower example. I was suggesting incorporating analogous code into the Spiral node and removing any reference to "Reverse" from the info panel or the node itself for that matter. Which is to say, that the negative or positive property of the "turns" value, alone, would designate the direction of twist.

Thank you for all your your effort
James
https://www.instagram.com/nodeology/

Hello Pilou,

an example of bundleArray - here for points. It takes points from the input and bundle it to packages in the output array. Here the first point of each input and so on.
Works also for numbers and objects.

Have a nice day
and thanks for your work on it!

Karsten