Re: [TRNSYS-users] GenOpt variations on Type56

["Jeff Thornton" <thornton@tess-inc.com>]

<This leads me to the question; why does our non-standard type incur
problems when called from GenOpt and not when run from within simulation
studio; how does the data stream between these programs bring about such
behaviour? We are willing to accept that our type is not perfect (that it
has some NaN or overflow by near-zero flow or other such circumstances)
but I'm not sure how to isolate the problem further than this.>

When you run your simulation from the Studio, you're running a single set
of conditions.  When GenOpt runs the analysis it performs hundreds or
sometimes thousands of simulations with different combinations of
parameters.  It seems that at least one combination of parameters is
causing your problem and stopping the analysis.  The good news is that the
input file that failed will still be contained in the GenOpt/Simulation
directory.  Find the file, identify the set of parameters that caused the
problem, plug them into your studio project and see what is causing the
failure (try tracing the components etc.).

Jeff



Jeff Thornton
President - TESS, LLC

2916 Marketplace Drive - Suite 104
Madison WI 53719 USA

Phone: 608-274-2577
Fax: 608-278-1475
E-mail: thornton@tess-inc.com
Web: www.tess-inc.com