[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension t
From: |
Liang Tang |
Subject: |
[Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type |
Date: |
Sun, 12 Feb 2023 06:33:44 -0500 (EST) |
Follow-up Comment #14, bug #63791 (project octave):
As I mentioned before, by cutting off the number of points by half, this works
on my low power laptop. When it works for small data (not this example), the
results are correct. I think one of you can do the same to see if the array
sizes are the same as what shown below. If the array sizes are different, we
have a different problem.
On MS window, virtual memory is very ineffective. So I also expect virtual
memory handling on Linux and Win should be different. Are u on Linux or Win?
I don't understand the method. Therefore I cannot investigate numbers but I
can compare if a correct reference exists.
>> tic, v=movmean(rand(1,500000), 513); toc
Elapsed time is 3.28492 seconds.
>
v=movmean(rand(1,500000), 513); break point @ 299 as before.
stopped in movfun>movfun_oncol at line 299
[C:\Octave\Octave-7.1.0\mingw64\share\octave\7.1.0\m\signal\movfun.m]
299: y(C,:) = fcn (x(slcidx));
debug> whos
Variables visible from the current scope:
variables in scope: movfun_oncol:
C:\Octave\Octave-7.1.0\mingw64\share\octave\7.1.0\m\signal\movfun.m
Attr Name Size Bytes Class
==== ==== ==== ===== =====
f C 1x499488 24 double
f Cpos 1x256 24 double
f Cpre 1x256 24 double
N 1x1 8 double
ans 1x1 1 logical
f bcfunc 1x1 0 function_handle
f fcn 1x1 0 function_handle
f odim 1x1 8 double
f slcidx 513x499488 2049898752 double
f win 513x1 4104 double
f wlen 1x2 16 double
f x 500000x1 4000000 double
f y 500000x1 4000000 double
Total is 257737864 elements using 2057902961 bytes
dbstep here
debug> whos
Variables visible from the current scope:
variables in scope: movfun_oncol:
C:\Octave\Octave-7.1.0\mingw64\share\octave\7.1.0\m\signal\movfun.m
Attr Name Size Bytes Class
==== ==== ==== ===== =====
f C 1x499488 24 double
f Cpos 1x256 24 double
f Cpre 1x256 24 double
N 1x1 8 double
ans 1x1 1 logical
f bcfunc 1x1 0 function_handle
f fcn 1x1 0 function_handle
f odim 1x1 8 double
f slcidx 513x499488 2049898752 double
f win 513x1 4104 double
f wlen 1x2 16 double
f x 500000x1 4000000 double
f y 500000x1 4000000 double
Total is 257737864 elements using 2057902961 bytes
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63791>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #63791] [octave-forge] (Statistics) movmean error message, (continued)
- [Octave-bug-tracker] [bug #63791] [octave-forge] (Statistics) movmean error message, Liang Tang, 2023/02/11
- [Octave-bug-tracker] [bug #63791] [octave-forge] (Statistics) movmean error message, Liang Tang, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Nicholas Jankowski, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Dmitri A. Sergatskov, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Nicholas Jankowski, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Liang Tang, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Rik, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Liang Tang, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Nicholas Jankowski, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Dmitri A. Sergatskov, 2023/02/11
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type,
Liang Tang <=
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Liang Tang, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Rik, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Liang Tang, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movmean - out of memory or dimension too large for index type, Liang Tang, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movfun - high intermediate memory use for moderate data input resulting in out of memory errors, Nicholas Jankowski, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movfun - high intermediate memory use for moderate data input resulting in out of memory errors, Nicholas Jankowski, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movfun - high intermediate memory use for moderate data input resulting in out of memory errors, Liang Tang, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movfun - high intermediate memory use for moderate data input resulting in out of memory errors, Rik, 2023/02/12
- [Octave-bug-tracker] [bug #63791] movfun - high intermediate memory use for moderate data input resulting in out of memory errors, Liang Tang, 2023/02/13
- [Octave-bug-tracker] [bug #63791] movfun - high intermediate memory use for moderate data input resulting in out of memory errors, Nicholas Jankowski, 2023/02/13