You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If one defines a parameter/variable in main.gms to configure the behaviour of a specific module, it has to be named cm_ instead of c123_ for codeCheck() to succeed. That is counter-intuitive and reduces lucidity, as elements used only in one module look as if they were relevant to core as well.
As an example, check cm_indst_H2costAddH2Inv in REMIND, which could be renamed c37_indst_H2costAddH2Inv if codeCheck() would get this right.
The text was updated successfully, but these errors were encountered:
This is the intended behavior as everything which is not part of a module is part of core. If you want to use c37_... instead of cm_..... you can declare the parameter/variable directly in the corresponding module. See for instance here
If one defines a parameter/variable in
main.gms
to configure the behaviour of a specific module, it has to be namedcm_
instead ofc123_
forcodeCheck()
to succeed. That is counter-intuitive and reduces lucidity, as elements used only in one module look as if they were relevant to core as well.As an example, check
cm_indst_H2costAddH2Inv
in REMIND, which could be renamedc37_indst_H2costAddH2Inv
ifcodeCheck()
would get this right.The text was updated successfully, but these errors were encountered: