Page 4 - Demo

Interface to Scilab%uf09f%uf09fRCPConsult2021-2025Page 4The second type of script may contain any set of commands in notation of Scilablanguage. Such a script must have a statement defining variable %u2019res%u2019 as a final return value. Usually, this statement is the last one. We recommend using thefirst type of script, because a description of functionwill be loaded and parsed by engine once. Then, on runtime, it will be just evaluated numerically. The second kind of script requires loading and parsing of its content by the engine runtime for each call of evaluation. This slows down computation.Additionally, it is possible to send a single statement or an expression with multiple statements direct into the engine for a numerical evaluation or intermediate processing for evaluation of the state function.5.Global Data in the InterfaceBefore processing interface data in form of script files or direct expressions STRUREL presets all required input variables. Three global sets will be defined: two global vectorsand additionally, each stochastic variable and deterministic parameter become an assigned global namehaving exactly the same name as in the Stochastic Model. This allows to work in vector notation and/or direct over global names. The first global vectorhas a fixed name s_XP_and contains the mean values for the stochastic X-variables followed by the values of the deterministic Parameters. The second global vectorhas a fixed name v_XP_and receives all values of the current evaluation step for the X-variables followed again by the values of the deterministic Parameters.Implementation of global vectors s_XP_and v_XP_allows creation of plots of the initial and final (%uf062-point) states of a structure where a comparison can be shown graphically and numerically.Finally, for special purposes, the following set of STRUREL information variableswill be also defined: StrurelMode0 %u2013initial state ofevaluation having global vector state as mean values1 intermediate state of evaluation of global vector during run2 %u2013final state after runhaving global vector state at %u00df-pointStrurelRunInteger counter of calls of state functionStrurelNameLiteral value %u2018STRUREL%u2019StrurelModuleLiteral value %u2018COMRELTI%u2019 or %u2018COMRELTV%u2019 or %u2018SYSREL%u2019 or %u2018COSTREL%u2019StrurelVersionLiteral value %u20182025%u2019 or corresponding value for future versionsStrurelIMETLiteral value with description of method of probaility integrationStrurelIOPTLiteral value with description of optimizer for %u00df-point searchStrurelBetaReal value of reliability index %u00dfStrurelPfReal value of failure probability PfStrurelEngineLiteral value with information about compiler used in Buildout Add-onStrurelPlotLogical variable to switch on/off postprocessing facilitiesStrurelPlotNameLiteral value for a base name of file for plot drawn in interface engineStrurelPlotTypeLiteral value for an extension of file for plot drawn in interface engineStrurelPlotMode1 shows a generated plot in a separate window2 %u2013saves a generated plot in a file with format defined by an plot extension3 combines mode 1 and mode 2StrurelPlotCountInteger counter of plots drawn on run. Default is 0