Replacing the "<null>" with "0" in a list?

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.

Replies to This Discussion

Permalink Reply by Chris Tietjen on November 11, 2012 at 7:03am

Permalink Reply by djordje on November 11, 2012 at 7:23am

Thank you for the help Chris.

Is this some kind of issue related to my version of grasshopper (0.8.0066) or am I doing something wrong? I got my "<null>" value from the intersection of two curves. I know the output of this component does not result in a number, but a point, but I was thinking of a way to generate the <null> on purposely, so I thought that maybe I could use two curves, which do not intersect:

What am I doing wrong?

Thank you.

Attachments:

null.gh, 3 KB
null.3dm, 51 KB

Permalink Reply by Hannes Löschke on November 11, 2012 at 8:45am

You should update ;)

Permalink Reply by djordje on November 11, 2012 at 8:47am

Thank you for the help Hannes.

A particular plugin is not working onto 9+ versions.

Is there a way this issue can be solved without using 9+ versions?

Permalink Reply by Hannes Löschke on November 11, 2012 at 9:03am

null-item should be availble in .8 versions as well as pick'n'choose

(longest-list behaviour is no longer built into the components for .9 versions, hence the extra component)

Permalink Reply by Michael Pryor on November 11, 2012 at 9:03am

What plugin?

Permalink Reply by Erick Vásquez on November 11, 2012 at 9:04am

or with list replace.

Permalink Reply by djordje on November 11, 2012 at 9:16am

Thank you, all of you.

Michael: it is a component David wrote, for deleting the referenced curves.
Not a plugin, I apologize for using the wrong term.

Permalink Reply by Hannes Löschke on November 11, 2012 at 9:55am

Are you referring to this thread?

If so, Davids script seems to be working with 0.9.0014. Only problem is your workflow. Referenced Lines are lines that sit in Rhino. The have a unique number each to identifiy them (the GUID = globally unique ID). The script can delete Rhino-Curves by knowing their GUIDs.

Once the lines are fed to LineToBeam, they will be copied to GH lines and loose their connection to the original Rhino Lines. Their GUIDs are lost.

Disassemble will give you valid GH lines that have no knowledge of their Rhino parents.

You need to cull on the original input curves in order to maintain GUIDs.

Permalink Reply by Michael Pryor on November 11, 2012 at 10:24am

I would just put them on their own layer, or internalize the line data.

Permalink Reply by djordje on November 11, 2012 at 11:13am

Thank you for the reply, both of you.

Hannes: You are right, this is karamba we are talking about.
And I can not cull the original input curves (at least I think), as that original list was culled few times along the way.

Permalink Reply by Hannes Löschke on November 11, 2012 at 12:15pm

As Michael suggested, why don't you just put your input lines on a different layer than the one you are going to bake the results to?

You can hide/delete everything you don't need afterwards.