How can i get rid of Null and Infinity!

Revit
1

Hello,

I just want to get rid of this values. so i do it, with 2 boolmasks. but i think there is a better way. Can i combine this filter rules?
there is this issue "" ; null ; Null ,

KR

Andreas

2022-05-16_14h13_58
2022-05-16_14h13_581511Ă—453 92.2 KB

2022-05-16_14h14_08
2022-05-16_14h14_08981Ă—692 85.8 KB

2

Use this in codeblock
x>100000 || x==null ? false:true

3

2022-05-16_14h21_38
2022-05-16_14h21_381561Ă—753 116 KB

@theshysnail still i need 2 boolfilters!

4

You’re getting Null with a capital N? Most probably those are just string values. Try "Null" or Null instead of null.

x>100000 || x=="Null" ? false:true

1 Like
5

@theshysnail they are not strings… that are areavalues which are stored in a Parameter.
the infinity, Null and null comes from there

6

@Draxl_Andreas would that work?

image
image1639Ă—553 41.9 KB

1 Like
7

The problem is not the conditional statement. You can see that it’s returning the correct booleans. If you read the error from FilterByBoolMask it states that it’s merely a warning that the Infinity value is outside the working range. You actually just need another condition to convert the Infinity to something within range.

image
image1185Ă—425 55.7 KB

As an FYI, you can see that in later versions Dynamo still handles the booleans appropriately.
image
image1167Ă—512 48 KB

1 Like
8

2022-05-16_15h23_28
2022-05-16_15h23_281063Ă—428 65.2 KB

@Nick_Boyts @Elie.Trad @theshysnail
I should never say to a college “it is a easy task for dynamo!” :slight_smile:

9

What is it that you’re trying to do? You can’t convert a null to a string so you’re still going to have issues. I thought you just wanted to filter the out the non-real numbers?

10

@Nick_Boyts i want to remove all from my value.list thats not a area.Value.
Null
null
infinity

                                     #here_is_nothing
11

Then you’ll have to do something like I suggested in my first post, which is to convert the Infinity value to a real number within your working range.

1 Like
12

@Draxl_Andreas use the node String from Object

13

Ok, i give it a try! :wink:

1 Like
14

2022-05-16_15h43_24
2022-05-16_15h43_24648Ă—765 83.1 KB

I solved the problem… i can live with the warning. my calculated vales get filed correctly! @Elie.Trad

15

@Draxl_Andreas use String from Object instead of the Code Block x+"" as well :smiley:

1 Like
16

Again, you can bypass the warning by converting the Infinity to something in range.

image
image1545Ă—538 101 KB

Converting everything to a string would work as well.

1 Like
17

@Nick_Boyts

there is still a sorting issue?

2022-05-16_17h14_24
2022-05-16_17h14_24763Ă—414 54 KB

2022-05-16_17h15_18

18

@Elie.Trad @Nick_Boyts @theshysnail
look at that :slight_smile:


OUT = []

for i in IN[0]:
	if i >= 99999:
		OUT.append(False)
	elif i == None :		
		OUT.append(False)
	else:
		OUT.append(True)

that works for me so Null + null = None :slight_smile:

2022-05-16_17h34_26

19

That’s cause you only gave it 3 booleans. I was just showing you an example with those values. You obviously have to use the appropriate booleans (based on your conditional statement) for your set of values.

1 Like
20

But infinity is a value… not a happy one for math purposes, but a value all the same!

I would replace the 0 with a alternative number prior to doing the math.

1 Like