MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015275ParaView(No Category)public2015-01-22 05:012016-08-12 09:59
ReporterVadim SANDLER 
Assigned ToTristan Coulange 
PrioritynormalSeverityminorReproducibilityunable to reproduce
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version4.2 
Target VersionFixed in Version 
ProjectParaViS
Topic Name
Typeincorrect functionality
Summary0015275: Calculator filter grants forbidden calculation and do not prevent errors
DescriptionWhen using the calculator filter in ParaView, it has been noticed 2 issues :

- forbidden calculations as /0, sqrt(negative number), ln(0)... return 0 value as a result which is not intuitive;

- if we fill in a wrong formula, for instance cossin(my_field) or my_field**2, there is no warning or error message display. The "Result" field is simply not available which is, once more, not really intuitive.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-01-22 05:01Vadim SANDLERNew Issue
2015-01-22 05:01Vadim SANDLERAssigned To => Tristan Coulange
2015-03-16 10:39Tristan CoulangeNote Added: 0034308
2015-03-16 10:40Tristan CoulangeReproducibilityhave not tried => unable to reproduce
2016-08-12 09:59Kitware RobotNote Added: 0038763
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved

Notes
(0034308)
Tristan Coulange   
2015-03-16 10:39   
Hello,

Indeed for calculations like /0, sqrt(negative number), ln(0)... the filter returns 0 by default. But it can return another value thanks to the option "Replacement value", or display a warning if the option "Replace Invalid Results" is unchecked. These options are just below the buttons.

The wrong formulas already display a warning.

And for both cases, the new array generated has the suffix "(?)" to show that there was a problem.

Feel free to tell me if I missed something.

Tristan
(0038763)
Kitware Robot   
2016-08-12 09:59   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.