No consistency for Catalyst generated scripts and state files with regards to floating point number formatting
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
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.