@edpmay ,
Thanks again for all of the information and I have pushed the changes to the “Read THERM Result” component such that you now get the BC length and the delta T:
I also changed these outputs to be a data tree where each UFactorTag is its own branch, which I think will make it a lot easier to process the results for these simulations where you have more than one uFactorTag:
I also decided to bring in all of the tags even when the BC length is 0 and the UFactor is NaN since this will make it easier to write scripts to process the results (since the first UFactor in the list will always be the Total Length, the second will always be Projected X, etc.). At the least, this will save you from having to manually select each UFactorTag out of the list in your result post-processing. In an ideal scenario, I hope that it also means that you might be able to use the projected X and projected Y U-factors in a Psi value component instead of having to manually put in points but I realize there may be a few steps to figuring out how to do this.
Lastly, I added you to the credits on the components for supplying to code to parse out the BCLength and the DeltaT:
Let me know if you get the chance to post an updated Psi value component now that we have these changes. As I said, we’d be happy to have it as a part of Honeybee.
Oh, and @jwoodall , I added a check to the THERM simulation component, which should decrease the probability of you seeing the WindowsError. I have realized the latest versions of THERM seem to be locking the thmx file somehow, which cases errors when you re-run the component. The check in the component should catch these situations now.