pockit.lobatto
Submodule for Legendre-Gauss-Lobatto pseudo-spectral methods.
The Lobatto phase is suitable for problems with continuous state and control variables.
A phase is a lower level objective of a multiple-phase optimal control problem.
Initialize a phase with given state, control, and static variables.
States and controls can be given as the number of variables or the list of variable names. If names are given, they are used as the names of the variables. Otherwise, the names are generated automatically as \( x_0, x_1, \dots, x_{n - 1} \).
Static variables should be identical to those defined in the system level.
The identifier
should be unique for each phase in a given system to avoid possible name conflict.
It is recommended to use the System.new_phase()
method of the System
object to create phases instead of manually using this method.
If simplify
is True
, every symbolic expression will be simplified (by sympy.simplify()
) before
being compiled. This will slow down the speed of compilation.
If parallel
is True
, the parallel
flag will be passed to the Numba JIT compiler,
which will generate parallel code for multicore CPUs.
This will slow down the speed of compilation and sometimes the speed of execution.
If fastmath
is True
, the fastmath
flag will be passed to the Numba JIT compiler,
see Numba
and LLVM documentations for details.
Arguments:
- state: Number of state variables or list of state variable names.
- control: Number of control variables or list of control variable names.
- symbol_static_parameter: list of static parameters,
should be identical to those in the
System
object. - identifier: Unique identifier of the phase.
- simplify: Whether to use Sympy to simplify
sympy.Expr
before compilation. - parallel: Whether to use Numba
parallel
mode. - fastmath: Whether to use Numba
fastmath
mode.
Lobatto nodes cannot approximate discontinuous functions precisely.
Use radau nodes instead.
Raises:
- NotImplementedError: Always
Check the continuous error. Same as check_continuous()
.
Arguments:
- variable: Variable to be checked.
- static_parameter: Static parameter to be checked. Set to
None
if the phase has no static parameters. - absolute_tolerance_continuous: Absolute tolerance for continuous error.
- relative_tolerance_continuous: Relative tolerance for continuous error.
- tolerance_discontinuous: In each subinterval, after scaling to \( [0, 1] \), the bang-bang control functions
should either be less than
tolerance_discontinuous
or greater than1 - tolerance_discontinuous
simultaneously. - tolerance_mesh: Skip the check if the mesh width is smaller than this value.
Returns:
True
if the error is within the tolerance,False
otherwise.
Lobatto nodes cannot approximate discontinuous functions precisely.
Use radau nodes instead.
Raises:
- NotImplementedError: Always
Adjust the mesh and the number of interpolation points to match the
continuous error tolerance. Same as refine_continuous()
.
Arguments:
- variable: Variable of the previous iteration.
- static_parameter: Static parameter of the previous iteration.
Set to
None
if the phase has no static parameters. - absolute_tolerance_continuous: Absolute tolerance for continuous error.
- relative_tolerance_continuous: Relative tolerance for continuous error.
- tolerance_discontinuous: In each subinterval, after scaling to \( [0, 1] \), the bang-bang control functions
should either be less than
tolerance_discontinuous
or greater than1 - tolerance_discontinuous
simultaneously. - num_point_min: Minimum number of interpolation points.
- num_point_max: Maximum number of interpolation points.
- mesh_length_min: Minimum mesh length.
- mesh_length_max: Maximum mesh length.
Inherited Members
- pockit.base.phasebase.PhaseBase
- set_dynamics
- set_integral
- set_phase_constraint
- set_boundary_condition
- set_discretization
- check_continuous
- refine_continuous
- n_x
- x
- n_u
- u
- n
- n_s
- s
- t
- F_d
- n_d
- F_I
- n_I
- I
- F_c
- n_c
- v_lb
- v_ub
- c_lb
- c_ub
- s_b
- bc_0
- bc_f
- F_b
- n_b
- t_0
- t_f
- N
- ok
- index_state
- index_control
- index_mstage
- l_v
- r_v
- t_m
- l_m
- r_m
- L_m
- w_m
- f_v2m
- T_v
- T_v_coo
- I_m
- I_m_coo
- l_d
- r_d
- t_m_aug
- l_m_aug
- r_m_aug
- L_m_aug
- w_aug
- P
- V_xu_aug
- T_x_aug
- I_m_aug
- t_x
- t_u
- l_x
- r_x
- l_u
- r_u
- L_x
- L_xu
- L
A system is the higher level objective of a multiple-phase optimal control problem.
Initialize a system with given static parameters.
If static_parameter
is an integer, the names are generated automatically as \( s_0, s_1, \dots, s_{n-1} \).
If simplify
is True
, every symbolic expression will be simplified (by sympy.simplify()
) before
being compiled. This will slow down the speed of compilation.
If parallel
is True
, the parallel
flag will be passed to the Numba JIT compiler,
which will generate parallel code for multicore CPUs.
This will slow down the speed of compilation and sometimes the speed of execution.
If fastmath
is True
, the fastmath
flag will be passed to the Numba JIT compiler,
see Numba
and LLVM documentations for details.
Arguments:
- static_parameter: Number of static parameters or list of static parameter names.
- simplify: Whether to use Sympy to simplify
sympy.Expr
before compilation. - parallel: Whether to use Numba
parallel
mode. - fastmath: Whether to use Numba
fastmath
mode.
Lobatto nodes cannot approximate discontinuous functions precisely.
Use radau nodes instead.
Raises:
- NotImplementedError: Always
Check the continuous error. Same as check_continuous()
.
Arguments:
- value: The variable to be checked. If the system has only one phase and no static variables,
value
can be a singleVariable
object. Otherwise,value
should be a list ofVariable
objects, one for eachPhase
, followed by an array as values of static variables. - absolute_tolerance_continuous: Absolute tolerance for continuous error.
- relative_tolerance_continuous: Relative tolerance for continuous error.
- tolerance_discontinuous: In each subinterval, after scaling to \( [0, 1] \), the bang-bang control functions
should either be less than
tolerance_discontinuous
or greater than1 - tolerance_discontinuous
simultaneously. - tolerance_mesh: Skip the check if the mesh width is smaller than this value.
Returns:
True
if the error is within the tolerance,False
otherwise.
Lobatto nodes cannot approximate discontinuous functions precisely.
Use radau nodes instead.
Raises:
- NotImplementedError: Always
Adjust the mesh and the number of interpolation points to match the
continuous error tolerance. Same as refine_continuous()
.
Arguments:
- value: The variable to be checked. If the system has only one phase and no static variables,
value
can be a singleVariable
object. Otherwise,value
should be a list ofVariable
objects, one for eachPhase
, followed by an array as values of static variables. - absolute_tolerance_continuous: Absolute tolerance for continuous error.
- relative_tolerance_continuous: Relative tolerance for continuous error.
- tolerance_discontinuous: In each subinterval, after scaling to \( [0, 1] \), the bang-bang control functions
should either be less than
tolerance_discontinuous
or greater than1 - tolerance_discontinuous
simultaneously. - num_point_min: Minimum number of interpolation points.
- num_point_max: Maximum number of interpolation points.
- mesh_length_min: Minimum mesh length.
- mesh_length_max: Maximum mesh length.
Returns:
The
Variable
s interpolated to the new discretization scheme.
Inherited Members
- pockit.base.systembase.SystemBase
- new_phase
- set_phase
- set_objective
- set_system_constraint
- update
- objective
- constraints
- gradient
- jacobianstructure
- jacobian
- hessianstructure_o
- hessian_o
- hessianstructure_c
- hessian_c
- hessianstructure
- hessian
- check_continuous
- refine_continuous
- n_s
- s
- n_p
- p
- F_o
- n_c
- F_c
- v_lb
- v_ub
- c_lb
- c_ub
- N
- L
- ok
Optimization variable for a discretized phase.
Variable
objects provide two kinds of interfaces:
- Plain 1D array for passing to the solver;
- Methods for quickly accessing specific variables for users to set and extract corresponding values.
Besides, Variable
provides methods to generate interpolation matrices for mesh adaption and plotting.
Generally, users need not create Variable
objects directly.
A better way is to use the func:constant_guess
and func:linear_guess
functions to generate a starting point and possibly adjust it manually.