|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0014800||ParaView||(No Category)||public||2014-06-13 10:28||2016-08-12 09:59|
|Assigned To||Utkarsh Ayachit|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0014800: No consistency for Catalyst generated scripts and state files with regards to floating point number formatting|
|Description||Bob Kares sent an email with:|
Why is there no consistency in the output format used for numbers that appear in the Catalyst generated .py script? For example, one of my palettes uses a data range -2e+10 to 2e+10. When I look at what the Catalyst plugin generates by default, the CreatePiecewiseFunction line generated by the Catalyst plugin has -20000000000 and 20000000000. Sometimes "e" format is used instead, but I can’t really discern what the rule is.
This same problem occurs in the state files ParaView writes out. This is
more than a cosmetic issues because it makes data values you know are
there hard to find with a text editor.
|Tags||No tags attached.|
Kitware Robot (administrator)
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.
|2014-06-13 10:28||Andy Bauer||New Issue|
|2014-06-13 10:28||Andy Bauer||Assigned To||=> Utkarsh Ayachit|
|2016-08-12 09:59||Kitware Robot||Note Added: 0038581|
|2016-08-12 09:59||Kitware Robot||Status||backlog => closed|
|2016-08-12 09:59||Kitware Robot||Resolution||open => moved|
|Copyright © 2000 - 2018 MantisBT Team|