Thorsten Meyer | 2 Dec 21:34 2008
Picon
Picon

failed nchoosek test in mercurial tip

Hi,

while doing
	make check
with the latest mercurial tip on an intel pc running debian, I got this test failure:

>>>>> processing /home/thorsten/hg/octave/scripts/specfun/nchoosek.m
  ***** assert (nchoosek(100,45), bincoeff(100,45))
!!!!! test failed
assert (nchoosek (100, 45),bincoeff (100, 45)) expected
 6.1448e+28
but got
 6.1448e+28
values do not match

Trying directly in octave, I get:
octave:2> (nchoosek (100, 45)-bincoeff (100, 45))/nchoosek(100,45)
ans =  2.8343e-14

The difference certainly is not much, but still significantly larger than eps. So, the question is:
is it relevant?

regards

Thorsten
John W. Eaton | 4 Dec 16:38 2008

Line and Marker Properties Corrupt

On 26-Nov-2008, Peter Berntsen wrote:

| 
| I don't know if it is gnuplot or octave to blame but
| 
| t = 0:0.1:6.3;
| line(t,sin(t),'linestyle','-')
| Gives the same result as linestyle changed to:
|      Dashed lines.
| "--"
|      Points.
| ":"
|      A dash-dot line.
| "-."
| That is the line style is solid no matter what I specify.
| Linewidth works.
| 
|  plot(t,sin(t),".","markersize",3)
|  plot(t,sin(t),"+","markersize",3)
|  plot(t,sin(t),"*","markersize",3)
|  plot(t,sin(t),"o","markersize",3)
|  plot(t,sin(t),"x","markersize",3)
|  
| Gives the same results as octave: 
| plot(t,sin(t),".")
| 
| I run gnuplot 
| 	G N U P L O T
| 	Version 4.2 patchlevel 3 
| 	last modified Mar 2008
(Continue reading)

georgios | 4 Dec 08:58 2008

Octave UI 3.0.3 and 3.1.50

Hej

I have alreday sent an email to octave help but I never got an answer. 
Well, I am a new Octave user and I found out that Octave UI is very 
convenient and user friendly. When I tried to change the Octave version 
thus, 3.0.1 to 3.0.3 or 3.1.50 the Octave UI is not installed thus, 
octavede.exe is not found in the bin directory. Please kindly note that 
I am using the windows version. When I install the above mentioned 
versions the Graphical User Interface is not found in Miscellaneous so 
I was not able to choose it. But is possible in Octave 3.0.1.

How can I solve the problem? Or is this a bug?

Additionally, when I am using Go in the Tools in SciTe in order to run 
a script the figures are flying by. What is the problem? How can I 
solve it?

Thank you in advance

Regards

Georgios
Dave Goel | 4 Dec 22:54 2008
X-Face
Picon

Kolmogorov smirnoff test for two samples: bug

Consider a=[1 2 3 4], and b=[5 6 7 8].

The null is a = b.  The alt. is !=.

We get 

octave:3> kolmogorov_smirnov_test_2 (a,b,"!=")
  pval: 0.0366311

Now consider an even more ridiculous null of a>b.  In this case, the
alt. is "<", So, p should get even lower. But, 
octave:5> kolmogorov_smirnov_test_2 (a,b,"<")
  pval: 1

Now, consider a very plausible null of a<b. The alt. is ">".  P should
now be about 1, but we get:

octave:6> kolmogorov_smirnov_test_2 (a,b,">")
  pval: 0.0183156

It seems that the meaning of < and > are flipped in the test.  Note
that the third argument refers to ALT, and not to NULL, as for
example, seen for the case of !=.

I have tested this with the latest octave as well. 
Jan Albersmeyer | 6 Dec 16:33 2008
Picon

Parse error when defining a cell array

Bug report for Octave 3.0.1 configured for i686-pc-linux-gnu

Description:
-----------

It seems that the call to the "eye" function is not handled correctly
while defining a cell array.

Repeat-By:
---------

This is how I would expect Octave to work, and in this case it does fine.

octave:1> e = { 0, eye(5) }
e =

{
  [1,1] = 0
  [1,2] =

     1   0   0   0   0
     0   1   0   0   0
     0   0   1   0   0
     0   0   0   1   0
     0   0   0   0   1

}

Here, a whitespace is inserted between eye and its argument, leading to
irritating results:
(Continue reading)

Bill Denney | 6 Dec 17:50 2008

Re: Parse error when defining a cell array

Jan Albersmeyer wrote:
> Description:
> -----------
>  
> It seems that the call to the "eye" function is not handled correctly
> while defining a cell array.
>
>
> Repeat-By:
> ---------
>
> This is how I would expect Octave to work, and in this case it does fine.
>
> octave:1> e = { 0, eye(5) }
>
> Here, a whitespace is inserted between eye and its argument, leading to
> irritating results:
>
> octave:2> e = { 0, eye (5) }
>   

Hi Jan,

This is actually expected behavior (sorry for the irritation).  The
reason is that since Octave allows spaces or commas to separate
matrix/cell arguments, it is impossible to tell when you mean

0, eye() (5)

as opposed to
(Continue reading)

Afief Halumi | 5 Dec 14:05 2008
Picon

polyfit enters infinite loop

Bug report for Octave 3.0.1 configured for i486-pc-linux-gnu

Description:
-----------

  trying to polyfit log(x) when x starts at 0( log(0)=-inf according to
octave ) keeps running indefinitely(or at least for over 15 minutes)

Repeat-By:
---------

  * x=0:0.1:10; y=log(x); polyfit(x,y,3);

Fix:
---

  * I think polyfit chokes on the -inf value returned by log(0), a
possible solution might be to replace -inf with a value that's 10^5
times less than the lowest value polyfit has to deal with.



Configuration (please do not edit this section):
-----------------------------------------------

uname output:     Linux afief-laptop 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux
configure opts:   '--host=i486-linux-gnu' '--build=i486-linux-gnu' '--prefix=/usr' '--datadir=/usr/share' '--libdir=/usr/lib' '--libexecdir=/usr/lib' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-blas=-lblas-3gf' '--with-lapack=-llapackgf-3' '--with-hdf5' '--with-fftw' '--enable-shared' '--enable-rpath' '--disable-static' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CC=gcc' 'CFLAGS=-g -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS=' 'CXX=g++' 'CXXFLAGS=-g -O2' 'F77=gfortran' 'FFLAGS=-g -O2'
Fortran compiler: gfortran
FFLAGS:           -O2 -g
F2C:              <at> F2C <at>
F2CFLAGS:         <at> F2CFLAGS <at>
FLIBS:            -L/usr/lib/gcc/i486-linux-gnu/4.3.1 -L/usr/lib/gcc/i486-linux-gnu/4.3.1/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.3.1/../../.. -lhdf5 -lz -lgfortranbegin -lgfortran -lm
CPPFLAGS:        
INCFLAGS:         -I. -I. -I./liboctave -I./src -I./libcruft/misc
C compiler:       gcc, version 4.3.1 (Ubuntu 4.3.1-8ubuntu3)
CFLAGS:           -O2 -g
CPICFLAG:         -fPIC
C++ compiler:     g++, version 4.3.1
CXXFLAGS:         -O2 -g
CXXPICFLAG:       -fPIC
LD_CXX:           g++
LDFLAGS:         
LIBFLAGS:         -L.
RLD_FLAG:         -Wl,-rpath -Wl,/usr/lib/octave-3.0.1
BLAS_LIBS:        -llapackgf-3 -lblas-3gf
FFTW_LIBS:        -lfftw3
LIBS:             -lreadline  -lncurses -ldl -lhdf5 -lz -lm
LEXLIB:          
LIBGLOB:         
SED:              /bin/sed
DEFS:

  -DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION=""
  -DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DOCTAVE_SOURCE=1
  -D_GNU_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
  -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
  -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSEPCHAR=':'
  -DSEPCHAR_STR=":" -D__NO_MATH_INLINES=1 -DCXX_NEW_FRIEND_TEMPLATE_DECL=1
  -DCXX_ISO_COMPLIANT_LIBRARY=1 -DCXX_ABI=unknown -DHAVE_LIBM=1
  -DHAVE_QHULL=1 -DHAVE_PCRE=1 -DHAVE_REGEXEC=1 -DHAVE_REGEX=1
  -DHAVE_ZLIB_H=1 -DHAVE_ZLIB=1 -DHAVE_HDF5_H=1 -DHAVE_HDF5=1
  -DHAVE_H5GGET_NUM_OBJS=1 -DHAVE_FFTW3=1 -DHAVE_GLPK_H=1 -DHAVE_GLPK=1
  -DHAVE_CURL_CURL_H=1 -DHAVE_CURL=1 -DHAVE_IEEE754_DATA_FORMAT=1
  -DF77_FUNC(name,NAME)=name ## _ -DF77_FUNC_(name,NAME)=name ## _
  -DHAVE_BLAS=1 -DHAVE_SUITESPARSE_UMFPACK_H=1 -DHAVE_UMFPACK=1
  -DUMFPACK_SEPARATE_SPLIT=1 -DHAVE_SUITESPARSE_COLAMD_H=1
  -DHAVE_COLAMD=1 -DHAVE_SUITESPARSE_CCOLAMD_H=1 -DHAVE_CCOLAMD=1
  -DHAVE_SUITESPARSE_CHOLMOD_H=1 -DHAVE_CHOLMOD=1 -DHAVE_SUITESPARSE_CS_H=1
  -DHAVE_CXSPARSE=1 -DHAVE_GETHOSTNAME=1 -DHAVE_GETPWNAM=1 -DHAVE_DEV_T=1
  -DHAVE_INO_T=1 -DHAVE_NLINK_T=1 -DHAVE_NLINK_T=1 -DHAVE_LONG_LONG_INT=1
  -DHAVE_UNSIGNED_LONG_LONG_INT=1 -DHAVE_SIGSET_T=1 -DHAVE_SIG_ATOMIC_T=1
  -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8
  -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DNPOS=std::string::npos
  -DHAVE_PLACEMENT_DELETE=1 -DHAVE_DYNAMIC_AUTO_ARRAYS=1 -DSTDC_HEADERS=1
  -DHAVE_DIRENT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_SYS_WAIT_H=1
  -DHAVE_ASSERT_H=1 -DHAVE_CURSES_H=1 -DHAVE_DLFCN_H=1 -DHAVE_FCNTL_H=1
  -DHAVE_FLOAT_H=1 -DHAVE_GRP_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1
  -DHAVE_LOCALE_H=1 -DHAVE_MEMORY_H=1 -DHAVE_NCURSES_H=1 -DHAVE_POLL_H=1
  -DHAVE_PWD_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
  -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_POLL_H=1
  -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_STAT_H=1
  -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_SYS_TYPES_H=1
  -DHAVE_SYS_UTSNAME_H=1 -DHAVE_TERMCAP_H=1 -DHAVE_UNISTD_H=1
  -DHAVE_UTIME_H=1 -DHAVE_SSTREAM=1 -DHAVE_TERMIO_H=1 -DHAVE_SGTTY_H=1
  -DHAVE_GLOB_H=1 -DHAVE_FNMATCH_H=1 -DHAVE_FNMATCH=1 -DHAVE_GLOB=1
  -DHAVE_ATEXIT=1 -DHAVE_BASENAME=1 -DHAVE_BCOPY=1 -DHAVE_BZERO=1
  -DHAVE_CANONICALIZE_FILE_NAME=1 -DHAVE_CHMOD=1 -DHAVE_DUP2=1
  -DHAVE_ENDGRENT=1 -DHAVE_ENDPWENT=1 -DHAVE_EXECVP=1 -DHAVE_FCNTL=1
  -DHAVE_FORK=1 -DHAVE_GETCWD=1 -DHAVE_GETEGID=1 -DHAVE_GETEUID=1
  -DHAVE_GETGID=1 -DHAVE_GETGRENT=1 -DHAVE_GETGRGID=1 -DHAVE_GETGRNAM=1
  -DHAVE_GETPGRP=1 -DHAVE_GETPID=1 -DHAVE_GETPPID=1 -DHAVE_GETPWENT=1
  -DHAVE_GETPWUID=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_GETUID=1 -DHAVE_GETWD=1
  -DHAVE_KILL=1 -DHAVE_LGAMMA=1 -DHAVE_LINK=1 -DHAVE_LOCALTIME_R=1
  -DHAVE_LSTAT=1 -DHAVE_MEMMOVE=1 -DHAVE_MKDIR=1 -DHAVE_MKFIFO=1
  -DHAVE_MKSTEMP=1 -DHAVE_ON_EXIT=1 -DHAVE_PIPE=1 -DHAVE_POLL=1
  -DHAVE_PUTENV=1 -DHAVE_RAISE=1 -DHAVE_READLINK=1 -DHAVE_REALPATH=1
  -DHAVE_RENAME=1 -DHAVE_RINDEX=1 -DHAVE_RMDIR=1 -DHAVE_ROUND=1
  -DHAVE_SELECT=1 -DHAVE_SETGRENT=1 -DHAVE_SETLOCALE=1
  -DHAVE_SETPWENT=1 -DHAVE_SETVBUF=1 -DHAVE_SIGACTION=1
  -DHAVE_SIGLONGJMP=1 -DHAVE_SIGPENDING=1 -DHAVE_SIGPROCMASK=1
  -DHAVE_SIGSUSPEND=1 -DHAVE_SNPRINTF=1 -DHAVE_STAT=1 -DHAVE_STRCASECMP=1
  -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRPTIME=1
  -DHAVE_STRSIGNAL=1 -DHAVE_SYMLINK=1 -DHAVE_TEMPNAM=1 -DHAVE_TGAMMA=1
  -DHAVE_UMASK=1 -DHAVE_UNAME=1 -DHAVE_UNLINK=1 -DHAVE_USLEEP=1
  -DHAVE_UTIME=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1
  -DHAVE_WAITPID=1 -DHAVE_STRFTIME=1 -DHAVE_LIBDL=1 -DHAVE_DLOPEN=1
  -DHAVE_DLSYM=1 -DHAVE_DLERROR=1 -DHAVE_DLCLOSE=1 -DHAVE_DLOPEN_API=1
  -DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1 -DHAVE_FINITE=1
  -DHAVE_ISNAN=1 -DHAVE_ISINF=1 -DHAVE_COPYSIGN=1 -DHAVE_DECL_SIGNBIT=1
  -DHAVE_ACOSH=1 -DHAVE_ASINH=1 -DHAVE_ATANH=1 -DHAVE_ERF=1 -DHAVE_ERFC=1
  -DHAVE_EXP2=1 -DHAVE_LOG2=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1
  -DHAVE_STRUCT_STAT_ST_BLOCKS=1 -DHAVE_STRUCT_STAT_ST_RDEV=1
  -DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1 -DUSE_READLINE=1
  -DEXCEPTION_IN_MATH=1 -DRETSIGTYPE=void -DHAVE_DECL_SYS_SIGLIST=1
  -DHAVE_POSIX_SIGNALS=1 -DRETSIGTYPE_IS_VOID=1 -DHAVE_GETRUSAGE=1
  -DHAVE_TIMES=1 -DYYTEXT_POINTER=1 -DGNUPLOT_BINARY="gnuplot"

User-preferences (please do not edit this section):
--------------------------------------------------

  EDITOR = emacs
  EXEC_PATH = /usr/lib/octave/3.0.1/site/exec/i486-pc-linux-gnu:/usr/lib/octave/api-v32/site/exec/i486-pc-linux-gnu:/usr/lib/octave/site/exec/i486-pc-linux-gnu:/usr/lib/octave/3.0.1/exec/i486-pc-linux-gnu:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  IMAGE_PATH = .:/usr/share/octave/3.0.1/imagelib
  PAGER = pager
  PS1 = \s:\#>
  PS2 = >
  PS4 = +
  beep_on_error = 0
  completion_append_char = 
  crash_dumps_octave_core = 1
  echo_executing_commands = 0
  fixed_point_format = 0
  gnuplot_binary = gnuplot
  gnuplot_command_end =

  gnuplot_command_plot = pl
  gnuplot_command_replot = rep
  gnuplot_command_splot = sp
  gnuplot_command_title = t
  gnuplot_command_using = u
  gnuplot_command_with = w
  history_file = /home/afief/.octave_hist
  history_size = 1024
  ignore_function_time_stamp = system
  info_file = /usr/share/info/octave3.0.info
  info_program = info
  makeinfo_program = makeinfo
  max_recursion_depth = 256
  output_max_field_width = 5
  output_precision = 5
  page_output_immediately = 0
  page_screen_output = 1
  print_answer_id_name = 1
  print_empty_dimensions = 1
  save_precision = 16
  saving_history = 1
  sighup_dumps_octave_core = 1
  sigterm_dumps_octave_core = 1
  silent_functions = 0
  split_long_rows = 1
  string_fill_char = 
  struct_levels_to_print = 2
  suppress_verbose_help_message = 0
_______________________________________________
Bug-octave mailing list
Bug-octave <at> octave.org
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave
Thorsten Meyer | 6 Dec 22:23 2008
Picon
Picon

Re: polyfit enters infinite loop

Afief Halumi wrote:
> Bug report for Octave 3.0.1 configured for i486-pc-linux-gnu
> 
> Description:
> -----------
> 
>   trying to polyfit log(x) when x starts at 0( log(0)=-inf according to
> octave ) keeps running indefinitely(or at least for over 15 minutes)
> 
> Repeat-By:
> ---------
> 
>   * x=0:0.1:10; y=log(x); polyfit(x,y,3);
> 
I can confirm this bug with 3.0.1.

In octave freshly built from the mercurial sources the command returns:
octave:4> x=0:0.1:10; y=log(x); polyfit(x,y,3)
ans =

   NaN   NaN   NaN  -Inf
So apparently, it has already been fixed.

can somebody check in 3.0.3?

Thorsten
Sergei Steshenko | 6 Dec 22:46 2008
Picon

Re: polyfit enters infinite loop


--- On Sat, 12/6/08, Thorsten Meyer <thorsten.meyier <at> gmx.de> wrote:

> From: Thorsten Meyer <thorsten.meyier <at> gmx.de>
> Subject: Re: polyfit enters infinite loop
> To: bug <at> octave.org
> Date: Saturday, December 6, 2008, 1:23 PM
> Afief Halumi wrote:
> > Bug report for Octave 3.0.1 configured for
> i486-pc-linux-gnu
> > 
> > Description:
> > -----------
> > 
> >   trying to polyfit log(x) when x starts at 0(
> log(0)=-inf according to
> > octave ) keeps running indefinitely(or at least for
> over 15 minutes)
> > 
> > Repeat-By:
> > ---------
> > 
> >   * x=0:0.1:10; y=log(x); polyfit(x,y,3);
> > 
> I can confirm this bug with 3.0.1.
> 
> In octave freshly built from the mercurial sources the
> command returns:
> octave:4> x=0:0.1:10; y=log(x); polyfit(x,y,3)
> ans =
> 
>    NaN   NaN   NaN  -Inf
> So apparently, it has already been fixed.
> 
> can somebody check in 3.0.3?
> 
> Thorsten
> 

In my case octave-3.0.3 hangs.

Regards,
  Sergei.
Ben Abbott | 6 Dec 23:21 2008
Picon

Re: polyfit enters infinite loop


On Dec 6, 2008, at 4:46 PM, Sergei Steshenko wrote:
>
> --- On Sat, 12/6/08, Thorsten Meyer <thorsten.meyier <at> gmx.de> wrote:
>
>> From: Thorsten Meyer <thorsten.meyier <at> gmx.de>
>> Subject: Re: polyfit enters infinite loop
>> To: bug <at> octave.org
>> Date: Saturday, December 6, 2008, 1:23 PM
>> Afief Halumi wrote:
>>> Bug report for Octave 3.0.1 configured for
>> i486-pc-linux-gnu
>>>
>>> Description:
>>> -----------
>>>
>>>  trying to polyfit log(x) when x starts at 0(
>> log(0)=-inf according to
>>> octave ) keeps running indefinitely(or at least for
>> over 15 minutes)
>>>
>>> Repeat-By:
>>> ---------
>>>
>>>  * x=0:0.1:10; y=log(x); polyfit(x,y,3);
>>>
>> I can confirm this bug with 3.0.1.
>>
>> In octave freshly built from the mercurial sources the
>> command returns:
>> octave:4> x=0:0.1:10; y=log(x); polyfit(x,y,3)
>> ans =
>>
>>   NaN   NaN   NaN  -Inf
>> So apparently, it has already been fixed.
>>
>> can somebody check in 3.0.3?
>>
>> Thorsten
>>
>
> In my case octave-3.0.3 hangs.
>
> Regards,
>  Sergei.

The "compatible" behavior would be

 >> x=0:0.1:10; y=log(x); polyfit(x,y,3)
ans =
    NaN   NaN   Inf  -Inf

Running the developer's source (a week or two old) give

octave:1> x=0:0.1:10; y=log(x); polyfit(x,y,3)
ans =
    NaN   NaN   NaN  -Inf

For me the result is instantaneous.

Ben

Gmane