Best way to display Exponential values in Data Page

Solved1.32K viewsCube exponential values protocol
1
0 Comments

What is the best way to define exponential values in a protocol?
For example a value that can range between 1E-3 and 1E-10

Goals:

  1. readable in a data page
  2. able to trend
  3. able to add alarm thresholds
Mieke Dryepondt [SLC] [DevOps Advocate] Selected answer as best 29th June 2020

2 Answers

3
11.74K 4 Comments

Would the scientificNotation option on the Measurement -> Type tag do what you are looking for?

Laurens Moutton [SLC] [DevOps Enabler] Posted new comment 30th June 2020
Mieke Dryepondt [SLC] [DevOps Advocate] commented

Thanks, this is indeed what I need.
Only the trend graph is now no longer readable:
– only zooms until 0.1 steps
– selected value shows the full (very small / large value)

Could the graph apply a similar dynamic display?
Is this feasible for a new cube feature?
Laurens Moutton [SLC] [DevOps Enabler] commented

How do you get it to work correct for small numbers?
When using universal notation, 2 decimals:
-If I perform a set from a QAction with 2235, then the UI shows 2,24E+003
-If I perform a set from a QAction with double 0.02235, then the UI shows 2,00E-002
When going one digit smaller to 0.002235, then the UI shows 0,00E+000 so I need to increase the digits to 3, and then it shows 2,000+E-003
It seems that the decimals is used duplicate: it’s used for the “raw” value to take that number of decimals, but it’s also used to display the “E” value with such amount of decimals and how smaller the number is how more “0” are appended. E.g. 0.000002235 if I specify 6 decimals then it’s capping the raw value to 0.000002 (6 decimals) and then shows it as 2.000000E-006 . How did you get to let it display e.g. 2 decimals but still display a value of E-006? How does the parameter definition look like?
João Severino [SLC] [DevOps Catalyst] commented

I have only used it before to represent large numbers, so I had not noticed the issue Laurens is mentioning, I tried playing around with the Interprete and Display decimals tag but the behavior seems to always be the same.

Could this be something to improve on as a new feature, where, for instance, the decimals on the Display tag are used to indicate how many decimals are shown in the scientific notation and the decimals on the Interprete are used to limit the actual precision of the raw value?
Laurens Moutton [SLC] [DevOps Enabler] commented

I have created task 132515 for this so we will be able to display E-006 without having to specify decimals > 6, with this task it shouldn’t cap the original raw value before converting to the scientific equivalent.
You are viewing 1 out of 2 answers, click here to view all answers.