octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #63162] Inaccurate "Events" location in ode45,


From: Ken Marek
Subject: [Octave-bug-tracker] [bug #63162] Inaccurate "Events" location in ode45, ode23(s)
Date: Wed, 5 Oct 2022 15:57:31 -0400 (EDT)

Follow-up Comment #6, bug #63162 (project octave):

Ok, I think I can make that happen. Just to clarify, this is what you want:

* Additional parameters passed to ode45, etc. will continue to be passed to
fcn, as well as to OutputFcn and Events if they exist, but we will now
generate a warning that this functionality is deprecated.

Rather than passing along all the arguments explicitly, couldn't we just
redefine the functions in the first script? I.e., in ode45, something like:

temp_fcn = fcn;
funarguments = {varargin{2:numel (varargin)}};
fcn = @(t,y) feval(temp_fcn,t,y,funarguments);

and so on for OutputFcn and Events? Then everything that was given those
function handles afterward wouldn't need to worry about whether or not there
are extra input parameters.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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