Mercurial > hg > octave-nkf

comparison PROJECTS @ 3136:af7ec9d3a5e6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[project @ 1998-02-01 20:11:06 by jwe]
author jwe
date Sun, 01 Feb 1998 20:11:08 +0000
parents 02766207b74c
children 292ff0bf484b
comparison
equal deleted inserted replaced
3135:267b3a5c6b28 3136:af7ec9d3a5e6
116 * Make plotting with plplot work. 116 * Make plotting with plplot work.
117 117
118 * Fix interface with gnuplot to wait for gnuplot to output any text 118 * Fix interface with gnuplot to wait for gnuplot to output any text
119 before octave returns a prompt. Possible by implementing two 119 before octave returns a prompt. Possible by implementing two
120 way communication between gnuplot and Octave. 120 way communication between gnuplot and Octave.
121
122 * Handle gnuplot ranges correctly for parametric modes (accept 3
123 ranges for 2d plots and 5 ranges for 3d plots).
121 124
122 * Make gsave (and possibly gload) work. Implement gsave by having it 125 * Make gsave (and possibly gload) work. Implement gsave by having it
123 also alter the plot command to not use temporary files (perhaps 126 also alter the plot command to not use temporary files (perhaps
124 with some user-specified template for naming them) and then 127 with some user-specified template for naming them) and then
125 sending a `save' command to gnuplot. 128 sending a `save' command to gnuplot.
707 2d) and in what order they are processed (stream or random 710 2d) and in what order they are processed (stream or random
708 access). 711 access).
709 712
710 Perhaps this can be done entirely with a library of M-files. 713 Perhaps this can be done entirely with a library of M-files.
711 714
715 * An interface to gdb.
716
717 Michael Smolsky <fnsiguc@weizmann.weizmann.ac.il> wrote:
718
719 I was thinking about a tool, which could be very useful for me
720 in my numerical simulation work. It is an interconnection
721 between gdb and octave. We are often managing very large arrays
722 of data in our fortran or c codes, which might be studied with
723 the help of octave at the algorithm development stages. Assume
724 you're coding, say, wave equation. And want to debug the
725 code. It would be great to pick some array from the memory of
726 the code you're develloping, fft it and see the image as a
727 log-log plot of the spectral density. I'm facing similar
728 problems now. To avoid high c-development cost, I develop in
729 matlab/octave, and then rewrite into c. It might be so much
730 easier, if I could off-load a c array right from the debugger
731 into octave, study it, and, perhaps, change some [many] values
732 with a convenient matlab/octave syntax, similar to
733 a(:,50:250)=zeros(100,200), and then store it back into the
734 memory of my c code.
735
712 * Add a function like strptime() which is the opposite of 736 * Add a function like strptime() which is the opposite of
713 strftime(). A C version is apparently in recent releases of the 737 strftime(). A C version is apparently in recent releases of the
714 Linux C library. 738 Linux C library.
715 739
716 * Add a definition to lgrind so that it supports Octave. 740 * Add a definition to lgrind so that it supports Octave.