I’m having a very tough time understanding what you are inputting into the Adaptive Chart component from your images. I at least know that your prevailing outdoor temperatures are for Boston, which may not be the site that you are trying to evaluate. If you upload a GH file or an image of the adaptive chart component, I could be of more assistance.
The degreesFromTarget is the number of degrees Celsius that your input conditions are from the centerline of the adaptive comfort polygon. I added this output because I wanted to have something similar to PMV but for the adaptive model. So, just like PMV, when the degreesFromTarget is 0, you are at the most comfortable temperature possible, positive numbers are warmer than this, and negative numbers are cooler than this.
I understand perfectly now. You are using the adaptive component correctly but, in your CBE example, you are taking the outdoor temperature AT THAT HOUR. The outdoor temperature at a single hour is not what determines occupant comfort according to the adaptive model but rather the PREVAILING outdoor temperature. The prevailing outdoor temperature represents the average temperature for that time of year and is either a monthly average temperature (according to ASHRAE) or a running mean outdoor temperature (according to the ISO). I realize that it might not have been perfectly clear that the adaptive chart component is actually calculating this prevailing outdoor temperature for you from the outdoor dry bulb so I added it as in output on the adaptive chart component here:
… and in the attached file.
Here you can see that, even though the outdoor temperature for your specific hour is at 27.8C, the running mean temperature for that time of year is much lower around 16.7 and it is this lower temperature that drives the comfort model.
This is clear now. I think the input name _prevailingOutdoorTemp is a bit misleading in the sense that the hint recommends to plug the DryBulb from the EPW. I believe there is no other possible input here, right (the prevOutTemp is not provided elsewhere).
Can you point me where in the component’s code you calculate this average/mean?
I struggled with the input name when I made the component because I originally thought that people would plug in an actual calculated prevailing outdoor temperature (which the component accepts if it doesn’t find the “Dry Bulb Temperature” in the header of the data). It was only afterwards that I realized that (practically every time) you want to just plug in outdoor air temperature and have the component figure things out for you. Would just plain old “outdoorTemperature” be a better name or does the vagueness of it make it worse?
Here is the part of the code where I calculate the prevailing outdoor temperature:
I think the outdoorTemperature name fits better. In the hint of it you (can) explain the possible inputs. i would add in the hint, for such cases where the user has the prevailingTemp, what should be in the header, so it won’t calculate the averages/mean.
I will change the name of the input around the next stable release as I have been trying to keep the need to drag/drop the components to a minimum since the last stable release was only a month ago. I set a reminder for myself on the github: