I realize there are lots of posts and documents related to EPlus simulation time and solutions for mitigating long run time. My question takes these posts/solutions a step further and looks at what exactly is causing the slow down. I've had scenarios where I inadvertently figure out a particular zone/object that was causing a slow down - but entirely by dumb luck. Is there any way to dissect or expand the simulation run log in order to figure out if-or-which zone/object is causing the slow-up or getting stuck in a calculation loop?
This may not be possible, but worth throwing out to the group.
