[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #57715] Discontinuity time - event missed - oops?
From: |
Frederic Yves Bois |
Subject: |
[bug #57715] Discontinuity time - event missed - oops? |
Date: |
Sat, 1 Feb 2020 02:53:59 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0 |
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/
- [bug #57715] Discontinuity time - event missed - oops?,
Frederic Yves Bois <=