PROJECTS
Technical Tool·2021–2022·Completed

Dynamic PID Controlfor DroneTrajectory Optimization

MATLAB Sandbox for Hybrid Optimization, PID Control, and GMM Target Fields

A compact technical simulation project for trajectory optimization over GMM-style target landscapes, combining optimization logic with a dynamic PID controller to study drone motion, error, and response in one MATLAB sandbox.

Project Evidence
MATLABDynamic PIDTrajectory OptimizationGMM FieldsSimulation Outputs
Tool Facts
Tool type
MATLAB sandbox
Compact experiment loop, not a platform
Focus
Trajectory + PID
Optimization logic coupled to control response
Target fields
GMM-style
Structured landscapes for motion studies
Outputs
Motion traces
Trajectory, speed, and error inspection
02 · Tool Facts

A Sandbox, Not a Platform

Simulation-first

The project is a controlled experiment environment, not a deployable autonomy stack. Its value is in making the optimization-plus-control loop inspectable.

One technical loop

Target field, optimizer, controller, simulated motion, and output plots live in one sandbox so behavior can be studied end to end.

Compact scope

The page should stay tool-sized. It should feel technical and real without pretending this repo is broader than it is.

03 · Simulation Loop

The Technical Loop the Repo Actually Makes Visible

The useful thing about the project is not UI breadth. It is the closed loop between target landscape, optimizer, controller, motion, and output plots.

Simulation Loop
01
GMM target field
02
Trajectory optimization logic
03
Dynamic PID controller
04
Simulated drone motion
05
Trajectory / speed / error outputs
04 · Why Dynamic PID Helped

Why the Controller Layer Was Worth Isolating

Response tuning mattered

The point of the dynamic PID layer was not only stability. It gave a way to shape how aggressively the simulated drone responded to the optimizer’s intended motion.

Optimization needed a controller partner

Optimization logic alone does not say how the simulated vehicle should settle, overshoot, or recover. The PID loop made those behaviors explicit.

Outputs became interpretable

Once trajectory, speed, and error were produced together, the sandbox became a clearer place to compare controller behavior than a loose collection of scripts and plots.

05 · Outputs / Visualizations

The Outputs That Made the Sandbox Useful

Trajectory traces

Observe how the simulated path moves across the target landscape under the combined optimizer and controller.

Speed profiles

Inspect whether aggressive optimization updates translate into stable or erratic motion commands.

Tracking error curves

Use error plots to understand settling behavior, transient mismatch, and the practical effect of controller tuning.

Open MATLAB Simulation Repo