Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.8
    • Fix Version/s: None
    • Component/s: Results management
    • Labels:
      None
    • Sprint:
      May 2015

      Description

      When the user inputs a DL, the system calculates the uncertainty based on that value. For example, if the user inputs '< 10', the system uses 10 to calculate the uncertainty. This is a wrong behavior. For DL results, the system must not calculate the uncertainty, but leave it empty

        Issue Links

          Activity

          Hide
          leonardorojass Leo added a comment -

          Yes, it is working! I have noticed that after this change the precision calculation in scientific notation is not working according to the uncertainty.

          Show
          leonardorojass Leo added a comment - Yes, it is working! I have noticed that after this change the precision calculation in scientific notation is not working according to the uncertainty.
          Show
          xispa Jordi (Inactive) added a comment - Should work now: https://github.com/labsanmartin/Bika-LIMS/commit/8065939f61aa9bacb7d71b51214a96de643995d2
          Hide
          leonardorojass Leo added a comment -

          Jordi, it is working, thanks! For some analysis the system adds more significant digits from the ones specified in the LDL field. For example one AS have LDL = 0.01 but in the results field it shows "<0,0100" after submitting to verification.

          Show
          leonardorojass Leo added a comment - Jordi, it is working, thanks! For some analysis the system adds more significant digits from the ones specified in the LDL field. For example one AS have LDL = 0.01 but in the results field it shows "<0,0100" after submitting to verification.
          Hide
          xispa Jordi (Inactive) added a comment -

          Leo, upgrade to your hotfix/3.1.8. You must run the upgrade step 3.1.8 and do a Ctrl+F5 later.

          Show
          xispa Jordi (Inactive) added a comment - Leo , upgrade to your hotfix/3.1.8. You must run the upgrade step 3.1.8 and do a Ctrl+F5 later.

            People

            • Assignee:
              xispa Jordi (Inactive)
              Reporter:
              xispa Jordi (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile