[Octave-bug-tracker] [bug #63063] ode{23, 45} options "Events" and "OutputFcn" do not perform correctly.

[Ken Marek]

Follow-up Comment #1, bug #63063 (project octave):

A correction to the original bug description:

In test case 2 (and 4), two events were encountered on the same step, and the
second event was terminal. Octave detected a terminal event but only reported
the first (non-terminal) event. If the testEvent function were redefined so
that the non-terminal event occurs on a different step than the terminal
event, e.g.:

function [val, isTerm, dir] = testEvent ( t , y )
  isTerm = [ 0; 1 ];
  dir = [ 1; 1 ];
  val = [ y(1) - 0.1; y(1) - 1.5 ];
end

then test case 2 returns the same as Matlab.

This is still a different result than Matlab gives, and should be fixed. The
pre-empting of OutputFcn by an Events break (case 4) is still an issue,
although with the modified testEvent function, both Events would be reported.

Contrary to my initial indication, fixing test case 2 will require
modifications to ode_event_handler.m. I believe the rest of the problems still
lie in integrate_adaptive.m.


    _______________________________________________________

Reply to this item at:

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

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