Uploaded image for project: 'Cannabis'
  1. Cannabis
  2. CAN-50

Decimal Precision on Converted results

    Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None

      Description

      At the moment, Converted results are displayed with the same precision (and significant figures) as the primary result which in many cases are not technically correct.

      It could be deducted from the formula, but for Ace we should simply add it to the Unit Conversion table.

      Not sure Sig Figures are applied in BC yet, use as place holder here for now

        Activity

        Hide
        lemoene lemoene added a comment -

        This I realise now is actually AS dependent, eg a unit conversion can be used on ASs of different decimal precisions... from 0 to 0.1234 say.

        Stand by, there has to be a formula

        Show
        lemoene lemoene added a comment - This I realise now is actually AS dependent, eg a unit conversion can be used on ASs of different decimal precisions... from 0 to 0.1234 say. Stand by, there has to be a formula
        Hide
        lemoene lemoene added a comment -

        This should go away now we are using standard Bika Calculations

        Show
        lemoene lemoene added a comment - This should go away now we are using standard Bika Calculations
        Hide
        lemoene lemoene added a comment -

        I predict not... see Dry Result which uses the same function

        We also cannot blindly apply the same precision as for the AS itself, but is first option . Please do like that

        Interims in the Views and COA are displayed with the same number of decimals as that of the final AS

        Except where notr all decimals captured, display only those captured, e.g.

        For an AS set to 3 decimals, but captured as 1.2 g only, display and print just 1.2, not 1.200 as that indicates higher precision than achieved

        If that algorithm needs a revisit in core, it is way overdue

        In the end, we'll have to add a precision column for the interims, eg 1.0 mg = 0.0010 g...

        Show
        lemoene lemoene added a comment - I predict not... see Dry Result which uses the same function We also cannot blindly apply the same precision as for the AS itself, but is first option . Please do like that Interims in the Views and COA are displayed with the same number of decimals as that of the final AS Except where notr all decimals captured, display only those captured, e.g. For an AS set to 3 decimals, but captured as 1.2 g only, display and print just 1.2, not 1.200 as that indicates higher precision than achieved If that algorithm needs a revisit in core, it is way overdue In the end, we'll have to add a precision column for the interims, eg 1.0 mg = 0.0010 g...
        Hide
        lemoene lemoene added a comment -

        For the purpose of the sprint

        Simply apply the the same precision as for the unconverted result?

        Show
        lemoene lemoene added a comment - For the purpose of the sprint Simply apply the the same precision as for the unconverted result?

          People

          • Assignee:
            Unassigned
            Reporter:
            lemoene lemoene
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Agile