Re: MuPad 3.0 extraction of individual eigenvectors

From: Torsten Metzner (tom_at_mupad.de)
Date: 11/12/04 

Date: Fri, 12 Nov 2004 12:34:29 +0000 (UTC)

Brad Cooper <Brad.Cooper_17@bigpond.com> wrote:
>This leads me to thinking a How To document with several examples would be
>very useful. It is often the case that a user of MuPad does not want to
>simply take output from a command to MuPad, but the user often wants do
>something with it i.e. feed it into another command.
>
>I don't think it has to be a particularly lengthy document, but it would be
>good to have a set of examples graded from the pretty standard things people
>want to do and also include a few of the more esoteric.

And here the problems starts. What are "standard things" because there
are so many MuPAD libraries and every user has another view to what is
important for him. I think you cannot solve this with one small
document. And there exist a lot of "basic" documentation. One resource
which is available is the tutorial. There you can select the chapters
about the topics you are interested in. Especially chapter 4 about the
MuPAD objects should demonstrate a lot of "standard things". Then we
have the quick reference. With die MS Windows version there comes two
introduction notebooks. For german users (sorry not available in
english) there are a lot of examples available under:
   http://schule.mupad.de/material/index.shtml

But if you have a good idea how such a "how to document" can be
structered we are very interested. Please let us know.

At least some advertising for a book. The book from M.Majewski:
  MuPAD Pro Computing Essentials, ISBN: 3540219439
is a very good introduction to MuPAD.

In general I agree that for most MuPAD commands (where the output is
"not clear"), there should be one or two examples how to use the output
for another command or at least an option to get the specific data
directly. But again here is the question how verbose the documentation
should be. For e.g. standard data types like lists, sets, sequences
there should be normally no need to do this, because if you wants to
work effective with such a system some basics must be known.

Have a nice weeekend,
Torsten.

Relevant Pages

  • Re: MuPad 3.0 Calculus of Variations - syntax
    ... I forwarded your news article to Werner Seiler ... in the standard `diff' notation of MuPAD. ...
    (sci.math.symbolic)
  • Re: MuPad 3.0 extraction of individual eigenvectors
    ... > that case, the aforementioned use of op, map and indexing is still required. ... way of asking MuPAD “if I wanted to extract this, ... > something with it i.e. feed it into another command. ... general not be eigenvectors any longer: ...
    (sci.math.symbolic)
  • MuPAD: TeX output bug?
    ... We have trouble with generating TeX output via generate::TeX in ... Is there anything wrong or does command generate::TeX work only ... Why does MuPAD return wrong result and ...
    (sci.math.symbolic)
  • MuPAD (Win 3.0 Pro) Minutia
    ... I'm a new'ish MuPAD user and undergraduate student battling with both ... first year calculus and MuPAD 3.0 Pro. ... it either opens in a non-maximized window, or it opens in a maximized ... One of the purposes of the MuPAD's "is" command is to "checks whether ...
    (sci.math.symbolic)