![]() ![]() However, when MedModel is first launched and no INI file exists for it, the defaults in the following table apply. As your models differ, so will the need to change these settings from their default. Since MedModel can be used for a wide variety of applications, you may require different settings. While your models may require different settings, an effort has been made to select the most common and helpful default settings. This section discusses and lists the default settings when you first run MedModel.Īs in most software packages, MedModel makes certain assumptions regarding the most useful settings for the program. Fields not listed on this chart are either menu fields or expression fields that accept only numbers. Fields are classified as either expression fields or logic fields. The following chart categorizes the edit fields in this manner and shows the expression and statement groups that can be used in each field. When running a simulation, expressions and statements are either evaluated 1) once at translation (before initialization logic and before any events are created) or 2) continuously during the simulation run. Valid Expression and Statement Groups by Field When a subroutine is used in a logic field, the subroutine may include any logic element that is valid in that logic field. A subroutine may also be used in an expression field provided that the Return statement is used to return a value to the expression field. When a macro is used in a logic field, the macro may include any logic element that is valid in that logic field. Graphic StatementĪ macro may be used in any expression field, but the macro may only contain expressions which return a value (e.g., Entries(LOC1), U(5,1)). External Spreadsheet FileĮntity Location Expression File. Operation Statements (Group 2)įree, Get, Jointly Get, and Use. ![]() Operation Statements (Group 1)Īccum, Combine, Create, Group, Join, Load, Match, Move, Rename, Route, Split As, Ungroup, and Unload. (You may not use the Log statement in Initialization or Termination Logic.) 15. , /*.*/), Debug, Dec, Display, Do.Until, Do.While, Goto, If.Then/ If.Then.Else, Inc, Int, Local Variable, Log, MapArr, O rder, Pause, Prompt, Read, Real, Reset, Reset Stats, Return, Report, Send, SetRate, Stop, String Expressions, Sound, Trace, View, WarmUp, While.Do, and Write/ Writeline/ XWrite. General Statements: (Run-Time Only)Īctivate, Animate, Assignment, Begin End, Break, BreakBLK, Close, Comment(#, GetCost(), GetResRate(), IncEntCost, IncLocCost, and IncResCost. Off-Shift & Break Logic-Specific System Functions & StatementsĭTLeft(), Priority, and Skip. Preemption Logic-Specific System Functions Shift-Specific System FunctionsįorLocation(), ForResource(). Downtime-Specific System FunctionĭTDelay(). (The Last function is valid only in Node Entry Logic and the Next function is valid only in Node Exit Logic.) 9. General System FunctionsĬap(), C alDay(), C alDom(), C alHour(), C alMin(),C alMonth(), C alYear(), Clock(), Contents(), DownQty(), Entries(), FreeCap(), FreeUnits(), OwnedResource(), TimesUsed(), U nits(), and V ariable(). Entity-Specific System Functions and AttributesĮntity(), GroupQty(), ResQty(). Referencing a location attribute in any expression or assigning to a location attribute. Numbers, Variables, Math Functions, Functions Table, Distribution Functions, XSUB(), and Name Functions (i.e., RES(), ENT(), LOC()). The table also tells where you may use an expression or statement. Below is a list of all expressions and statements by category, and a table telling which fields evaluate at translation and which fields MedModel evaluates continuously during a simulation. MedModel evaluates others as necessary throughout the simulation. Some evaluate only once when the model prepares to run a simulation, called the translation time. MedModel evaluates v arious fields and logic at different times during a simulation run.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |