@c Copyright (C) 1996, 1997 John W. Eaton
@c This is part of the Octave manual.
@c For copying conditions, see the file gpl.texi.

@node Preface
@unnumbered Preface
@cindex contributors
@cindex history

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.

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.

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.

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.

Virtually everyone thinks that the name Octave has something to do with
music, but it is actually the name of a former professor 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.

Everyone is encouraged to share this software with others under the
terms of the GNU General Public License (@pxref{Copying}) 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.

@menu
* Acknowledgements::            
* How You Can Contribute to Octave::  
* Distribution::                
@end menu

@node Acknowledgements
@unnumberedsec Acknowledgements
@cindex acknowledgements

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 (listed alphbetically).

@noindent
Andy Adler, Joel Andersson, Muthiah Annamalai,
Shai Ayal, Roger Banks, Ben Barrowes, Alexander Barth, 
David Bateman, Heinz Bauschke, Karl Berry, David Billinghurst, 
Don Bindner, Jakub Bogusz, Marcus Brinkmann, Remy Bruno, 
Marco Caliari, Daniel Calvelo, John C. Campbell, Jean-Francois Cardoso, 
Joao Cardoso, Larrie Carr, David Castelow, Vincent Cautaerts, 
Clinton Chee, Albert Chin-A-Young, J. D. Cole, Martin Costabel, 
Michael Creel, Jeff Cunningham, Martin Dalecki, Jorge Barros de Abreu,
Philippe Defert, Bill Denney, David M. Doolin, Pascal A. Dupuis,
John W. Eaton, Dirk Eddelbuettel, Paul Eggert, Stephen Eglen, Peter Ekberg, 
Rolf Fabian, Stephen Fegan, Ramon Garcia Fernandez, Torsten Finke, 
Jose Daniel Munoz Frias, Castor Fu, Eduardo Gallestey, Walter Gautschi, 
Klaus Gebhardt, Driss Ghaddab, Nicolo Giorgetti, From Michael Goffioul, 
Michael Goffioul, Glenn Golden, Tomislav Goles, Keith Goodman, 
Etienne Grossmann, Kai Habel, William Poetra Yoga Hadisoeseno, Benjamin Hall, 
Kim Hansen, Soren Hauberg, Daniel Heiserer, Yozo Hida, 
Roman Hodek, A. Scottedward Hodel, Richard Allan Holcombe, Tom Holroyd, 
David Hoover, Kurt Hornik, Christopher Hulbert, Cyril Humbert, 
Teemu Ikonen, Alan W. Irwin, Geoff Jacobsen, Mats Jansson, 
Cai Jianming, Steven G. Johnson, Heikki Junes, Atsushi Kajita, 
Mohamed Kamoun, Lute Kamstra, Mumit Khan, Paul Kienzle, 
Aaron A. King, Arno J. Klaassen, Geoffrey Knauth, Heine Kolltveit, 
Ken Kouno, Oyvind Kristiansen, Piotr Krzyzanowski, Volker Kuhlmann, 
Miroslaw Kwasniak, Rafael Laboissiere, Kai Labusch, Claude Lacoursiere, 
Walter Landry, Duncan Temple Lang, Bill Lash, Dirk Laurie, 
Maurice LeBrun, Friedrich Leisch, Benjamin Lindner, Ross Lippert, 
David Livings, Erik de Castro Lopo, Massimo Lorenzin, Hoxide Ma, 
James Macnicol, Jens-Uwe Mager, Ricardo Marranita, Orestes Mas, 
Makoto Matsumoto, Laurent Mazet, G. D. McBain, Stefan Monnier, 
Antoine Moreau, Kai P. Mueller, Victor Munoz, Carmen Navarrete, 
Todd Neal, Al Niessner, Rick Niles, Takuji Nishimura, 
Eric Norum, Michael O'Brien, Thorsten Ohl, Arno Onken, 
Luis F. Ortiz, Luis Ortiz, Scott Pakin, Gabriele Pannocchia, 
Sylvain Pelissier, Per Persson, Jim Peterson, Danilo Piazzalunga, 
Nicholas Piper, Hans Ekkehard Plesser, Tom Poage, Orion Poplawski, 
Ondrej Popp, Jef Poskanzer, Francesco Potorti, James B. Rawlings, 
Eric S. Raymond, Balint Reczey, Michael Reifenberger, Petter Risholm, 
Matthew W. Roberts, Andrew Ross, Mark van Rossum, Kevin Ruland, 
Olli Saarela, Toni Saarela, Juhani Saastamoinen, Ben Sapp, 
Alois Schloegl, Michel D. Schmid, Nicol N. Schraudolph, Ludwig Schwardt, 
Daniel J. Sebald, Dmitri A. Sergatskov, Baylis Shanks, Joseph P. Skudlarek, 
John Smith, Julius Smith, Shan G. Smith, Joerg Specht, 
Quentin H. Spencer, Christoph Spiel, Richard Stallman, Russell Standish, 
Doug Stewart, Thomas Stuart, Ariel Tankus, Georg Thimm, 
Thomas Treichl, Utkarsh Upadhyay, Stefan van der Walt, Peter Van Wieren, 
James R. Van Zandt, Gregory Vanuxem, Ivana Varekova, Thomas Walter, 
Olaf Weber, Thomas Weber, Bob Weigel, Andreas Weingessel, 
Fook Fah Yap, Michael Zeising, Federico Zenith, and Alex Zvoleff.

Special thanks to the following people and organizations for
supporting the development of Octave:

@itemize @bullet
@item
The National Science Foundation, through grant numbers CTS-0105360,
CTS-9708497, CTS-9311420, and CTS-8957123.

@item
The industrial members of the Texas-Wisconsin Modeling and Control
Consortium (@uref{http://www.che.utexas.edu/twmcc, TWMCC}).

@item
The Paul A. Elfers Endowed Chair in Chemical Engineering at the
University of Wisconsin-Madison.

@item
Digital Equipment Corporation, for an equipment grant as part of their
External Research Program.

@item
Sun Microsystems, Inc., for an Academic Equipment grant.

@item
International Business Machines, Inc., for providing equipment as part
of a grant to the University of Texas College of Engineering.

@item
Texaco Chemical Company, for providing funding to continue the
development of this software.

@item
The University of Texas College of Engineering, for providing a
Challenge for Excellence Research Supplement, and for providing an
Academic Development Funds grant.

@item
The State of Texas, for providing funding through the Texas
Advanced Technology Program under Grant No. 003658-078.

@item
Noel Bell, Senior Engineer, Texaco Chemical Company, Austin Texas.

@item
John A. Turner, Group Leader, Continuum Dynamics (CCS-2), Los Alamos
National Laboratory, for registering the @url{octave.org} domain name.

@item
James B. Rawlings, Professor, University of Wisconsin-Madison,
Department of Chemical and Biological Engineering.

@item
Richard Stallman, for writing GNU.
@end itemize

This project would not have been possible without the GNU software used
in and used to produce Octave.

@node How You Can Contribute to Octave
@unnumberedsec How You Can Contribute to Octave
@cindex contributing to Octave
@cindex funding Octave development

There are a number of ways that you can contribute to help make Octave a
better system.  Perhaps the most important way to contribute is to write
high-quality code for solving new problems, and to make your code freely
available for others to use.

If you find Octave useful, consider providing additional funding to
continue its development.  Even a modest amount of additional funding
could make a significant difference in the amount of time that is
available for development and support.

If you cannot provide funding or contribute code, you can still help
make Octave better and more reliable by reporting any bugs you find and
by offering suggestions for ways to improve Octave.  @xref{Trouble}, for
tips on how to write useful bug reports.

@node Distribution
@unnumberedsec Distribution
@cindex distribution of Octave

Octave is @dfn{free} software.  This means that everyone is free to
use it and free to redistribute it on certain conditions.  Octave is not
in the public domain.  It is copyrighted and there are restrictions on
its distribution, but the restrictions are designed to ensure that
others will have the same freedom to use and redistribute Octave that
you have.  The precise conditions can be found in the GNU General Public
License that comes with Octave and that also appears in @ref{Copying}.

Octave is available on CD-ROM with various collections of other free
software, and from the Free Software Foundation.  Ordering a copy of
Octave from the Free Software Foundation helps to fund the development
of more free software.  For more information, write to

@quotation
Free Software Foundation@*
51 Franklin Street, Fifth Floor@*
Boston, MA 02110-1301--1307@*
USA
@end quotation
 
Octave is also available on the Internet from
@url{ftp://ftp.che.wisc.edu/pub/octave}, and additional information is
available from @url{http://www.che.wisc.edu/octave}.