[Octave-bug-tracker] [bug #63791] movfun - high intermediate memory use for moderate data input resulting in out of memory errors

[Liang Tang]

Follow-up Comment #36, bug #63791 (project octave):

I am going to break a golden rule with this feedback: never criticize unless I
have a better solution.  

I did try to read the movfun code but failed to follow.  My sense is that the
code is unnecessarily complicated for my original report, i.e.,  movmean.  

If the choice is between spending resource to speed up fsolve or sqp vs
movmean, I would pick fsolve/sqp in a heart beat.  So ideally, utilities like
movmean should be done only once such that resource can be freed for other
numerical intensive functions.  For example, can  we make parfor work? 
Thanks.  


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63791>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/