ptolemy.domains.ct.kernel
Class CTMultiSolverDirector

java.lang.Object
  extended byptolemy.kernel.util.NamedObj
      extended byptolemy.kernel.util.Attribute
          extended byptolemy.actor.Director
              extended byptolemy.actor.sched.StaticSchedulingDirector
                  extended byptolemy.domains.ct.kernel.CTDirector
                      extended byptolemy.domains.ct.kernel.CTMultiSolverDirector
All Implemented Interfaces:
Changeable, java.lang.Cloneable, Debuggable, DebugListener, Derivable, Executable, ModelErrorHandler, MoMLExportable, Nameable, java.io.Serializable
Direct Known Subclasses:
CTEmbeddedDirector, CTMixedSignalDirector

public class CTMultiSolverDirector
extends CTDirector

A CTDirector that uses multiple ODE solvers. The reason for switching solvers is that when abrupt changes in signals or actor functions (also called breakpoints) occur, the state of the system has to be recalculated. At these points, a special ODE solver, called the "breakpointODESolver" is used. The simulation is executed as if the breakpoint is a new starting point. Typically, breakpointODESolvers do not advance time.

This director handles both predictable breakpoints, which are breakpoints that are registered in the breakpoint table, and unpredictable breakpoints, which are breakpoints that are not known before hand.

This director can only be a top-level director. For a CT domain inside an opaque composite actor, use CTMixedSignalDirector (if the outer domain is discrete) or CTEmbeddedDirector (if the outer domain is a CT domain or a HS domain.)

This director recognizes actors that implement the CTStepSizeControlActor interface. To adjust step sizes, it polls such actors. If all are content with the current step size, then it attempts to raise the step size. If any is not content, then it reduces the step size. If there are no such actors, then it leaves the step size where it is.

This director has two more parameters than the CTDirector base class.