[bug #57715] Discontinuity time - event missed - oops?

Follow-up Comment #1, bug #57715 (project mcsim):

Thanks. Yes, the way input function values are computed on the fly is prone to
that kind of problems. A general fix would be to pre-compute all
discontinuities and outputs and merge events close by an epsilon. That's a big
task though.
Spikes() in itself is problematic too, and using Events() is better. Can you
try to do away with Spikes()? You seem to have an Event at the same time, and
at that time the input variable itself takes value 1 (0 elsewhere). So it is
in fact a Spike... You can them use it anyway you want to alter your
computations.
Frederic


    _______________________________________________________

Reply to this item at:

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

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