Solve Adjacencies

Replies to This Discussion

Permalink Reply by Mostapha Sadeghipour Roudsari on August 19, 2015 at 12:28pm

I can't check your file now but my best guess is that you're creating zones with similar names. Make sure zone names are not replicated.

Permalink Reply by Mostapha Sadeghipour Roudsari on August 19, 2015 at 12:36pm

I think I lied! I just checked and that was the case. Check the attached file.

Permalink Reply by Mostapha Sadeghipour Roudsari on August 19, 2015 at 12:36pm

-

Attachments:

• solveadjacencies_msr.gh, 523 KB

Permalink Reply by Blanca Dasi Espuig on August 20, 2015 at 2:35am

Thank you for your fast replay Mostapha, unfortunately it is still not fully working for me.

I did tha same with the core zone but that didn't change anything (the walls were the same when I opened your file).

Permalink Reply by Blanca Dasi Espuig on August 20, 2015 at 2:44am

Also, I get this for different components everytime I open a file, not sure if it has anything to do with it or it is just bc it hasn't update the components yet at that time.

Permalink Reply by Chris Mackey on August 22, 2015 at 4:19pm

Blanca,

Sometimes, you might need to play around with the tolerance on the solveAdjacencies component and I was able to fix your case this way.  I am not sure if this is the underlying reason of your case but the tolerance is particularly important if the tolerance of your current Rhino document is different than that which originally created the geometry internalized in the GH file.  The file attached should work for you:

-Chris

Attachments:

• solveadjacencies_msr_CWM.gh, 508 KB

Permalink Reply by Blanca Dasi Espuig on August 24, 2015 at 4:54am

Hi Chris,

Thank you for your input. By changeing the tolerance in the component HB now identifies all interior walls, the problem is that when I run an energy simulation E+ (daylight seems to be working fine) doesnt seem to find the adjacent surfaces? (gh file attached)

Not sure if the problem is still in the adjacencies component.

Thank you,

Blanca

Attachments:

• SurfaceNotFound.gh, 618 KB

Permalink Reply by Mostapha Sadeghipour Roudsari on August 24, 2015 at 9:08pm

Blanca,

You had half of the zones not connected to the component. After you solve adjacency you need to run the analysis for all the zones.

Mostapha

Attachments:

• SurfaceNotFound_msr.gh, 631 KB

Permalink Reply by Blanca Dasi Espuig on August 25, 2015 at 4:32am

Hi Mostapha,

thanks for catching that, I've been trying so many different things that I end up missing the simplest. Still it is giving a severe error, though it is giving results, not sure how much does this error affect the results. Thanks,

Blanca

Permalink Reply by Mostapha Sadeghipour Roudsari on August 25, 2015 at 2:46pm

This is because your Zone is non-convex and EnergyPlus has limitation in calculating energy simulation for non-convex geometries. See this discussion: https://unmethours.com/question/1326/non-convex-surfaces-in-energyp...

Permalink Reply by Chris Mackey on August 26, 2015 at 10:17pm

Blanca,

The easy way to make the CHKBKS error go away is to use the EP Sim parameters component to set the simulation to run ExteriorWithReflections like so:

This will have E+ use a simplified model for interior solar distribution (all beam solar will go directly into the floor and the diffuse solar will be distributed by view-factor to the different surfaces).  While this is a big simplification, it will be more accurate than running the model with a faulty set of interior reflections.

-Chris

Permalink Reply by Blanca Dasi Espuig on August 27, 2015 at 2:15am

Thank you both so much!