3294
|
1 @c Copyright (C) 1996, 1997 John W. Eaton |
|
2 @c This is part of the Octave manual. |
|
3 @c For copying conditions, see the file gpl.texi. |
|
4 |
4167
|
5 @node Preface |
3294
|
6 @unnumbered Preface |
|
7 @cindex contributors |
|
8 @cindex history |
|
9 |
|
10 Octave was originally intended to be companion software for an |
|
11 undergraduate-level textbook on chemical reactor design being written by |
|
12 James B. Rawlings of the University of Wisconsin-Madison and John |
|
13 G. Ekerdt of the University of Texas. |
|
14 |
|
15 Clearly, Octave is now much more than just another `courseware' package |
|
16 with limited utility beyond the classroom. Although our initial goals |
|
17 were somewhat vague, we knew that we wanted to create something that |
|
18 would enable students to solve realistic problems, and that they could |
|
19 use for many things other than chemical reactor design problems. |
|
20 |
|
21 There are those who would say that we should be teaching the students |
|
22 Fortran instead, because that is the computer language of engineering, |
|
23 but every time we have tried that, the students have spent far too much |
|
24 time trying to figure out why their Fortran code crashes and not enough |
|
25 time learning about chemical engineering. With Octave, most students |
|
26 pick up the basics quickly, and are using it confidently in just a few |
|
27 hours. |
|
28 |
|
29 Although it was originally intended to be used to teach reactor design, |
|
30 it has been used in several other undergraduate and graduate |
|
31 courses in the Chemical Engineering Department at the University of |
|
32 Texas, and the math department at the University of Texas has been using |
|
33 it for teaching differential equations and linear algebra as well. If |
|
34 you find it useful, please let us know. We are always interested to |
|
35 find out how Octave is being used in other places. |
|
36 |
|
37 Virtually everyone thinks that the name Octave has something to do with |
|
38 music, but it is actually the name of a former professor of mine who |
|
39 wrote a famous textbook on chemical reaction engineering, and who was |
|
40 also well known for his ability to do quick `back of the envelope' |
|
41 calculations. We hope that this software will make it possible for many |
|
42 people to do more ambitious computations just as easily. |
|
43 |
|
44 Everyone is encouraged to share this software with others under the |
|
45 terms of the GNU General Public License (@pxref{Copying}) as described |
|
46 at the beginning of this manual. You are also encouraged to help make |
|
47 Octave more useful by writing and contributing additional functions for |
|
48 it, and by reporting any problems you may have. |
|
49 |
|
50 @menu |
|
51 * Acknowledgements:: |
|
52 * How You Can Contribute to Octave:: |
|
53 * Distribution:: |
|
54 @end menu |
|
55 |
4167
|
56 @node Acknowledgements |
3294
|
57 @unnumberedsec Acknowledgements |
|
58 @cindex acknowledgements |
|
59 |
6531
|
60 Many people have already contributed to Octave's development. The |
|
61 following people have helped write parts of Octave or helped out in |
|
62 various other ways (listed alphbetically). |
3294
|
63 |
6535
|
64 @include contributors.texi |
3294
|
65 |
|
66 Special thanks to the following people and organizations for |
|
67 supporting the development of Octave: |
|
68 |
|
69 @itemize @bullet |
|
70 @item |
3839
|
71 The National Science Foundation, through grant numbers CTS-0105360, |
|
72 CTS-9708497, CTS-9311420, and CTS-8957123. |
|
73 |
|
74 @item |
|
75 The industrial members of the Texas-Wisconsin Modeling and Control |
|
76 Consortium (@uref{http://www.che.utexas.edu/twmcc, TWMCC}). |
|
77 |
|
78 @item |
|
79 The Paul A. Elfers Endowed Chair in Chemical Engineering at the |
|
80 University of Wisconsin-Madison. |
|
81 |
|
82 @item |
3294
|
83 Digital Equipment Corporation, for an equipment grant as part of their |
|
84 External Research Program. |
|
85 |
|
86 @item |
|
87 Sun Microsystems, Inc., for an Academic Equipment grant. |
|
88 |
|
89 @item |
|
90 International Business Machines, Inc., for providing equipment as part |
|
91 of a grant to the University of Texas College of Engineering. |
|
92 |
|
93 @item |
|
94 Texaco Chemical Company, for providing funding to continue the |
|
95 development of this software. |
|
96 |
|
97 @item |
|
98 The University of Texas College of Engineering, for providing a |
|
99 Challenge for Excellence Research Supplement, and for providing an |
|
100 Academic Development Funds grant. |
|
101 |
|
102 @item |
|
103 The State of Texas, for providing funding through the Texas |
|
104 Advanced Technology Program under Grant No. 003658-078. |
|
105 |
|
106 @item |
|
107 Noel Bell, Senior Engineer, Texaco Chemical Company, Austin Texas. |
|
108 |
|
109 @item |
5753
|
110 John A. Turner, Group Leader, Continuum Dynamics (CCS-2), Los Alamos |
|
111 National Laboratory, for registering the @url{octave.org} domain name. |
|
112 |
|
113 @item |
3294
|
114 James B. Rawlings, Professor, University of Wisconsin-Madison, |
5753
|
115 Department of Chemical and Biological Engineering. |
3294
|
116 |
|
117 @item |
|
118 Richard Stallman, for writing GNU. |
|
119 @end itemize |
|
120 |
|
121 This project would not have been possible without the GNU software used |
|
122 in and used to produce Octave. |
|
123 |
4167
|
124 @node How You Can Contribute to Octave |
3294
|
125 @unnumberedsec How You Can Contribute to Octave |
|
126 @cindex contributing to Octave |
|
127 @cindex funding Octave development |
|
128 |
|
129 There are a number of ways that you can contribute to help make Octave a |
|
130 better system. Perhaps the most important way to contribute is to write |
|
131 high-quality code for solving new problems, and to make your code freely |
|
132 available for others to use. |
|
133 |
|
134 If you find Octave useful, consider providing additional funding to |
|
135 continue its development. Even a modest amount of additional funding |
|
136 could make a significant difference in the amount of time that is |
|
137 available for development and support. |
|
138 |
|
139 If you cannot provide funding or contribute code, you can still help |
|
140 make Octave better and more reliable by reporting any bugs you find and |
|
141 by offering suggestions for ways to improve Octave. @xref{Trouble}, for |
|
142 tips on how to write useful bug reports. |
|
143 |
4167
|
144 @node Distribution |
3294
|
145 @unnumberedsec Distribution |
|
146 @cindex distribution of Octave |
|
147 |
|
148 Octave is @dfn{free} software. This means that everyone is free to |
|
149 use it and free to redistribute it on certain conditions. Octave is not |
|
150 in the public domain. It is copyrighted and there are restrictions on |
|
151 its distribution, but the restrictions are designed to ensure that |
|
152 others will have the same freedom to use and redistribute Octave that |
|
153 you have. The precise conditions can be found in the GNU General Public |
|
154 License that comes with Octave and that also appears in @ref{Copying}. |
|
155 |
|
156 Octave is available on CD-ROM with various collections of other free |
|
157 software, and from the Free Software Foundation. Ordering a copy of |
|
158 Octave from the Free Software Foundation helps to fund the development |
|
159 of more free software. For more information, write to |
|
160 |
|
161 @quotation |
|
162 Free Software Foundation@* |
5307
|
163 51 Franklin Street, Fifth Floor@* |
|
164 Boston, MA 02110-1301--1307@* |
3294
|
165 USA |
|
166 @end quotation |
|
167 |
|
168 Octave is also available on the Internet from |
6620
|
169 @url{ftp://ftp.octave.org/pub/octave}, and additional information is |
|
170 available from @url{http://www.octave.org}. |