Currently, there are three options on DefaultSymbol for managing the String
representation of numeric Symbols:
_displayNumericPrecision
_displayScientificGreaterNIntegerPlaces
_displayScientificAfterNDecimalPlaces
which are global in the system. However, the PRAiSEDemoApp sets these fairly
low (originally set to 2,6,4 now 6,6,6 to accommodate default translate rules
precision). Therefore when a Model in instantiated and converted to its String
representation to work with the LBPQueryEngine API (which accepts String
representations of the input query and model in order to support working in
remote/server settings so that Expressions don't have to be passed directly)
precision defined in the model can be lost.
Original issue reported on code.google.com by ctjoreilly@gmail.com on 15 Jul 2013 at 7:05
Original issue reported on code.google.com by
ctjoreilly@gmail.com
on 15 Jul 2013 at 7:05