octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Octave on Windows with large arrays ?


From: Tatsuro MATSUOKA
Subject: Re: Octave on Windows with large arrays ?
Date: Fri, 17 Mar 2017 16:13:50 +0900 (JST)

----- Original Message -----

> From: Tatsuro MATSUOKA >
> To: Julien Bect ; "octave-maintainers
> Cc: 
> Date: 2017/3/17, Fri 08:35
> Subject: Re: Octave on Windows with large arrays ?
> 
> ----- Original Message -----
>> From: Julien Bect 
>> To: address@hidden 
>> Date: 2017/3/17, Fri 06:06
>> Subject: Re: Octave on Windows with large arrays ?
>> 
>> 
>> Le 16/03/2017 à 09:11, Tatsuro MATSUOKA a écrit :
>> 
>> I have executed __run_test_suite__ but hangs.   
> libinterp\corefcn\lsode.cc-tst .............................. LSODE-- 
>  AT T (=R1) AND STEP SIZE H (=R2), THE
>        CORRECTOR CONVERGENCE FAILED REPEATEDLY
>        OR WITH ABS(H) = HMIN
>       In above,  R1 =  0.0000000000000D+00   R2 =  0.3802108489572D-09
>  LSODE--  AT T (=R1) AND STEP SIZE H (=R2), THE
>        CORRECTOR CONVERGENCE FAILED REPEATEDLY
>        OR WITH ABS(H) = HMIN
>       In above,  R1 =  0.0000000000000D+00   R2 =  0.6424715644617D-09
>  LSODE--  AT T (=R1) AND STEP SIZE H (=R2), THE
>        CORRECTOR CONVERGENCE FAILED REPEATEDLY
>        OR WITH ABS(H) = HMIN
>       In above,  R1 =  0.0000000000000D+00   R2 =  0.4165001171641D-09
>  PASS      2/5
>                                                                   FAIL    3
>   libinterp\corefcn\lu.cc-tst .................................panic: 
> Segmentation fault -- stopping myself... Mmmmmmmm. Anyway I will test again 
> against binary I am now re-building after clean up.
>> 
>> Hi Tatsuro,
>> 
>> I haven't tried myself, but my colleague confirmed the crash with
>       lsode.
>> 
>> There were also some failed tests with det and eig (see below). 
>       Have you already seen these ?
>> 
>> @++
>> Julien
>> 
>> 
>> ________________________________
>> 
>> ***** assert (det ([1, 2; 3, 4]), -2, 10*eps) 
>> !!!!! test failed 
>> ASSERT errors for:  assert (det ([1, 2; 3, 4]),-2,10 * eps) 
>>  
>>   Location  |  Observed  |  Expected  |  Reason 
>>      ()           2            -2        Abs err 4 exceeds tol 2.2204e-015 
>> 
>> ***** assert (det (single ([1, 2; 3, 4])), single (-2), 10*eps 
> ("single")) 
>> !!!!! test failed 
>> ASSERT errors for:  assert (det (single ([1, 2; 3, 4])),single (-2),10 * eps 
> ("single")) 
>>  
>>   Location  |  Observed  |  Expected  |  Reason 
>>      ()           2            -2        Abs err 4 exceeds tol 1.1921e-006 
>> 
>> ***** test 
>>  A = diag([10^-16, 10^-15]); 
>>  chol_qz_accuracy (A, A, true, false); 
>> !!!!! test failed 
>> ASSERT errors for:  assert (isequal (A * V2, A * V2 * D2),is_chol_accurate) 
>>  
>>   Location  |  Observed  |  Expected  |  Reason 
>>      ()           1            0         Abs err 1 exceeds tol 0
>> 
>> 
> 
> 
> I have built again octave-4.2.1 with LargeArray after clean up but results 
> are 
> the same.
> 
>> I haven't tried myself, but my colleague confirmed the crash with
>       lsode.
> 
> 
> crash happens on lu but not onlsode
> 
>   libinterp\corefcn\lu.cc-tst .................................panic: 
> Segmentation fault -- stopping myself...
> 
> 
> on lsode error happens.
> 
> Hang on lu is easy to reproduce.
> 
>>>  A=rand(5);
>>>  [L,U,P]=lu(A);
> 
> panic: Segmentation fault -- stopping myself...
> attempting to save variables to 'octave-workspace'...
> save to 'octave-workspace' complete
> 
>> There were also some failed tests with det and eig (see below). 
>       Have you already seen these ?
> 
> 
> I have also seen this.
> 
> On octave-4.0.3 for windows with Large Arrays, I have not seen such errors on 
> __run_test_suite__.
> 
> Unfortunately octave-4.2.x for windows with Large Arrays has many fault, it 
> cannot be usable.
> 
> octave-4.0.3 for windows with Large Arrays can be downloaded from 
> http://www.tatsuromatsuoka.com/octave/Eng/Win/
> 
 

Perhaps my build failed without --enable-fortran-int64.
(That option was not required for mxe-build before I think )

I am trying rebuild 4.2.1 adding this option.

Tatsuro 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]