ARE THE SAME: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:ARE_THE_SAME}} | |||
'''ARE_THE_SAME''' statements tell ASCEND that two variables should be merged such that they actually refer to the same thing: when one changes, the other changes at exactly the same time. One can still refer to the variable by either name, but it will only occupy a single place in the solver's list of variables. | '''ARE_THE_SAME''' statements tell ASCEND that two variables should be merged such that they actually refer to the same thing: when one changes, the other changes at exactly the same time. One can still refer to the variable by either name, but it will only occupy a single place in the solver's list of variables. | ||
Latest revision as of 23:51, 13 December 2010
ARE_THE_SAME statements tell ASCEND that two variables should be merged such that they actually refer to the same thing: when one changes, the other changes at exactly the same time. One can still refer to the variable by either name, but it will only occupy a single place in the solver's list of variables.
For examples see Object-oriented modelling.
Note that there are some cases, such as within parameterised models, where ARE_THE_SAME is not allowed. In these cases, you can often achieve what is required using ALIASES instead.
See also ALIASES, IS_REFINED_TO, and WILL_BE_THE_SAME.