The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Macro values not VALIDATED correctly
Hi
currently macro values are not always recognized as its proper "compiled" type and tons of error messages are thrown.
These bogus errors just obscure possible real errors(and it just looks plain bad -_-).
For example when I use a macro for substituting Label attribute name, the validation wont recognize the %{LabelAttName} as a proper correct Label type.
thx
currently macro values are not always recognized as its proper "compiled" type and tons of error messages are thrown.
These bogus errors just obscure possible real errors(and it just looks plain bad -_-).
For example when I use a macro for substituting Label attribute name, the validation wont recognize the %{LabelAttName} as a proper correct Label type.
thx
0
Answers
Best, Marius
yeah mama and me are always right ;D
Yes the bug is talking about exactly the same thing but using nicer wording than me -_^.
ANOTHER thing though:
Macro CANNOT be used to Substitute a numerical value in e.g. Discretize operator(discretization threashold)).
It would be nice to be able to substitute ANY value in any operator.
ok why not make the value already a negative number.... I say: why would I?
When a simple expression is used as a parameter %{val1}-%{val2} .... it is parsed and substituted (e.g. as 3-1) but not executed.
Best, Marius
thx , M.
f
p.s.: I think I am not the only one who does not utilize the macros to their fullest, maybe you should dedicated some space to it in the upcoming Operator manual.
p.p.s.:It turned out to be more of a problem solving than a feature request.