GNU Octave: Design and Release

GNU Octave began in chemical-engineering education. In the late 1980s, James Rawlings and John Ekerdt at the University of Texas at Austin were planning a chemical reactor design textbook and wanted accompanying software to help students solve practical computational problems. John Eaton later recalled that the initial idea was a library of Fortran subroutines, which gradually evolved toward a more flexible interactive environment.

The 1995 manual explained this choice: instructors saw students spending substantial effort figuring out why their Fortran programs crashed rather than understanding the chemical-engineering problems. Octave therefore placed matrices, equation solving and plotting in higher-level commands, allowing users to concentrate on models and results. It was also used in other chemical-engineering courses at the university and in differential-equations and linear-algebra teaching in the mathematics department.

References: [1] [2]

In his 2001 technical report, Eaton dated the concept to around 1988 and recorded beginning to write the interpreter on February 20, 1992, while still completing his doctoral dissertation at the University of Texas. He did most of the programming in the first year. By that summer, the program could handle some simple differential equations, after which research-group members tried it and found bugs.

On January 4, 1993, he made anonymous FTP downloads available and posted announcements to Usenet discussion groups. Version 1.0 followed on February 17, 1994. Conception, internal trials and public release were separate stages. The later customary name GNU Octave also involved an agreement with Richard Stallman in May 1997 to join the GNU Project; these actions should not all be assigned to 1988.

References: [1]

Early Octave did not reinvent every numerical algorithm. Preserved technical FAQs explained that Fortran numerical programs such as LAPACK, LINPACK, ODEPACK and BLAS were organized behind a C++ class library. They could be compiled and called directly when a Fortran compiler was available, or converted using f2c. Users encountered concise expressions, while specialized numerical solvers still did the underlying work.

The interactive experience likewise relied on cooperation among several components. GNU Readline handled input editing and command history, and gnuplot provided plotting. Early manuals also recorded contributions including John Campbell's work on input and output and Kurt Hornik's statistical functions. The interpreter's principal author, developers of numerical libraries and later collaborators contributing features should therefore be distinguished in historical accounts.

References: [2] [3]

The 1995 manual discussed matrix creation, matrix operations and linear equation solving together. Following its syntax, a small example can be constructed by entering A = [2, 1; 1, 3] and b = [5; 7], then computing x = A \ b. Semicolons inside brackets separate rows, b is a column vector, and left division requests the solution of A times x equals b.

The solution is the column vector [1.6; 1.8]: substituting it into the two rows yields 5 and 7 respectively. This maps two simultaneous equations on paper directly into a matrix problem without requiring students first to write elimination loops. The manual specifically noted that left division avoided computing the matrix inverse directly. This also reminds readers that numerical algorithms lie behind a short language expression; it is not merely mechanical substitution of symbols.

References: [2]

In the same early manual, users first defined rates of state change with function, supplied an initial state and a list of output times, called lsode to obtain numerical integration results, and finally drew curves with plot. Function definitions left the particular model to the user, the solver handled numerical advancement, and graphics helped examine behavior over time.

This workflow allowed parameters to be changed repeatedly, solutions rerun and results compared. It did not automatically prove that a model matched a real reactor or remove the need to judge initial conditions, errors and physical assumptions. The interactive language shortened the path from expressing a problem to numerical experimentation; teachers, students or researchers remained responsible for chemical-engineering knowledge and interpreting computations.

References: [2]

The early FAQ listed specific ways to obtain the software: copy it from a friend who already had it, download it by anonymous FTP, or buy tapes and CDs from the Free Software Foundation. It explicitly stated that the foundation distributed Octave but was not its original developer. Source packages included README, INSTALL, NEWS and ChangeLog, keeping installation guidance, user-visible changes and detailed development records together.

These materials described an environment then dominated by Unix-like systems; later desktop interfaces should not be projected backward onto early operating practices. The manuals and FAQs also directed users to mailing lists for help, bug reports and patches. Release under the GNU General Public License made copying and modification permitted forms of collaboration, although versions, dependencies and specific operating conditions still had to be checked.

References: [3]

In a review later published in the Journal of Applied Econometrics, Dirk Eddelbüttel used version 2.0.14 to demonstrate data processing and simulation: taking logarithms of a price series and then successive differences produced a return series, after which statistics, tests and graphics could be calculated in the same environment. He also demonstrated extending numerical capabilities through C++, showing that the tool had moved beyond reactor-design courses.

The independent review also noted that specialized econometrics routines and documentation for internal extensions were still insufficient, and that porting MATLAB programs could encounter implementation differences. Early Octave's significance lay in joining mature numerical libraries, a matrix language and shareable source code into a usable computing environment, rather than replacing all commercial software in one release. The extensions and limitations described in the 1999 review belonged to a later stage and should not all be counted as features already present in 1993.

References: [4]