Re: MuPad 3.0 extraction of individual eigenvectors
From: Brad Cooper (Brad.Cooper_17_at_bigpond.com)
Date: 11/12/04
- Next message: stijn: "Re: MAPLE print content of myfile.m to maple standard output"
- Previous message: sean_incali: "Re: matlab to MMA, need some help converting this code."
- In reply to: John O'Flaherty: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Next in thread: Torsten Metzner: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Reply: Torsten Metzner: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Reply: Christopher Creutzig: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Nov 2004 10:25:24 GMT
Hi John, Ralf, Torsten,
I have read your replies with a great deal of interest.
The answers I received have given me a very clear understanding of how to
use op, map and indexing to do just about anything I need in the future to
extract arguments from the output of one command to use as input into
another.
In fact, I am reasonably confident that I will not need to ask a question of
this nature again (let's not get too carried away here, but I am fairly
sure).
John's idea of point and click to extract arguments has merit. Of course you
still want procedures you can embed in code that you may need to write. In
that case, the aforementioned use of op, map and indexing is still required.
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. I suspect most of
the required techniques are sprinkled in amongst the existing documentation,
but to have them pulled together in one place for the specific purpose of
showing by example what to do may be useful. For example, I was unaware of
op@op which is a nice little nick nack described in this current set of
newsgroup replies.
>From what I have been shown in this current set of newsgroup messages, I
"believe" I would probably be OK in the future without the How To document,
but it may be a nice resource for the larger MuPad community - particularly
new users. I wonder if other people agree.
BTW thanks to you guys for your really clear and helpful replies.
Cheers,
Brad
PS I haven't sent an official suggestion to the MuPad developers yet, but I
thought to see if anything relevant comes from other users first.
- Next message: stijn: "Re: MAPLE print content of myfile.m to maple standard output"
- Previous message: sean_incali: "Re: matlab to MMA, need some help converting this code."
- In reply to: John O'Flaherty: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Next in thread: Torsten Metzner: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Reply: Torsten Metzner: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Reply: Christopher Creutzig: "Re: MuPad 3.0 extraction of individual eigenvectors"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|