U Factor Component Behavior

[grahamjlinn]

Hi Chris - some unexpected behavior happening in the U Factor component

In the attached detail/script, when I set the U Factor to “Projected in Glass Plane”, THERM doesn’t interpret the glass plane correctly, it basically defaults to the Projected X plane value

Even when I open the THMZ in THERM it does the same thing

In order to get the desired glass plane U Factor I have to select Projected Y

I am guessing this occurs because we are building our glazing directly in therm and not importing an IGU from WINDOW…just a guess though

–
Also a separate small bug - the convert to IP units appears to break if one of the values in U Factor is 0

Project files for reference
gh_10-for_discourse.gh (85.6 KB)
rhino_template_07.3dm (409.2 KB)
detail1.thmz (517.6 KB)

[remyweather]

@grahamjlinn and @chris I am thinking this is also the culprit of my U Factors seeming a bit off as well.

[chris]

Thanks, @grahamjlinn and @remyweather ,

You are correct that the reason why “Projected in Glass Plane” is always equal to “Projected X” for your models is that, from the perspective of THERM, there is no glass in your model because we have not yet added support for THERM glazing systems.

As I have mentioned, adding support for glazing systems is high on my priority list for Fairyfly features but it is definitely something that I plan to do after the LBT 1.10 stable release since the first version of it is very likely to have some edge-case bugs that I’ll need your and the rest of the community’s help testing and fixing. So just be patient and we’ll get there.

And, speaking of edge-case bugs, thanks for letting me know about the bug when the U-Factor is null as a result of the length being zero. I just fixed that here:

fix(therm): Handle the case of null U-factors with zero length

[grahamjlinn]

Thank you Chris!! Totally understand development timelines, thanks for putting this on your roadmap

And thanks for lightning fast commit!