bugGNU Octave - Bugs: bug #52814, some obvious bugs in document...

 
 

bug #52814: some obvious bugs in document Chapter 21

Submitter:  None
Submitted:  Fri 05 Jan 2018 07:37:33 AM UTC
   
 
Category:  Documentation Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Documentation
Status:  Fixed Assigned to:  None
Originator Name:  Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 4.2.1
Operating System:  * Any Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 08 Jan 2018 06:53:57 PM UTC, comment #8: 

Rik,
OK. If this is Texinfo's very own style then it looks like
that is it.  Makes things easy, but not perfect. There are
reasons why I do not use Texinfo....

Michael Godfrey <godfrey>
Group Member
Mon 08 Jan 2018 05:45:28 PM UTC, comment #7: 

@Anonymous: Okay, thank you for your work.  That is a hard testing cycle to see if a bug is fixed, but if your network is slow I guess there are few other options.

Rik <rik5>
Group administrator
Mon 08 Jan 2018 05:24:11 PM UTC, comment #6: 

@Michael: Regarding gdbinit, the build process is being good.  It has noticed that you already have a gdbinit file, which you may have customized, and therefore it is not overwriting it with the default one that is shipped with Octave.  That feature has been in the build system for a long time, but perhaps this is the first time you noticed the message.  It isn't related to this cset.

Regarding the '.' as index entry.  We're using the default style that comes out of Texinfo with @printindex.  It works pretty well.  The function index, for example, has a large bold letter to start each section and then the function names are set in @code{} style below that.  There is no indenting easily available, alas.

Rik <rik5>
Group administrator
Mon 08 Jan 2018 11:30:20 AM UTC, comment #5: 

Rik,
I now notice that the * (dot actually) is intentional. It is
the heading for the following subsection. But, 2 things:
1. Would it be helpful to indent the following entries?
2. Then maybe larger type and bold for heading would
   not be necessary?

Just minor style issues.

Michael Godfrey <godfrey>
Group Member
Mon 08 Jan 2018 11:16:42 AM UTC, comment #4: 

Rik,
This may not relate to this bug, but my build with
your latest updates showed the following:

  MAKEINFO doc/interpreter/octave.info
  GEN      doc/interpreter/doc-cache
refusing to overwrite test/.gdbinit with newer version from etc/gdbinit
refusing to overwrite .gdbinit with newer version from etc/gdbinit
  TEXI2DVI doc/interpreter/octave.dvi
  DVIPS    doc/interpreter/octave.ps
  TEXI2PDF doc/interpreter/octave.pdf

Just for information.


Also, the Manual is much better, but notice an extraneous "dot"
near the top of the right column first page of Operator Index.

Michael Godfrey <godfrey>
Group Member
Mon 08 Jan 2018 07:30:04 AM UTC, comment #3: 

From the Mercurial log I see that maintainers are very busy in developing recently. Thank you very much for taking time to apply these small patches.

Because I have a very bad network, I could neither perform an "hg clone" nor download an archive of the source files. So I don't know how to make a Mercurial changeset without the repo.  What I do recently is that
- when finding a bug, search locally in my computer (version 4.2.1 now) to try to gather all bugs of the same type;
- try to determine which source files are these bugs in;
- download only these source files (newest version) to see whether these bugs have already been fixed;
- edit these files and make a diff.

No need to add my name to the list of contributors. I'm grateful to Octave maintainers for Octave is very very useful.

Anonymous
Mon 08 Jan 2018 05:43:43 AM UTC, comment #2: 

I applied your patch here http://hg.savannah.gnu.org/hgweb/octave/rev/6e81c8a5add7.

You have contributed quite a few patches lately.  If you would like your name to appear in the list of contributors at the front of the Octave manual just let me know.  Also, if you like you can contribute Mercurial changesets, rather than just diffs, and have your name credited to the changes you make.

Marking this bug report as fixed and closing.

Rik <rik5>
Group administrator
Fri 05 Jan 2018 08:06:08 AM UTC, comment #1: 

Because the "left division" operators are also grouped "leftmost first", just like most other operators,

A \ B \ C == (A \ B) \ C != A \ (B \ C) == inv(A) inv(B) C

So we must be very careful when using multiple "left division" operators.

Anonymous
Fri 05 Jan 2018 07:37:33 AM UTC, original submission:  

It looks that there are many bugreports and changesets recently...
I directly put a possible patch here for maintainers convenience:

--- a/doc/interpreter/diagperm.txi
+++ b/doc/interpreter/diagperm.txi
@@ -275,7 +275,7 @@
 then @code{D*M} is equivalent to

 @example
-[D(1:n,n) * M; zeros(m-n, columns (M))],
+[D(1:n,:) * M; zeros(m-n, columns (M))],
 @end example

 @noindent
@@ -447,7 +447,7 @@
 @example
 @group
   [L, U, P] = lu (A); ## now L*U = P*A
-  x = U \ L \ P*b;
+  x = U \ (L \ P)*b;
 @end group
 @end example

@@ -526,7 +526,7 @@

 The primary distinction is that an assumed zero, when multiplied
 by any number, or divided by any nonzero number,
-yields *always* a zero, even when, e.g., multiplied by @code{Inf}
+yields @strong{always} a zero, even when, e.g., multiplied by @code{Inf}
 or divided by @code{NaN}.
 The reason for this behavior is that the numerical multiplication is not
 actually performed anywhere by the underlying algorithm; the result is



An explanation about the 2nd change:

the following equivalent expressions are all wrong

x = U \ L \ P * b
x = (U \ L) \ P * b
x = (U \ L \ P) * b
x = inv(inv(U) * L) * P * b


the following equivalent expressions are all right

x = U \ (L \ P) * b
x = U \ (L \ P * b)
x = inv(U) * inv(L) * P * b


these can be verified directly in Octave such as

A = randn(5);
b = randn(5,1);
x = A \ b;
[L, U, P] = lu (A);
L*U - P*A          ## L*U == P*A
x - U \ (L \ P)*b  ## x == U \ (L \ P)*b
x - U \ L \ P*b    ## x != U \ L \ P*b


Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by godfrey (Posted a comment)
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-01-08 rik5 StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code