Open BenWibking opened 1 year ago
Interesting, the expression lang takes these as a string arg to field function to avoid this very issue.
But it sounds like we have a bug where we aren't sanitizing the name in the generated OCCA C++ code.
I don't have workaround, I'll need to explore a fix for you in the OCCA code generation.
The JIT expression compiler incorrectly interprets field names containing dashes (e.g.
field('x-GasMomentum')
) in expressions and can't compile them:The relevant part of the error message is:
Is there a workaround for this? Or do I need to rename my fields so they don't contain dashes?