Grasshopper

algorithmic modeling for Rhino

[issue to be reported] "indoor view factor calculator" & "Microclimate Map Analysis" error

I got the following error when using the indoor view factor calculator component which is working fine previously:

Solution exception:'int' object is unsubscriptable

May I ask what's the source of the problem and how to solve it?

Thank you!

Views: 866

Attachments:

Replies are closed for this discussion.

Replies to This Discussion

OK, I replaced the indoor view factor calculator and its input components from a previous working file, and it works now, strangely ...

a new problem now for the microclimate mapping component with the error message of:

The calculation has been terminated by the user! , although I didn't intervene at all ....

May I have your advice on this problem?

Thank you!

Attachments:

Dear bee and bugs, really appreciate if you can kindly help to take a look and advise cause I'm kind of stuck here....!

Thank you very much!

I suggest you to simplify your example, for the sake of the simulation time. All Comfort analysis is processor consuming.

Just opening the file takes a while ...

I see that you want to analyze only one zone, so why you are connecting all the 53 zones to the analysis. I suspect that your computer gets "tired" and it's resources are exhausted.

Can be?

-A.

Thanks, Abraham!

I agree that my example file is too complicated to run for debugging purpose...

Nevertheless, I found that if analysis period is disconnected with the microclimate mapping component, it will work fine, but with only winter solstice data is generated.

I wonder if the error is caused by reading analysis period for this component.

As to the thermal zones connected to the view factor calculator component, I follow the original workflow shown on Hydra in which all thermal zones used for energyplus simulation are connected to this component.

Is is correct?

http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&for...

OK, I simplified the geometry for test, and it runs faster now.

However, the problem for the Microclimate Map Analysis component is still there when connected to analysis period component ...

Helps are greatly appreciated!

Attachments:

Yes. You should connect all zones (my bad) since it is required for the MRT calculations.

I'll check your file ...

-A.

I noticed that the Microclimate Map Analysis component was just updated on Jan-26. I wonder if it is the latest update of this component that causing the problem...

See attached,

It is working but is not "healthy".

There is a problem with the analysisPeriod component and the results obtained from different simulations. I mentioned this issue in another discussion (can't recall which one).

See at the right the yellow group. Instead of connecting the analysisPeriod to the HB_MicroclimateMap i connected a HOY. It works and shows the selected hour, but ...

The legend shows a wrong month (March instead of April). When you go to hour 17 it crashes also. Don't understand why.

Notice that also the KB_selectAndAverageData is failing (trying to divide by zero). So, something is going on there and i can't catch it exactly. Maybe it is related to some "Line meshes" output in the HB_IndoorViewFactor.

Will be glad if Chris can have a look or give his opinion on this.

-A.

Attachments:

Thank you very much, Abraham, for your kind help!

I found that average data component works for full year hourly results, so, I'm not sure if there is a bug in this component that can't deal with non-annual data.

I also noticed, as you mentioned, that there are quite a lot of month-day-hour combination for the HOY component that will make the Microclimate Map Analysis component fail:

So, I'll change the title of this post to get Chris and Mostapha's input.

I would report the issue in the github.

-A.

Abraham and Grasshope,

I apologize for being so lat to the conversation.  The stable release last week took a lot of time and, now that we are well past it, I can get down to addressing all of the discussions.

The heart of the problem was a math domain error that was occurring in the function that calculates indoor air stratification, which is ironic as this was a simulation that did not have any indoor test points.  This has now been fixed in the attached file and on the github.

The second issue was that the month was off by 1 when you connected up an HOY and this has also been fixed now.

https://github.com/mostaphaRoudsari/Honeybee/commit/d45ac37bc8b9db3...

My last comment is a suggestion to break up the ground top surface into several surfaces as this allows the temperature maps to account for spatial differences in ground temperature across the scene.  This is what I do in this file here:

http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&for...

Thanks for getting down to the cause of issues like this one. It really makes these bugs much easier to fix. Between the both of you, I feel you can take credit for over 90% of the bug fixes in the community.

Great job, as always,

-Chris

Attachments:

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2025   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service