Full Version: Nodebundle for playing with nodes

Show messages:  1-18  …  1659-1678  1679-1698  1699-1718  1719-1738  1739-1758  1759-1778  1779-1798  …  1859

Thread Split: Some posts in this thread have been moved here

Max,

"could you send me the nod-file? I'll try to find a solution."

I have attached .nod file, but please don't spend any of your precious time
trying to find another solution, I'm happy with existing solution.

---

While pondering the NE interface design, I had a thought.

I was wondering if the wires between nodes could be different to graphically communicate the nature the data flowing through them. I should preface this by saying that this is not a request, more a question of possibilities.

The image below shows 3 examples of point data: (1) a point, (2) multiple points & (3) ordered point sequence with a ranges of wire types to reflect the particular data type.



Similarly, the wires may vary for single numbers and numArrays, as well as to denote single objects and collections of objects.

Again, I'm not asking for this to be done, but rather wanting to know your thoughts on the future development of NE; whether this was even a possibility.

Perhaps even more useful for debugging node circuits might be a wire type that indicates that indeed no data is flowing through a wire.

UPDATED:

Another suggestion of UI enhancement might be to include set of dots at top right corner of node to indicate that it is a multi-mode node. It is a well established interface convention that requires no explanation. Also there may be some value in grouping the multi-mode nodes under a single heading: "General".



Of course it would appropriate for some multi-mode nodes to reside within other groupings. Several of the "Points" nodes could be folded into the "Transform" nodes, e.g."Move" "Rotate" & "Scale" node could all have modes for "Objects" as well as "Points".

The ability for a single node to operate on a number of different data type is one area where NE is superior to GH (Grasshopper)


Anyway, I am so appreciative that you are working again on NE,
& will be onboard with any direction you choose to take it.
James
https://www.instagram.com/nodeology/

Attachments:
shapeSurfOutput.nod

Image Attachments:
dot:dashLines.gif  GeneralMenu.gif 

---

Hi, everybody.
New nodes: Box, Box Center, Box3pts.

Attachments:
box.nod
boxHelix.nod
wnSolids.js

Image Attachments:
box.PNG  boxHelix.PNG 

---

Hello Karsten,

Hope you are well.

I have been trying over and over to create a recursive pattern with your loop nodes (loopStart & loopEnd), but I can't get my head around how to set it up.
I have search the forum for an example of looping, to no avail.

I would greatly appreciate, when you have a free moment, if you could post a super simple example of the nodes in use, so that I may use as reference, for building something more complex.

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

---

Looking at hoopsnake may help. (?)

Google search of "hoopsnake examples"

Laying bricks example pdf:
https://www.researchgate.net/publication/332834996_Loops_in_Grasshopper

https://www.youtube.com/watch?v=gpv5prTmcjo

- Brian

A processed component gets feed back into the "start" of the node program, with some termination method...

(cannot say that I understand it. It would be nice to identify the inputs and outputs of Karsten's program, and compare with the hoopsnake inputs and outputs...(or the other two methods).

---

Hello James,

busy job, mother is gone - weather is good, beer is cold and the liver grows with its tasks - that's life.

Nevertheless - Loop.
The Loop implementation is very basic and limited to one loop, because there is only one array for storing the feedback data. You can find the declaration in basicFunctions.js in the first lines for numbers points and objects.
With this arrays is the feedback realized so you don't have to wire back something in the canvas - by the way, it's also not possible like in GH.
How it works:
The LoopStart node takes the initial data to the initial connection- a numarray, points or objects - you can set it with the RMB. At the Trigger input you have to put a cycled quartz node that kicks the process again and again. In the first cycle LoopStart takes the initial data and put it to the output. You have to take now this data, do someting with it and give them to the LoopEnd. Loop End stores them in the mentioned array. In the following cycles loopStart checks if it is a first cycle or not - if not it takes the data from the array. It is possible to RESET the node by RMB. This would run now forever - so we need also a termination condition that stops the manipulation of your looped data. So you have evaluate something from your data - compare someting or get the number of object ... and feed the result in the Run input of the LoopEnd node. If you put in a 1 here, the data will be put back to the LoopStart otherwise not and the manipulation stops or better the manipulation cycle takes allway the same data.


I've took my old post to explain it on this example:
http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.1382
Try GetInTouch.nod.
Here is the start object a small cone. LoopStart takes it and put it to the out. Then the cone is moved a little bit. With a intersection node I check if the objects create a clash. This is my termination criteria. So no Intersection - no Objects. I take the Length of the objectlist and check if it is 0, If yes the process starts again with the new position of the cone. If a clash is detected the process stops and with a tolerance of the movement I brought the cone in touch with the sphere.

I Hope you can do something with it - allways a pleasure to see your results!

Have a nice day
Karsten

---

Hello Karsten,

Thanks so much for getting back to me.

I have almost got it work, but I'm not sure if recursion is possible
because the end result of a transformation (in this case: scale by 0.5)
does not replace initial object.



Another problem I have encountered is that my nodes do not have object input/outputs.
See in image above. The dark nodes are loaded with your nod file, while the light ones
are those inserted from my node menu.

I tried reinstalling the posted files (loop.js & basicFunctions.js), and quitting/reopening MoI3D/NodeEditor; but the issue persists....curious!
Any idea what could be causing this?

Have a great weekend,
James
https://www.instagram.com/nodeology/

Attachments:
loopTest.nod

Image Attachments:
loopTest.gif 

---

Hello James,

in short, because I have an appointment now. Try right click on the node to switch to objects and think about switching the compare node to a|b. I'm not sure what the result should be. Maybe more in the evening (CET).

Have a nice day
Karsten

---

UPDATED

Thanks Karsten,

How profoundly stupid of me not to have checked to see if the node had alternate modes.

I was trying to make an H-Tree Pattern, only as a first step in exploring recursive patterns.
just as Wayne has done here: http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.1702

However, this would only be a starting point; I would like to explore a broader scope of recursive patterns.

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

---

Message 7777.1727 was deleted

---

So there is only one "loop", but the loop can be used for multiple cycles. (?)
Nesting of loops?

- Brian 3+ years

---

Hi, James.
Example of using the "Loop Start" and "Loop End" nodes.

Attachments:
animation.mp4
animation.nod

Image Attachments:
LoopsSE.PNG 

---

Message 7777.1730 was deleted

---

Hi WN,

Welcome to the forum.

Wayne
https://www.instagram.com/waynejhill/

---

Hi Wayne.

Thanks!

---

Wayne,

Yes exactly, but as I said "only as a first step in exploring recursive patterns"
I have updated my earlier post with link to your posted image.

Brian,
Yes exactly! "Nesting of loops".

WN,
Welcome & thanks for the attachments.
They are not what I'm looking for, but I hope these are the first of many posts
of your node experiments - playing with nodes.

Thanks to all of you,
Have a great weekend,
James
https://www.instagram.com/nodeology/

---

Hello Karsten,

This may not help with my particular requirements, but as a first step in that direction,
if "LoopEnd" node was inline with the "Output" node rather than branched off prior
with "clone" node, then each iteration could be recorded and if the option selected, outputted.

Does that make sense?

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

Image Attachments:
loopEnd.gif 

---

Hello James,
yep! Maybe a solution for the problem not to loop all data again. The loop stuff is only a q'n'd' draft and it took a year that someone was asking for. So I've never thought about it in the past again. I had to look twice to understand what I have done here;-)
Maybe we need a second array to store and push collected data? I'm not sure how we can realize it.
Any idea is wellcome!

A nice day to all
Karsten

---

NE -> Gordians_Knot_Puzzle.

Image Attachments:
Gordians_Knot_Puzzle.PNG  Gordians_Knot_Puzzle_2.PNG 

---

Hello James,

I'm trying to find a solution at the moment for the loop stuff - difficult, because no time and written no code since one year. By the way - Could someone explain me nested loops??? Loops in loops?


Not finished, but a first step for an experiment. Only one loop at the moment (think about a solution), but a cumulated output.

Only for experiments!

A nice day to all
Karsten

p.s.: @WN -it seems you have fun!

Attachments:
basicFunctions.js
loop.js
loopTest.nod

---

Karsten,

Thank you for getting back to me.

The new loopEnd node looks promising.

It was clever to use splitPt - ptExt to strip out the rotational data from the point instances.

I repurposed your wiring to do a "drunken walk" (a staple introductory exercise in computer graphics).

A video can be found here:
https://www.instagram.com/p/CDi5Uw1J_5s/

nod file attached
Nested Loops

Nested loops are loops within loops...this video gives a clear description:
https://www.youtube.com/watch?v=1c1_TMdf8b8

I'm not sure how this may work with nodes. I'll see if I can build something.

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

Attachments:
drunkenWalk.nod

---

Show messages:  1-18  …  1659-1678  1679-1698  1699-1718  1719-1738  1739-1758  1759-1778  1779-1798  …  1859