Mercurial > hg > octave-nkf
changeset 2339:8d7454ead97e
[project @ 1996-07-24 07:18:22 by jwe]
author | jwe |
---|---|
date | Wed, 24 Jul 1996 07:19:06 +0000 |
parents | 18953de8c308 |
children | 599f8f054840 |
files | WWW/index.html WWW/mailing-lists/index.html WWW/preface.html WWW/readme.html |
diffstat | 4 files changed, 418 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
new file mode 100644 --- /dev/null +++ b/WWW/index.html @@ -0,0 +1,75 @@ +<!doctype html public "-//IETF//DTD HTML Strict//EN"> +<html> +<head> +<title> Octave -- a high-level language for numerical computations </title> +</head> + +<body> +<hr> +<h1>Octave</h1> +<hr> + +<p> +Octave is a high-level language, primarily intended for numerical +computations. It provides a convenient command line interface for +solving linear and nonlinear problems numerically. +</p> + +<h3>Source and Binaries</h3> +<p> +Octave source and binaries are available by anonymous ftp from +<a href="ftp://www.che.wisc.edu/pub/octave">ftp://www.che.wisc.edu/pub/octave</a>. +</p> + +<p> +Source and binaries for a port of Octave to OS/2 are available from +several sites, including: +</p> +<ul> + <li><a href="ftp.informatik.tu-muenchen.de/pub/comp/os/os2/math">ftp.informatik.tu-muenchen.de/pub/comp/os/os2/math</a> + <li><a href="wcarchive.cdrom.com/pub/os2/incoming">wcarchive.cdrom.com/pub/os2/incoming</a> + <li><a href="hobbes.nmsu.edu/incoming">hobbes.nmsu.edu/incoming</a> +</ul> + +<h3>Documentation</h3> +<p> +To get started, there is a +<a href="readme.html">brief introduction</a>, and also the +<a href="preface.html">preface</a> to the manual. For more +detailed information, you can browse the +<a href="http://www.che.wisc.edu/cgi-bin/info2www?(octave)">complete +documentation</a>, which has been converted to HTML directly from the +installed info files with +<a href="http://www.che.wisc.edu/info2www.html">info2www</a>. +</p> + +<p> +If you still have questions, there is always the +<a href="http://www.che.wisc.edu/cgi-bin/info2www?(octave-faq)Top"> +FAQ</a> (with answers). +</p> + +<h3>Mailing Lists</h3> +<p> +There are two active mailing lists devoted to Octave. The +<em>help-octave</em> mailing list is available for questions related +to using, installing, and porting Octave that are not adequately +answered by the Octave manual or by the FAQ. The <em>bug-octave</em> +list is used for reporting bugs. An archive of postings to both lists +are available <a href="mailing-lists">here</a>. +</p> + +<h3>Contributed Functions</h3> +<p> +An archive of contributed functions for Octave is available from +<a href="http://www.tsc.uvigo.es/GTS/Octave/oct_arch.html">http://www.tsc.uvigo.es/GTS/Octave/oct_arch.html</a>. +</p> + +<p> +<a href="http://www.che.wisc.edu/~jwe">John W. Eaton</a><br> +<a href="mailto:jwe@bevo.che.wisc.edu"><i>jwe@bevo.che.wisc.edu</i></a><br> +University of Wisconsin<br> +Department of Chemical Engineering<br> +Madison WI 53719 +</body> +</html>
new file mode 100644 --- /dev/null +++ b/WWW/mailing-lists/index.html @@ -0,0 +1,59 @@ +<title>Octave Mailing List Archives</title> + +<h2> +Octave Mailing List Archives +</h2> +<hr> + +<h3> +help-octave -- General discussion about using and installing Octave. +</h3> +<p> + +<ul> +<li><a href="help-octave/1996">1996</a> +<li><a href="help-octave/1995">1995</a> +<li><a href="help-octave/1994">1994</a> +<li><a href="help-octave/1993">1993</a> +<li><a href="help-octave/1992">1992</a> +</ul> + +<h3> +bug-octave -- Bug reports. Fixes are also sometimes posted to this list. +</h3> +<p> + +<ul> +<li><a href="bug-octave/1996">1996</a> +<li><a href="bug-octave/1995">1995</a> +<li><a href="bug-octave/1994">1994</a> +<li><a href="bug-octave/1993">1993</a> +<li><a href="bug-octave/1992">1992</a> +</ul> +<p> + +<h3> +octave-sources -- Enhancements contributed by Octave users. +</h3> +<p> + +<ul> +<li><a href="octave-sources/1996">1996</a> +</ul> +<p> + +If you would like to join the discussion and receive all messages sent +to these mailing lists, please send a short note to +help-octave-<b>request</b>@bevo.che.wisc.edu (to join help-octave) or +bug-octave-<b>request</b>@bevo.che.wisc.edu (to join bug-octave), or +octave-sources-<b>request</b>@bevo.che.wisc.edu (to join octave-sources). +<p> + +<b> +Please do NOT send subscription requests directly to the lists +themselves. +</b> +<p> + +Back to the +<a href="http://bevo.che.wisc.edu/octave.html>Octave home page</a>.
new file mode 100644 --- /dev/null +++ b/WWW/preface.html @@ -0,0 +1,164 @@ +<!doctype html public "-//IETF//DTD HTML Strict//EN"> +<html> +<head> +<title> Preface to the Octave Manual </title> +</head> + +<body> +<h2>Preface</h2> +<p> +Octave was originally intended to be companion software for an +undergraduate-level textbook on chemical reactor design being written by +James B. Rawlings of the University of Wisconsin-Madison and John +G. Ekerdt of the University of Texas. +</p> + +<p> +Clearly, Octave is now much more than just another `courseware' package +with limited utility beyond the classroom. Although our initial goals +were somewhat vague, we knew that we wanted to create something that +would enable students to solve realistic problems, and that they could +use for many things other than chemical reactor design problems. +</p> + +<p> +There are those who would say that we should be teaching the students +Fortran instead, because that is the computer language of engineering, +but every time we have tried that, the students have spent far too much +time trying to figure out why their Fortran code crashes and not enough +time learning about chemical engineering. With Octave, most students +pick up the basics quickly, and are using it confidently in just a few +hours. +</p> + +<p> +Although it was originally intended to be used to teach reactor design, +it has been used in several other undergraduate and graduate +courses in the Chemical Engineering Department at the University of +Texas, and the math department at the University of Texas has been using +it for teaching differential equations and linear algebra as well. If +you find it useful, please let us know. We are always interested to +find out how Octave is being used in other places. +</p> + +<p> +Virtually everyone thinks that the name Octave has something to do with +music, but it is actually the name of a former +<a href="http://www.engr.orst.edu/~reed/CSTR/profs.html">professor</a> +of mine who wrote a famous textbook on chemical reaction engineering, +and who was also well known for his ability to do quick `back of the +envelope' calculations. We hope that this software will make it +possible for many people to do more ambitious computations just as +easily. +</p> + +<p> +Everyone is encouraged to share this software with others under the +terms of the +<a href="cgi-bin/info2www?(octave)Copying">GNU General Public License</a> +as described at the beginning of this manual. You are also encouraged +to help make Octave more useful by writing and contributing additional +functions for it, and by reporting any problems you may have. +</p> + +<p> +Many people have already contributed to Octave's development. In +addition to John W. Eaton, the following people have helped write parts +of Octave or helped out in various other ways. +</p> + +<ul> +<li><em>Karl Berry</em> (karl@cs.umb.edu) wrote the <tt>kpathsea</tt> library +that allows Octave to recursively search directory paths for function +and script files.</li> + +<li><em>Georg Beyerle</em> (gbeyerle@awi-potsdam.de) contributed code to +save values in Matlab's <tt>.mat</tt>-file format, and has provided +many useful bug reports and suggestions.</li> + +<li><em>John Campbell</em> (jcc@bevo.che.wisc.edu) wrote most of the file +and C-style input and output functions.</li> + +<li><em>Brian Fox</em> (bfox@gnu.ai.mit.edu) wrote the <tt>readline</tt> +library used for command history editing, and the portion of this +manual that documents it.</li> + +<li><em>A. Scottedward Hodel</em> (scotte@eng.auburn.edu) contributed a +number of functions including <tt>expm</tt>, <tt>qzval</tt>, +<tt>qzhess</tt>, <tt>syl</tt>, <tt>lyap</tt>, and <tt>balance</tt>.</li> + +<li><em>Kurt Hornik</em> (Kurt.Hornik@ci.tuwien.ac.at) provided the +<tt>corrcoef</tt>, <tt>cov</tt>, <tt>kurtosis</tt>, <tt>pinv</tt>, and +<tt>skewness</tt> functions.</li> + +<li><em>Phil Johnson</em> (johnsonp@nicco.sscnet.ucla.edu) has helped to +make Linux releases available.</li> + +<li><em>Friedrich Leisch</em> (leisch@ci.tuwien.ac.at) provided the +<tt>mahalanobis</tt> function.</li> + +<li><em>Ken Neighbors</em> (wkn@leland.stanford.edu) has provided many +useful bug reports and comments on Matlab compatibility.</li> + +<li><em>Rick Niles</em> (niles@axp745.gsfc.nasa.gov) rewrote Octave's +plotting functions to add line styles and the ability to specify an +unlimited number of lines in a single call. He also continues to +track down odd incompatibilities and bugs.</li> + +<li><em>Mark Odegard</em> (meo@sugarland.unocal.com) provided the initial +implementation of <tt>fread</tt>, <tt>fwrite</tt>, <tt>feof</tt>, and +<tt>ferror</tt>.</li> + +<li><em>Tony Richardson</em> (tony@guts.biomed.uakron.edu) wrote Octave's +image processing functions as well as most of the original polynomial +functions.</li> + +<li><em>R. Bruce Tenison</em> (Bruce.Tenison@eng.auburn.edu) wrote the +<tt>hess</tt> and <tt>schur</tt> functions.</li> + +<li><em>Teresa Twaroch</em> (twaroch@ci.tuwien.ac.at) provided the functions +<tt>gls</tt> and <tt>ols</tt>.</li> + +<li><em>Fook Fah Yap</em> (ffy@eng.cam.ac.uk) provided the <tt>fft</tt> and +<tt>ifft</tt> functions and valuable bug reports for early versions. +</ul> + +<p> +Special thanks to the following people and organizations for +supporting the development of Octave: +</p> + +<ul> +<li><em>Digital Equipment Corporation</em>, for an equipment grant as part +of their External Research Program.</li> + +<li><em>Sun Microsystems</em>, Inc., for an Academic Equipment grant.</li> + +<li><em>International Business Machines, Inc.</em>, for providing equipment +as part of a grant to the University of Texas College of Engineering.</li> + +<li><em>Texaco Chemical Company</em>, for providing funding to continue the +development of this software.</li> + +<li><em>The University of Texas College of Engineering</em>, for providing a +Challenge for Excellence Research Supplement, and for providing an +Academic Development Funds grant.</li> + +<li><em>The State of Texas</em>, for providing funding through the Texas +Advanced Technology Program under Grant No. 003658-078.</li> + +<li><em>Noel Bell</em>, Senior Engineer, Texaco Chemical Company, Austin +Texas.</li> + +<li><em>James B. Rawlings</em>, Professor, University of Wisconsin-Madison, +Department of Chemical Engineering.</li> + +<li><em>Richard Stallman</em>, for writing GNU.</li> +</ul> + +<p> +This project would not have been possible without the GNU software used +in and used to produce Octave. +</p> +</body> +</html>
new file mode 100644 --- /dev/null +++ b/WWW/readme.html @@ -0,0 +1,120 @@ +<!doctype html public "-//IETF//DTD HTML Strict//EN"> +<html> +<head> +<title> Octave -- a high-level language for numerical computations </title> +</head> + +<h3>Copyright (C) 1996 John W. Eaton</h3> + +<h4>Overview</h4> +<p> +Octave is a high-level language, primarily intended for numerical +computations. It provides a convenient command line interface for +solving linear and nonlinear problems numerically. +</p> + +<p> +Octave is free software; you can redistribute it and/or modify it +under the terms of the GNU General Public License as published by the +Free Software Foundation; either version 2, or (at your option) any +later version. +</p> + +<p> +Octave is distributed in the hope that it will be useful, but WITHOUT +ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE. See the file COPYING for more +details. +</p> + +<h4>Availability</h4> +<p> +The latest released version of Octave is always available via +anonymous ftp from <a href="ftp://ftp.che.wisc.edu/pub/octave"> +ftp.che.wisc.edu</a> in the directory /pub/octave. +Complete source and binaries for several popular systems are +available. +</p> + +<h4>Installation and Bugs</h4> +<p> +Octave requires approximately 25MB of disk storage to unpack and +install (significantly less if you don't compile with debugging +symbols). In order to build Octave, you will need a current version +of g++, libg++, and GNU make. Octave is known to compile on the +following systems: +</p> + +<ul> +<li>SPARCstation 2 SunOS 4.1.2</li> +<li>IBM RS/6000 AIX 3.2.x</li> +<li>DECstation 5000/240 Ultrix 4.2a</li> +<li>i486 Linux</li> +<li>i486 NetBSD (without IEEE floating point support)</li> +<li>HP 9000/7xx HP-UX 9.x</li> +<li>SGI Irix 4.04</li> +<li>NeXT NeXTStep ?</li> +</ul> + +<p> +See the notes in the files INSTALL and INSTALL.OCTAVE for more +specific installation instructions, including directions for +installing Octave from a binary distribution. +</p> + +<p> +The file BUGS contains a recommended procedure for reporting bugs, as +well as a list of known problems. +</p> + +<h4>Binary Distributions</h4> +<p> +Binary copies of Octave are now distributed for several popular Unix +systems. To save disk space, the complete source code for Octave is +no longer included with the binary distribution, but should be +available in the same place as the binaries. If not, please contact +bug-octave@bevo.che.wisc.edu. +</p> + +<p> +The file INSTALL.OCTAVE contains specific installation instructions, +for installing Octave from a binary distribution. +</p> + +<h4>Implemenation</h4> +<p> +Octave is being developed with the Free Software Foundation's make, +bison (a replacement for YACC), flex (a replacement for lex), gcc/g++, +and libg++ on a SPARCstation II and a DECstation 5000/240. It should +be possible to install it on any machine that runs GCC/G++. It may +also be possible to install it using other implementations of these +tools, but it will most certainly require much more work. Do yourself +a favor and get the GNU development tools, either via anonymous ftp +from prep.ai.mit.edu or by writing the Free Software Foundation, 675 +Mass Ave, Cambridge, MA 02139, USA. +</p> + +<p> +The underlying numerical solvers are currently standard Fortran ones +like Lapack, Linpack, Odepack, the Blas, etc., packaged in a library +of C++ classes (see the files in the libcruft and liboctave +subdirectories). If possible, the Fortran subroutines are compiled +with the system's Fortran compiler, and called directly from the C++ +functions. If that's not possible, they are translated with f2c and +compiled with a C compiler. Better performance is usually achieved if +the intermediate translation to C is avoided. +</p> + +<p> +The library of C++ classes may also be useful by itself. +</p> + +<h4>Author</h4> +<p> +<a href="http://www.che.wisc.edu/~jwe">John W. Eaton</a><br> +<a href="mailto:jwe@bevo.che.wisc.edu"><i>jwe@bevo.che.wisc.edu</i></a><br> +University of Wisconsin<br> +Department of Chemical Engineering<br> +Madison WI 53719 +</body> +</html>