Details

    • Proposal:
      Hide

      6.16.12
      now
      Syntax: BESSELI( Integer X ; Number N )

      should be
      Syntax: BESSELI( Number X ; Number N )

      6.16.13
      now
      Syntax: BESSELJ( Integer X ; Number N )

      should be
      Syntax: BESSELJ( Number X ; Number N )

      6.16.14
      now
      Syntax: BESSELK( Integer X ; Number N )
      Constraints: N >= 0, INT(N)=N;

      should be
      Syntax: BESSELK( Number X ; Number N )
      Constraints: X≠0, N >= 0, INT(N)=N;

      6.16.15
      now
      Syntax: BESSELY( Integer X ; Number N )
      Constraints: N >= 0, INT(N)=N;

      should be
      Syntax: BESSELY( Number X ; Number N )
      Constraints: X≠0, N >= 0, INT(N)=N;

      Show
      6.16.12 now Syntax: BESSELI( Integer X ; Number N ) should be Syntax: BESSELI( Number X ; Number N ) 6.16.13 now Syntax: BESSELJ( Integer X ; Number N ) should be Syntax: BESSELJ( Number X ; Number N ) 6.16.14 now Syntax: BESSELK( Integer X ; Number N ) Constraints: N >= 0, INT(N)=N; should be Syntax: BESSELK( Number X ; Number N ) Constraints: X≠0, N >= 0, INT(N)=N; 6.16.15 now Syntax: BESSELY( Integer X ; Number N ) Constraints: N >= 0, INT(N)=N; should be Syntax: BESSELY( Number X ; Number N ) Constraints: X≠0, N >= 0, INT(N)=N;

      Description

      All Bessel function have in their description data-type Integer for the argument X. But no one of LibreOffice, Callibre, Gnumeric, MS Excel, AOO restrict it to integer, but all allow real numbers. Outside spreadsheets the domain "complex numbers" is common.

        Attachments

          Activity

          Hide
          rcweir Robert Weir (Inactive) added a comment -

          Discussed on TC call of 2013-08-19

          Spec contains language "Evaluators may evaluate expressions where N >= 0 returns a non-error value', which suggests that an implementation may evaluate at non-Integer values. However the language here is not very clear.

          We'll confirm that existing implementations have reversed the parameter order. If no implementation would break then we can fix via errata and ODF 1.3

          Show
          rcweir Robert Weir (Inactive) added a comment - Discussed on TC call of 2013-08-19 Spec contains language "Evaluators may evaluate expressions where N >= 0 returns a non-error value', which suggests that an implementation may evaluate at non-Integer values. However the language here is not very clear. We'll confirm that existing implementations have reversed the parameter order. If no implementation would break then we can fix via errata and ODF 1.3
          Hide
          regina.henschel Regina Henschel added a comment -

          The first parameter is the argument X and the second parameter is the order N. That is correct and not reversed. But the type of the first parameter X is not integer, but real. The second parameter N is integer.
          Applications allow calls with non-integer value for N and trunc it to integer internally for calculation of the Bessel function.

          Show
          regina.henschel Regina Henschel added a comment - The first parameter is the argument X and the second parameter is the order N. That is correct and not reversed. But the type of the first parameter X is not integer, but real. The second parameter N is integer. Applications allow calls with non-integer value for N and trunc it to integer internally for calculation of the Bessel function.
          Hide
          aguelzow Andreas Guelzow (Inactive) added a comment -

          Just for the record, the newest versions of Gnumeric (1.12.7) calculates the Bessel functions also for fractional order N. This was implemented on user request.

          Show
          aguelzow Andreas Guelzow (Inactive) added a comment - Just for the record, the newest versions of Gnumeric (1.12.7) calculates the Bessel functions also for fractional order N. This was implemented on user request.
          Hide
          rcweir Robert Weir (Inactive) added a comment -

          Discussed in TC call of 2013-09-16. Agreed to resolve per proposal.

          Show
          rcweir Robert Weir (Inactive) added a comment - Discussed in TC call of 2013-09-16. Agreed to resolve per proposal.
          Hide
          patrick Patrick Durusau added a comment -

          Applied in OpenDocument-v1.3-wd03-part4-openformula.odt

          Show
          patrick Patrick Durusau added a comment - Applied in OpenDocument-v1.3-wd03-part4-openformula.odt
          Hide
          regina.henschel Regina Henschel added a comment -

          The word "Number" is missing as data type to X in part Syntax in 6.16.15 BESSELY in wd03-part4.

          Show
          regina.henschel Regina Henschel added a comment - The word "Number" is missing as data type to X in part Syntax in 6.16.15 BESSELY in wd03-part4.
          Hide
          patrick Patrick Durusau added a comment -

          Thanks for the catch Regina! Fixed in OpenDocument-v1.3-wd04-part4-openformula.odt

          Show
          patrick Patrick Durusau added a comment - Thanks for the catch Regina! Fixed in OpenDocument-v1.3-wd04-part4-openformula.odt
          Hide
          regina.henschel Regina Henschel added a comment -

          Clone for ODF 1.2 Errata 01 is in https://issues.oasis-open.org/browse/OFFICE-3962

          Show
          regina.henschel Regina Henschel added a comment - Clone for ODF 1.2 Errata 01 is in https://issues.oasis-open.org/browse/OFFICE-3962

            People

            • Assignee:
              Unassigned
              Reporter:
              regina.henschel Regina Henschel
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: