search

BHoM / LifeCycleAssessment_Toolkit

GNU Lesser General Public License v3.0
22 stars 5 forks source link

Help Please - Life Cycle assessment evaluation of the EPD by Volume or Mass is not available #229

Closed nadamowafy closed 1 year ago

nadamowafy commented 3 years ago

What is missing/incorrect?

After pulling the volume of the physical element to evaluate its EPD by the quantity, its node which is a engine>compute>evaluate EPD by Volume can not be found. I didn't find the node.

This is a screenshot of the available nodes for the quantity calculation of the GWP without volume or mass. 2

nadamowafy commented 3 years ago

@michaelhoehn

kayleighhoude commented 3 years ago

@nadamowafy the solution below might help, the methods by volume, mass etc have been simplified into a single evaluate method: image

nadamowafy commented 3 years ago

Thank you so much but I have several other problems.

The first one is when I use any EPD which is measured by mass and it needs the density information; the result always is equal to zero, on the other hand when I use EPDs with volume or area measuring methods, it will have the correct gwp output. Am I missing something here or a step?

The second one is that when I import a sample from Autodesk Revit, it is rendered in rhino but this error appears to me:

  1. Failed to run Geometry extension method. Error: Object reference not set to an instance of an object.
  2. Failed to run Geometry extension method. Error: Sequence contains no elements

The screenshots are found on this Google Drive link. https://drive.google.com/drive/folders/1CuJ08B-5MUKF5xolDoeHFdl2X2ucmXQ3?usp=sharing

Thank you so much.

michaelhoehn commented 3 years ago

@nadamowafy if using a Mass-based QuantityType EPD, the eval method will always require a density in order to calculate the desired metric. You can accomplish this in the latest beta by selecting the EPDDensity() data fragment and adding it to the EPD itself prior to evaluation. Volume or Area-based EPDs don't actually require density information to be calculated, so they will work out of the box. The reason this data was omitted is that density values are typically not included in the original database, and therefore we don't want to add anything to modify this data that would make it lose its source integrity.

image

Re your last question, the BHoM is limited on what geometry it can display natively as its primary objective is interoperability of raw data instead of geometry representation at this point in time. One limitation is the inability to display NURBS based geometry without having to reconstruct in Rhino. What you're showing in your examples are likely either geometry that cannot be natively represented, OR objects that do not have BHoM representation yet (such as footings). These objects are not yet defined and will result in an error if pulled via SelectionFilter() type request. If there are objects that you'd like to work with that don't yet have type schemas, please feel free to open an issue in the BHoM core repo for future integration.

Hope this helps!

michaelhoehn commented 1 year ago

Closing old thread. Please reopen when needed. Or make use of our open discussions.