[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #52685] redundant sentence in meansq docstring

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #52685] redundant sentence in meansq docstring
Date: Tue, 19 Dec 2017 14:37:31 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #14, bug #52685 (project octave):

The "by" symbol looks good in LaTeX.  In plain text, I guess I'm sort of used
to seeing m x n.  However, I started using m-by-n in the patch, especially in
cases where there were a lot of variables involved.  It's more a visual
digestion sort of thing.  Without the hyphens, it starts to be: x is t x k, e
is p x t, y is k x p, and c is kt x pt.  It looks like one big strung-together
set of foreign letters.

Upper case versus lower case matrix size parameter isn't too critical for me. 
I'm comfortable with either so long as it is consistent in a particular
function doc.  In signal processing, we typically use upper case limits,
especially N.  But in pure math, it's often lower case limits.

I think the upper-case, lower-case variable meaning matrix vs. vector vs.
function input variable question is more critical.

In the ols.m documentation, I think I'll change use of "vec(e)" to just plain
"e", i.e., @var{e}.  I don't know what was meant--if anything--by the vec()
function.  kron(s,I) I think is simply supposed to be "s I" in math speak,
that is the residuals are independent with the same variance.  But right, one
typically would write s^2 I where s is standard deviation (of a normal r.v.).


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]