org.apache.commons.math3.ode.events

Class EventFilter

• All Implemented Interfaces:
EventHandler

public class EventFilter
extends Object
implements EventHandler
Wrapper used to detect only increasing or decreasing events.

General events are defined implicitely by a g function crossing zero. This function needs to be continuous in the event neighborhood, and its sign must remain consistent between events. This implies that during an ODE integration, events triggered are alternately events for which the function increases from negative to positive values, and events for which the function decreases from positive to negative values.

Sometimes, users are only interested in one type of event (say increasing events for example) and not in the other type. In these cases, looking precisely for all events location and triggering events that will later be ignored is a waste of computing time.

Users can wrap a regular event handler in an instance of this class and provide this wrapping instance to the ODE solver in order to avoid wasting time looking for uninteresting events. The wrapper will intercept the calls to the g function and to the eventOccurred method in order to ignore uninteresting events. The wrapped regular event handler will the see only the interesting events, i.e. either only increasing events or decreasing events. the number of calls to the g function will also be reduced.

Since:
3.2
Version:
$Id: EventFilter.html 885258 2013-11-03 02:46:49Z tn$

• Nested classes/interfaces inherited from interface org.apache.commons.math3.ode.events.EventHandler

EventHandler.Action
• Constructor Summary

Constructors
Constructor and Description
EventFilter(EventHandler rawHandler, FilterType filter)
• Method Summary

Methods
Modifier and Type Method and Description
EventHandler.Action eventOccurred(double t, double[] y, boolean increasing)
Handle an event and choose what to do next.
double g(double t, double[] y)
Compute the value of the switching function.
void init(double t0, double[] y0, double t)
Initialize event handler at the start of an ODE integration.
void resetState(double t, double[] y)
Reset the state prior to continue the integration.
• Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
• Constructor Detail

• EventFilter

public EventFilter(EventHandler rawHandler,
FilterType filter)
Parameters:
rawHandler - event handler to wrap
filter - filter to use
• Method Detail

• init

public void init(double t0,
double[] y0,
double t)
Initialize event handler at the start of an ODE integration.

This method is called once at the start of the integration. It may be used by the event handler to initialize some internal data if needed.

Specified by:
init in interface EventHandler
Parameters:
t0 - start value of the independent time variable
y0 - array containing the start value of the state vector
t - target time for the integration
• g

public double g(double t,
double[] y)
Compute the value of the switching function.

The discrete events are generated when the sign of this switching function changes. The integrator will take care to change the stepsize in such a way these events occur exactly at step boundaries. The switching function must be continuous in its roots neighborhood (but not necessarily smooth), as the integrator will need to find its roots to locate precisely the events.

Also note that the integrator expect that once an event has occurred, the sign of the switching function at the start of the next step (i.e. just after the event) is the opposite of the sign just before the event. This consistency between the steps must be preserved, otherwise exceptions related to root not being bracketed will occur.

This need for consistency is sometimes tricky to achieve. A typical example is using an event to model a ball bouncing on the floor. The first idea to represent this would be to have g(t) = h(t) where h is the height above the floor at time t. When g(t) reaches 0, the ball is on the floor, so it should bounce and the typical way to do this is to reverse its vertical velocity. However, this would mean that before the event g(t) was decreasing from positive values to 0, and after the event g(t) would be increasing from 0 to positive values again. Consistency is broken here! The solution here is to have g(t) = sign * h(t), where sign is a variable with initial value set to +1. Each time eventOccurred is called, sign is reset to -sign. This allows the g(t) function to remain continuous (and even smooth) even across events, despite h(t) is not. Basically, the event is used to fold h(t) at bounce points, and sign is used to unfold it back, so the solvers sees a g(t) function which behaves smoothly even across events.

Specified by:
g in interface EventHandler
Parameters:
t - current value of the independent time variable
y - array containing the current value of the state vector
Returns:
value of the g switching function