THERM - Window section issues

Replies to This Discussion

Permalink Reply by Chris Mackey on January 13, 2017 at 6:33pm

Hi Abraham,

You were on the right route to getting your issue solved.  When you join all of your polygon surfaces together and use the dupborder command, you should be checking to see the number of borders that get produced.  If it is more than 1, then you have a hole in your model.  Here is how I checked for the hole in you model:

Note that the hole can be really small and I had to deselect the outer border with Cntrl+left click and use the "zoom selected" command to find your very tiny gap here:

To get rid of the gap, I deleted out the aluminum surface next to the hole, joined all of the polygons together, ran a dupborder command, and used the curve around the seleted aluminum surface to build a new surface with the PlanarSrf command (this ensures no gaps).  Then I brought all of the new aluminum geometry into GH, connected it up to the THERM components, and it ran the export component without and issue.  When you open the file in THERM, you will sometimes get the following message:

In this case, you should ignore it at take the default option (Mark the points but don't adjust them).  The reason why this error happens is just because there are no other CAD plugins for THERM and the software still freaks out whenever it recognizes that the geometry has not come from its own interface. After you simulate, you can bring your results back into Rhino/GH like so (and see attached):

I know that this seems like a lot of clean up work but trust me that this is far less than what it used to be when you had to build models from scratch in the THERM drawing interface.

-Chris

Attachments:

• ThermSection_CWM.gh, 628 KB

Permalink Reply by Abraham Yezioro on January 14, 2017 at 1:52am

Thanks Chris!!!

I was getting crazy with this. Specially since i built the polylines in Autocad and imported. Now i see that one of them had a "double line".

May i ask another one for the same case? From the HB_readTHERM i expected to get the uValues for the 4 boundary curves i defined in the input (I changed the input tags to List type, and now back to item, if you use the same fixed file). Instead i get only one of them (the frame). For some reason Therm don't get the other 3 boundary curves.

Thanks again,

-A.

Permalink Reply by Chris Mackey on January 16, 2017 at 6:21am

Abraham,

You had been assigning the U-Factor tags correctly and I have added in a message on the thermBC component that lets you know that this is happening.  The reason why all the tags were not showing up is that the glass polygon needs to have vertices that align with the endpoints of the therm BC line segments in order to be written into the thmx file.  You can see that I have done this in the attached file by generating the glass thermPolygon from a polyline that has vertices that align with the thermBC endpoints.

I had been thinking of writing a check in the writeTHERM component to automatically split the polygons using the BCs when it sees that the BCs are not aligned with the polygons but it was increasing the calculation time a lot.  Perhaps I'll put this in but I'll make it optional.

-Chris

Attachments:

• ThermSection_CWM2.gh, 632 KB

Permalink Reply by Abraham Yezioro on January 16, 2017 at 1:15pm

Ahhhhhhhh. That trick!! :-)

Thanks a lot. Now makes sense.

Whatever you can do to ease the process will be blessed. Right now i'm using your definition, cause when i tried the insertion points is still not recognizing them. Sometimes i missed the exact location (not well aligned), but after fixing them (i think) ... no luck. For now i have to finish a presentation for class, but tomorrow i'll let my version a try.

Thanks again. This is awesome.

-A.

Permalink Reply by Abraham Yezioro on January 17, 2017 at 9:37am

Hi Chris,

Now my own version works fine ... finally!!

Something happened now the messes the legend. I updated today the ThermBoundary component and right after that the legend is scrambled. See image. I assume that things are related.

Thanks,

-A.

Permalink Reply by Abraham Yezioro on January 18, 2017 at 4:13am

Hi,

Somehow the issue dissapeared and the legend shows now. Was weird. So disregard the previous comment.

Thanks again and this is great!!

-A.

Permalink Reply by Abraham Yezioro on January 21, 2017 at 12:01pm

Hi again,

The previous issue appeared again and now i can't make it dissapear (messed legend). I can't say what i did to make it happen, so i don't know where to point a finger. Just can say that it started when the ThermBoundary component was updated.

After the previous paragraph, I copied from another file a previous version of the component and the legend was fixed. Switched back to the updated version and it is working now.

Weird, but there is an issue here. FYI.

Thanks,

-A.