Some dynamo BHoM nodes not searchable and add fragment returns null value?...

[JeamesH]

Hi there,

Im after some additional help actually running a script in Dynamo. Ive got 2 points I need assistance on.

1 - The Add fragment node has a null list even though Ive fed in 16 true BHoM Floors into it. can someone help explain what is going wrong here?

Evaluate EPD by volume. When I search for evaluate by volume I can’t find that node?

these 2 issues seem to be stopping the script from running any further?
Once I get past this I was going to go and start on evaluating walls, roofs, ceilings etc.

I would appreciate any help you can assist me with.

Thanks 😊

[FraserGreenroyd]

@michaelhoehn are you able to provide any input on this?

[oswaldohb]

Hey, having exactly the same problem @JeamesH @andreea101

[michaelhoehn]

@JeamesH @andreea101 @OswaldoHernandezB sorry about all the difficulty with mapping materials. This is actually the core functionality that the next version of the toolkit will hope to solve.

For this issue, however, I'm fairly confident that this can be resolved by checking the exact property name that is being modified for each object type. Currently, BHoM physical objects may actually have different material accessors. For example, a Floor (physical object) can be modified using Construction.Layers.Material while a Column can only be modified using Property.Material. Currently there is no easy way to distinguish which one you should be using to set with other than exploding the objects (already sorted by type) and tracing through the relevant properties.

I can't tell what type of objects you are actually working with in your example snippet, but I'd guess they required a different accessor string in order to modify. If switching this doesn't resolve your problem, I'd recommend downloading the latest BHoM 5.1 beta and trying it again as certain material-specific workflows have changed a bit in the past. As I said earlier, we hope to be resolving this issue entirely in the next major LCA toolkit update.

[JeamesH]

Hi Michaelhoehn, no need ot apologise the tool kit is coming along nicely and autodeks dont make it easy to get to this level of data through the API.
thanks for the clarification about material accessors. Flors I have working well. I would have assumed a Coloumn was a BHoM physical object too? you can see in my screenshots below I am using structural columns in revit with the material (concrete, metal etc.) in the family name. In dynamo I am, then pulling columns through BHoM, sorting columns by family name contains noides and then trying to apply EPD data using your 'Property.Material' code. columns are still not picking up those values though.

Ive ben to the BHoM website its still beta version 5.0 that is downloading...
appreciate the work you are all doing on this. thanks.

[FraserGreenroyd]

Ive ben to the BHoM website its still beta version 5.0 that is downloading...

@JeamesH you might need to clear your cache to force it to download 5.1, however, on Monday we'll be releasing the 5.2 beta so it may also be worth waiting till then? 😄

[JeamesH]

@FraserGreenroyd thanksfor the tip :) will wait for mondya then. thanks again !