Hi,
I'm new at IES, but i thought I was getting into the swing of things until I tried to carry out a suncast analysis, and it gets to a certain room and then stops, and the simulation becomes non responsive and therefore dosent be carried out. I'm a student, out on a years placement, and I've been given a project. I drew the project in revit and imported it into IES, is that a possible reason? I've assigned construction and thermal templates and I was running the suncast to be able to produce a yearly heating load profile of the building. Can anyone give me any advice on this problem, or take a at the model for me?
Best Regards,
Jordan
SUNCAST not being carried out
-
JordanGlasgow
- VE Newbie
- Posts: 6
- Joined: Sun Nov 11, 2012 1:13 pm
Re: SUNCAST not being carried out
Would really appreciate anyones help or take on this...
Re: SUNCAST not being carried out
Hi,
A robust geometry is essential before you move on to analysis. If you are importing from Revit then you may find there is a bit of iteration required before you can get a good full model.
I'd recommend after you import to VE that you generate a ModelIT geometry report (Settings menu >> model... then click on Intersection, zones, surfaces and click the Check button). The first thing to look for is Intersections, non-planar surfaces and unmatched adjacencies. If there are issues then you would need to clean these up in the source Revit file or else using the ModelIT edit space tools.
In my experience almost all issues can be corrected in Revit prior to exporting gbXML but sometimes the fastest solution is to redraw key spaces in VE.
Only other useful advice for you is to look for where SunCast is stalling and then go and check that room in ModelIT. It can be a complex calculation so the geometry needs to be good to help it run smoothly.
Phil
A robust geometry is essential before you move on to analysis. If you are importing from Revit then you may find there is a bit of iteration required before you can get a good full model.
I'd recommend after you import to VE that you generate a ModelIT geometry report (Settings menu >> model... then click on Intersection, zones, surfaces and click the Check button). The first thing to look for is Intersections, non-planar surfaces and unmatched adjacencies. If there are issues then you would need to clean these up in the source Revit file or else using the ModelIT edit space tools.
In my experience almost all issues can be corrected in Revit prior to exporting gbXML but sometimes the fastest solution is to redraw key spaces in VE.
Only other useful advice for you is to look for where SunCast is stalling and then go and check that room in ModelIT. It can be a complex calculation so the geometry needs to be good to help it run smoothly.
Phil
IES Worldwide Technical Support
-
JordanGlasgow
- VE Newbie
- Posts: 6
- Joined: Sun Nov 11, 2012 1:13 pm
Re: SUNCAST not being carried out
Thanks for getting back to me,
From your experience, where did the problems originate from in revit, have you any tips for drawing whilst in revit, major do's and donts? One wee question also, when exporting to IES, should sliver tolerances be set to zero tolerance or should it be left at the default value.
Best Regards,
Jordan
From your experience, where did the problems originate from in revit, have you any tips for drawing whilst in revit, major do's and donts? One wee question also, when exporting to IES, should sliver tolerances be set to zero tolerance or should it be left at the default value.
Best Regards,
Jordan
Re: SUNCAST not being carried out
Hi,
In my experiences you can see the problems and where they will creep in in Revit if you view the room boundary lines in plan views/floorplans. Those lines are a visual representation of what Revit will base the gbXML it exports on to define room boundaries so as clean as possible is what you want to minimise risk of problems.
I haven't really messed with the sliver tolerance and would just leave as default but maybe you can begin to dig in there and might get some improvement in the geometry transfer.
http://www.iesve.com/support/knowledgebase/faq/3051
Phil
In my experiences you can see the problems and where they will creep in in Revit if you view the room boundary lines in plan views/floorplans. Those lines are a visual representation of what Revit will base the gbXML it exports on to define room boundaries so as clean as possible is what you want to minimise risk of problems.
I haven't really messed with the sliver tolerance and would just leave as default but maybe you can begin to dig in there and might get some improvement in the geometry transfer.
http://www.iesve.com/support/knowledgebase/faq/3051
Phil
IES Worldwide Technical Support