Grasshopper

algorithmic modeling for Rhino

I have just found out something I did not know: <null> (no data) is not the same as: 0 when it comes to addition or any other mathematical operation.
I know that 0 is a number and <null> is not a number, simply nothing, lack of data, but I thought that when it comes to mathematical operations there is some sort of a converter which will "see" <null> as 0. I was wrong:

How can I convert <null> to 0?

Thank you.

Views: 2095

Replies to This Discussion

Oh, so that was what "internalize the line data" meant?

It's a bit difficult, as a couple of bakes gradually are made from the start of the process until the end. And not all initial curves need to be removed, just particular ones.

In any case thank you for the help, previous solutions on <null> issue solved the problem.

Ok, I can see your logic.

There's an "internalize" option in the right button context menu for geometry params. This will convert the referenced geometry into GH-geometry and store the data in the param. Connection to Rhino geometry will be lost. You can delete all Rhino curves now and bake the culled curves back to Rhino. You would need to ressign and internalize the curves from Rhino at each iteration.

On the other hand, you can try and generate a culling pattern for the original list of lines from all the beams. Since you don't add or remove any beams, the pattern should be exactly the same.

Understood.
I was always being confused with .gh files with no additional .3dm files included, and still they had an input geometries at the end of their definition.

I did not know that it was "internalize" option that "did" that.

Vielen Dank.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service