[bug fixed] PMV calculator warning: "1. The calculation has been terminated by the user!"

Replies to This Discussion

Permalink Reply by Abraham Yezioro on July 30, 2015 at 10:36am

Hi,

Indeed you get this. I just reinserted the component manually and it works fine. Be sure you are synced with the last version in the github.

-A.

Permalink Reply by Grasshope on July 30, 2015 at 11:04am

Thanks, Abraham!

It seems that the PMV calculator cannot accept a whole year analysis period specified through the analysisPeriod component. (I understand that the PMV calculator does whole year calculation by default if no input is specified for its analysisPeriod_ node)

Might this be a bug (i mean a programming bug :) of the PMV calculator component?

a non-whole-year analysis period specified through analysisPeriod component works fine with PMV calculator:

But a whole year analysis period specified through analysisPeriod component doesn't work with PMV calculator:

Permalink Reply by Abraham Yezioro on July 30, 2015 at 11:22am

Seems to be a big.

In the meantime if you have  a whole year just don't hook the AnalysisPeriod componet to the PMV calculator.

-A.

Permalink Reply by Grasshope on July 31, 2015 at 11:12pm

Noted with thanks, Abraham!

I'll changed the title of this post, and hope the LB+HB team will take note of it.

Permalink Reply by Chris Mackey on August 1, 2015 at 3:37am

Grasshope,

Thank you for finding the bug. Given all that you have found over the last week, I think this makes you the community's official bug-finder for the present :). I have been teaching a class for the last week but, once I get back in a few more days, I will fix all that you have found.

-Chris

Permalink Reply by Grasshope on August 1, 2015 at 8:32am

Thanks, Chris! What an honor to be an "official bug-finder"! (.... can't talk, tears in my eyes ...)

Permalink Reply by Chris Mackey on August 4, 2015 at 7:27am

Grasshope,

I just fixed the bug.  Find the working file attached.

-Chris

Attachments:

• FixedPMVComfCalculator2.gh, 381 KB

Permalink Reply by Grasshope on August 4, 2015 at 7:46am

Thank you very much, Chris! Will update my GH file.

Permalink Reply by jay johnston on November 28, 2016 at 12:16pm

Hey Chris,

I'm assuming this bugfix was carried over to the latest and greatest version of ladybug (VER 0.0.63) however I'm getting the same problem identified above ("the calculation has been terminated by the user") with the PMV comfort calculator...

Attached is my GH file, hopefully you can assess what is going on

thanks in advance

Attachments:

• ladybug Comfort-4-Outdoor Comfort Standard Effective Temperature.gh, 412 KB

Permalink Reply by Chris Mackey on November 29, 2016 at 7:37am

Jay,

There seems to be a weird wind speed value that is causing the PMV function to fail.  I'll try to take a deeper look at it soon.

-Chris

Permalink Reply by jay johnston on November 29, 2016 at 3:44pm

Thanks Chris...

Let me know whenever you get a chance...

Permalink Reply by Chris Mackey on November 29, 2016 at 10:29pm

Jay,

It seems that you found some magical combination of PMV model inputs that caused the algorithm to diverge (it seems to be the result of high metabolic rate and high wind speed).  I added in an extra check and it works now:

https://github.com/mostaphaRoudsari/ladybug/commit/09c885c813a1118b...

-Chris

Attachments:

• ladybugComfort4OutdoorComfortStandardEffectiveTemperature_CWM.gh, 412 KB

• ‹ Previous
• 1
• 2
• Next ›
• Page