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 17:00:03 -0400 (EDT)

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

It depends what you mean by leaving it as is. To do the Events root finding I
need to send a handle of the complete Events function to the root solver, so
if there are extra inputs I still have to wrap the Events function in some
kind of anonymous function or something in ode_event_handler.m (Option 1), or
else copy and modify the entirety of fzero.m for use as a helper function in
ode_event_handler.m (Option 2, a real pain but possibly makes some minor
efficiency improvements). I can do one of these if you want.

I think it would actually be easier to implement my suggestion from comment #6
to maintain current functionality (Option 3), than to make everything work
with as much of the old code as possible, in which case I think I'd still have
code modifications in nearly all of the same places.

I can make Option 1 or 3 happen reasonably quickly, if you let me know your
preference. Option 2 will take a while.

There's also the other changes I mentioned:
* Cleaning up runge_kutta_interpolate.m, which I can mostly put back as before
or leave fixed; and
* Removing the y cell input from ode_event_handler.m. This one has to go, as
there's no way to accommodate the feature without knowing the underlying model
of the non-existent file that would theoretically use it.
So I guess let me know what you want for runge_kutta_interpolate.m as well.


    _______________________________________________________

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]