OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Issue Comment Edited: (OFFICE-1170) PublicComment: Re: [office-comment] ODFF: list of suggestions



    [ http://tools.oasis-open.org/issues/browse/OFFICE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128#action_15128 ] 

Eike Rathke edited comment on OFFICE-1170 at 12/10/09 6:18 PM:
---------------------------------------------------------------

Most topics of the post are already covered, the following are left:

> *Formulae: - I suspect that the integral may need to be from -infinity=20
> not 0 for the cumulative dist function (as with NORMDIST). I can't find=
=20
> this formula on the net - normally it seems to be quoted as=20
> 1/2+1/2*ERF((LN(x)-u)/(s*SQRT(2))) - which does seem to produce the same=
=20
> results, and may be preferable if it is standard practice. Or could be=20
> defined in terms of NORMDIST or NORMSDIST which is the simplest.

[ed:] The current draft has that correct, see also comment by Andreas Guelzow below.


> PROB
> *This needs to specify if Data must be ordered or not (unordered?).
> *It would also be better to be clear about whether Data must be=20
> sequential (is 1, 2, 3, 5 (missing 4) OK?) and/or integer (is 1, 2.5, 3,=
=20
> 4 OK?).
> *It would also be better to be clear about whether Start and End need to=
=20
> exist within Data (no?) and also whether they can be higher/lower than=20
> the max/min values in Data (yes?)
> * It would also be better to be clear about whether Start can be higher=
=20
> than End. Although they're defined as lower/upper bounds, is 'Start>End'=
=20
> an error, or valid with a probability of 0 returned?
> * This needs to specify how the result is calculated if End is omitted=20
> and Start is not present in Data (Calc returns 0).
> * This needs to specify the type of error returned - eg #N/A if Data,=20
> Probability are different lengths. This is important because #N/A is a=20
> specific (testable) type of error.

[ed:] Broken out to OFFICE-2246


> "Array Functions"
> This categorisation seems to me to be inconsistent. Functions which=20
> return arrays are:
> MINVERSE, MMULT, MUNIT, TRANSPOSE, FREQUENCY, GROWTH, LINEST, LOGEST,=20
> TREND
> Functions which have ForceArray parameters are:
> MDETERM, MINVERSE, MMULT, SUMPRODUCT, SUMX2MY2, SUMX2PY2, SUMXMY2,=20
> CORREL, COVAR, FORECAST, FTEST, INTERCEPT, MODE, PEARSON, PROB, RSQ,=20
> SLOPE, STEYX, TTEST (and LOOKUP sometimes).
> This doesn't relate to the current functions listed as array functions.=
=20
> We have for instance SUMPRODUCT listed as an array function (but it's=20
> really a maths function) but MODE listed in stats (OK) - but both force=
=20
> array_mode calculation. Surely either both should be 'array functions'=20
> or both where they belong.
> Perhaps only matrix functions should be in this category: MINVERSE,=20
> MMULT, MUNIT, TRANSPOSE, MDETERM. It could then be called 'matrix=20
> functions'.

[ed:] Broken out to OFFICE-2247


      was (Author: erack):
    Most topics of the post are already covered, the following are left:

> *Formulae: - I suspect that the integral may need to be from -infinity=20
> not 0 for the cumulative dist function (as with NORMDIST). I can't find=
=20
> this formula on the net - normally it seems to be quoted as=20
> 1/2+1/2*ERF((LN(x)-u)/(s*SQRT(2))) - which does seem to produce the same=
=20
> results, and may be preferable if it is standard practice. Or could be=20
> defined in terms of NORMDIST or NORMSDIST which is the simplest.

[ed:] TODO: someone with knowledge in this domain?


> PROB
> *This needs to specify if Data must be ordered or not (unordered?).
> *It would also be better to be clear about whether Data must be=20
> sequential (is 1, 2, 3, 5 (missing 4) OK?) and/or integer (is 1, 2.5, 3,=
=20
> 4 OK?).
> *It would also be better to be clear about whether Start and End need to=
=20
> exist within Data (no?) and also whether they can be higher/lower than=20
> the max/min values in Data (yes?)
> * It would also be better to be clear about whether Start can be higher=
=20
> than End. Although they're defined as lower/upper bounds, is 'Start>End'=
=20
> an error, or valid with a probability of 0 returned?
> * This needs to specify how the result is calculated if End is omitted=20
> and Start is not present in Data (Calc returns 0).
> * This needs to specify the type of error returned - eg #N/A if Data,=20
> Probability are different lengths. This is important because #N/A is a=20
> specific (testable) type of error.

[ed:] TODO: check current status.


> "Array Functions"
> This categorisation seems to me to be inconsistent. Functions which=20
> return arrays are:
> MINVERSE, MMULT, MUNIT, TRANSPOSE, FREQUENCY, GROWTH, LINEST, LOGEST,=20
> TREND
> Functions which have ForceArray parameters are:
> MDETERM, MINVERSE, MMULT, SUMPRODUCT, SUMX2MY2, SUMX2PY2, SUMXMY2,=20
> CORREL, COVAR, FORECAST, FTEST, INTERCEPT, MODE, PEARSON, PROB, RSQ,=20
> SLOPE, STEYX, TTEST (and LOOKUP sometimes).
> This doesn't relate to the current functions listed as array functions.=
=20
> We have for instance SUMPRODUCT listed as an array function (but it's=20
> really a maths function) but MODE listed in stats (OK) - but both force=
=20
> array_mode calculation. Surely either both should be 'array functions'=20
> or both where they belong.
> Perhaps only matrix functions should be in this category: MINVERSE,=20
> MMULT, MUNIT, TRANSPOSE, MDETERM. It could then be called 'matrix=20
> functions'.

[ed:] TODO: check what we have changed there already and what's left to do, if any.

  
> Public Comment: Re: [office-comment] ODFF: list of suggestions
> --------------------------------------------------------------
>
>                 Key: OFFICE-1170
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1170
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Eike Rathke
>            Priority: Blocker
>             Fix For: ODF 1.2
>
>
> Copied from office-comment list
> Original author: Eike Rathke <erack@sun.com> 
> Original date: 21 Dec 2008 20:54:35 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200812/msg00029.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]