Grasshopper

algorithmic modeling for Rhino

radiation analysis - taking very long and using 30gigs of ram. too much detail or memory leak?

I am analyzing a geometry like shown in the picture.

Except I added a round base (not shown), to see how the mass affects the ground in terms of solar radiation.

ladybug radiation analysis grid size 2, 

and its been using nearly 30gigs of ram.

causing other programs i'm using to slow down quite alot.

its been many hours now too. and I am thinking maybe there are too many details or I might not be able to do too many analysis.

Since it is written in python, i wonder if there is possibly a memory leak issue here?

seems like there was a discussion by mr heumann about ghpython performance issue here especially when its running in parallel.

and if it just has to do with the geometry or how I have prepared it, I am wondering if there is a possibility of putting a max ram usage like in a photoshop.

This way at least I will be able to do other things while the radiation analysis finishes.

Probably hard to achieve but I wanted to ask if it is possible.

in this img you can see that the grid size is not super fine - to me I dont know if I can lower the grid size too much from because I want to get information about detailing the facade system.

Views: 6004

Replies are closed for this discussion.

Replies to This Discussion

Hi Youngjae, Good to know that you are making good progress. The result difference is because in the case on the right normal directions are wrong. You need to flip the surfaces and then the results will be the same.

ahh that was it.

This was a long post! :) I will read the next one first and then reply to this if needed. You have access to vectors from testVec output, and yes as you said they are for center of the meshes as they should be.

oops! Here is the link to SAM: https://sam.nrel.gov/

Thank you! will definitely check it out.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service