So if you were to sell that tool/script- how much would you charge for it?
Besides whether @SeanP wants to sell it or not i guess his script is tailormade for their standards.
So it is not simple buy his script and it works.
And do you have the Dynamo knowlage to change his script to suit your standards?
Not to mention the packages you might need.
.dyn’s aren’t like add-ins.
1 Like
True- I’m just wondering if it would be easily adaptable to our workflow.
1 Like
I don’t mind sharing my graph, but mind you it is nearly 2 years old at this point and will most certainly need to be upgraded and packages referenced correctly. And of course it will also need to be modified to fit your families and standards. Merry Christmas!
Doors - Set Door Fire Rating from Wall Rating_IA Doors.dyn (56.1 KB)
3 Likes
Sean- what did you set your wall/door fire rating parameters to - type or instance? I presume instance, but I just wanted to confirm. Thanks!
Yes the door ratings are instance based, walls type based.
So I finally understood what others were talking about earlier, regarding making the parameters type-based. That did not work out.
So here’s where I’m at with Sean’s graph that I used as a model:
I have a type parameter within my walls called “Base Partition Type”. Each wall type has a nomenclature (for sake of argument, let’s say A10, B20, C30, etc.). So when you go into the wall type properties, under the wall type parameter, you will see similar text.
Also under the wall type properties, every wall type has a type parameter called “Fire Rating (Dynamo Type)”.
The doors have an instance parameter simply called “Fire Rating”.
Not sure what I am doing wrong, but now the fire ratings aren’t showing up at all in the schedule:
I ultimately want all the doors except wall type A28 to be reduced by 0.75. Doors in type A28 walls will be 20 minute doors in a 1-hour wall.
Ideas? Thanks!
Looks like your using the wrong parameter name on the doors. Wouldn’t it just be Fire Rating as you said, not Fire Rating (Dynamo Type)?
Also using a custom parameter called Fire Rating which is exactly the same as the build-in one is probably just asking for confusion.
Since I was experimenting with Dynamo, I needed a separate parameter that was called something else so I could differentiate.
Now that I am here, could someone tell me which parameters (according to my system), I would have to plug into the graph I most recently uploaded a screenshot of?
Again, I am trying to get all of the doors to report a Value of 0.75 Of the FR of the walls EXCEPT the residential demising walls which would be 1/3 of the fire rating of the wall (in reality- 20 min).
Thanks!
Gents- sorry to follow up, but I want to put this issue to bed tomorrow. Any help is much appreciated!
Thanks!
Augustin
As Sean said, according to your own text you used Fire Rating (Dynamo Type) at the bottom of your script where you should use Fire Rating.
That this doubles up on the Fire Rating parameter (your new one and the default one) is also probably why you’re having troubles.
Maybe read the whole conversation.
Your suggestion is NOT an option in this case.
The GetParameter should have a Type Parameter like in your Graph - Fire Rating (Type Parameter). The SetParameter should get a Instant Parameter in example - Fire Rating (Instant Parameter).
Keep in mind 
(try to avoid Parameters with the same name in your Project).
If you want to report 0.75 times the Fire Rating
to your Doors the you have to use a Math node (x * y) after the GetParameter and before the SetParameter.
You need to duplicate / split part of the nodes.
A part to set Doors 0.75 of the FR and a part to set Doors 1/3 of the FR.
Maybe this helps?
NB
Tbh you really bit more of then you can chew.
Also some things should have been clear by now as we explained it more than once. I feel like you would be better of now if someone would just make a working Graph for you, but AFAIK that is nof what this forum is about…
1 Like
BVS - thank you so much! That worked! My only issue now is that when I hook up the multiplication node with a number 0.75 for example (and I tried all variations), the FR is not changing. Wierd.
It is hard to tell why without seeing the whole
Graph and it’s values (you can pin then Lists / white boxes under the nodes)
Are their any warnings?
The 2 and 1 values are showing up correctly in the schedule… its only when I hook up the number and * node that I get incorrect values.
I need to see the values of the calculation node wired.
Wild guess… might be a rounding issue. What kinda parameters are your FR parameters?
Are they a Text, Integer or Number?
