MantisBT - ParaView
View Issue Details
0009695ParaViewBugpublic2009-10-12 14:562010-05-06 16:59
Sven Buijssen 
Zhanping Liu 
normalminoralways
closedfixed 
3.6 
 
0009695: Calculator: Data Array Names must not start with strings that are mathematical functions
Load attached state file.
It uses calculator to create a data array whose name starts with "norm". This confuses the parser of subsequent calculator filters which issues:

Syntax error: input to math function not in parentheses; see position 8

This affects any mathematical function defined in VTK/Common/vtkFunctionParser.cxx:GetMathFunctionNumber()

Tested with PV 3.6.1 and CVS HEAD on Linux 32-bit.
No tags attached.
? math-function-name-not-as-substring.3.8.pvsm (157,426) 2010-05-05 17:08
https://www.vtk.org/Bug/file/8092/math-function-name-not-as-substring.3.8.pvsm
Issue History
2009-10-12 14:56Sven BuijssenNew Issue
2009-10-12 14:56Sven BuijssenFile Added: math-function-name-not-as-substring.pvsm
2010-05-05 17:08Sven BuijssenFile Added: math-function-name-not-as-substring.3.8.pvsm
2010-05-05 17:08Sven BuijssenNote Added: 0020603
2010-05-05 17:22Zhanping LiuStatusbacklog => tabled
2010-05-05 17:23Zhanping LiuAssigned To => Zhanping Liu
2010-05-05 17:25Zhanping LiuFile Deleted: math-function-name-not-as-substring.pvsm
2010-05-05 17:27Zhanping LiuNote Added: 0020606
2010-05-05 17:28Zhanping LiuStatustabled => @80@
2010-05-06 16:59Alan ScottNote Added: 0020634
2010-05-06 16:59Alan ScottStatus@80@ => closed
2010-05-06 16:59Alan ScottResolutionopen => fixed

Notes
(0020603)
Sven Buijssen   
2010-05-05 17:08   
I've recreated the pipeline (with PV 3.8.0 RC2) as the initial state file contained an error in the function that is only visible now that the math function parsing error is fixed (got fixed along with 0009208).
(0020606)
Zhanping Liu   
2010-05-05 17:27   
The reported problem does not occur any more as it was actually resolved by an eariler fix (to bug 0009208). Now the attached state file works fine with ParaView.
(0020634)
Alan Scott   
2010-05-06 16:59   
Fixed with a previous fix.