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
When a variable is unknown, gt4py.cartesian expects it to be defined via the __externals__ mechanism. This in itself could be the subject of a ticket, but here we will assume it's the right behavior.
When the undefined variable is from a stencil the error is mildly helpful
gt4py.cartesian.frontend.exceptions.GTScriptSymbolError: Unknown symbol 'UNDEF_VAR' symbol in'<source>' (line: 3, col: 32)
The <source> field should at least give a stencil name. Running with build_info["debug"]=True doesn't help.
When the undefined variable is from a gtscript.function the error is even less readable:
gt4py.cartesian.frontend.exceptions.GTScriptSymbolError: Unknown symbol ValueError symbol in'<source>' (line: 5, col: 20)
When a variable is unknown,
gt4py.cartesian
expects it to be defined via the__externals__
mechanism. This in itself could be the subject of a ticket, but here we will assume it's the right behavior.When the undefined variable is from a stencil the error is mildly helpful
The
<source>
field should at least give a stencil name. Running with build_info["debug"]=True doesn't help.When the undefined variable is from a
gtscript.function
the error is even less readable:Example code:
Parent: #49
gtscript.function
reports name of the function or at least calling stencilThe text was updated successfully, but these errors were encountered: