Hi,

So I’ve started to play with obtaining material-level information from composite walls.
Although the Energy Evaluation module is capable to calculate the U-value of a given wall, it is not a parameter accessible to scheduling or to show in labels.

It would look something like the picture in the attachment.

My problem is, that I cannot get the proper values stored in the building material physical properties (as you can see, the thermal conductivity is properly assigned, but after that the density gets the same value…).

	for i=1 to n
	
	! building material name
		_wallSkins[i][1] = WALL_SKINS_BMAT_NAMES[i][1]
		text2 0,-i*0.1, _wallSkins[i][1]
	
	! building material width in cm
		_wallSkins[i][2] = WALL_SKINS_PARAMS[i][2]
		text2 dist_thickness,-i*0.1, STR ("%m", _wallSkins[i][2]*100) + " cm"

	! thermal conductivity
		thermCond = REQUEST{2} ("Building_Material_info", _wallSkins[i][1], "gs_bmat_physical_properties", thermalConductivity)
		_wallSkins[i][3] = thermalConductivity
		text2 dist_thermCond,-i*0.1, STR ("%m", _wallSkins[i][3]) + " W/mK"

	! density
		matDensity = REQUEST{2} ("Building_Material_info", _wallSkins[i][1], "gs_bmat_physical_properties", density)
		_wallSkins[i][4] = density
		text2 dist_density,-i*0.1, STR ("%m", _wallSkins[i][4]) + " kg/m³"
	
	! heat capacity
		heatCap = REQUEST{2} ("Building_Material_info", _wallSkins[i][1], "gs_bmat_physical_properties", heatCapacity)
		_wallSkins[i][5] = heatCapacity
		text2 dist_heatCap,-i*0.1, STR ("%m", _wallSkins[i][5]) + " J/kgK"

	! embodied energy
		embEnergy = REQUEST{2} ("Building_Material_info", _wallSkins[i][1], "gs_bmat_physical_properties", embodiedEnergy)
		_wallSkins[i][6] = embodiedEnergy
		text2 dist_embEnergy, -i*0.1, STR ("%m", _wallSkins[i][6]) + " MJ/kg"

!	! embodied carbon
!		embCarb = REQUEST{2} ("Building_Material_info", _wallSkins[i][1], "gs_bmat_physical_properties", embodiedCarbon)
!		_wallSkins[i][7] = embodiedCarbon
!		text2 dist_embCarbon, -i*0.1, STR ("%m", _wallSkins[i][7]) + " kgCO2/kg"

	
	next i

For some reason I thought, if I store the request in a variable and use that, it would work, but it works when the requested physical property (e.g. thermalConductivity instead thermCond) is used. Which confuses me, that I used the same logic with the density, but no success.:(

For the U-value calculation itself these values are not that important, but to double check the used composites, I would say it is useful. (Wish: if the U value of the layers would show up in the composite editor, that would be awesome!)

If the U-value is stored in a label object, is it possible to assign this value back to the wall? Theoretically, there would be a ,,calculated U-value” property, and a ,,required U-value” (already given) property, and a third value, ,,U-value is sufficient” boolean to create graphic overrides.