Final Project Report Template

Front Page

  • Title, course, instructor, academic year
  • Group members + roles
  • Date
  • Optional: representative image/diagram

Abstract (150–250 words)

  • Context (1–2 sentences)
  • Problem statement
  • Method (what you built)
  • Evaluation (how tested)
  • Key results (include 1–2 quantitative numbers)
  • Conclusion (impact + limitations)

1. Introduction

  • Operational scenario & motivation
  • Problem statement (precise)
  • Objectives
  • Contributions
  • Report organization

3. System Description

  • Models
  • Sensors and assumptions
  • Architecture diagram (pipeline)
  • Data / simulation environment summary

4. Methodology

4.1 Models
  • E.g., Equations of motion (only what’s needed)
  • Hydrodynamic terms included (added mass, damping, restoring)
  • Parameter selection / identification
  • Assumptions and implications
4.2 Control and/or Estimation
  • Control law (derivation or rationale)
  • Estimation method (state, measurement model, noise assumptions)
  • Stability/observability considerations (qualitative is OK)
4.3 Acoustic Integration (If Relevant)
  • Measurement model and update rate
  • Noise model, outliers, latency
  • How dynamics and sensing interact in the loop

5. Experimental Setup

  • Scenarios (at least 2–3)
  • Baselines
  • Metrics (define mathematically when possible)
  • Implementation details:
    • timestep, numerical integration
    • constraints
    • hardware/software stack (brief)

6. Results

  • Present results by objective:
    • Objective + plot/table + interpretation
  • Include:
    • trajectory overlays
    • error summaries (mean/max/RMSE)
    • robustness tests
  • One paragraph of interpretation per figure/table

7. Discussion

  • What the results mean operationally
  • Limitations (model mismatch, parameter uncertainty, unmodeled currents)
  • Failure cases and why they happen
  • Generalization: what transfers to other vehicles/scenarios

8. Conclusions

  • 3–6 bullet conclusions tied to objectives
  • Final takeaway message

9. Future Work

  • Ranked list (impact vs effort)
  • Next validation step (what experiment would you run next?)

References

  • Use a consistent style (IEEE/APA/ACM—anything consistent)
  • Cite datasets, libraries, and important papers you used

Appendices (Optional but Useful)

  • Parameter tables
  • Additional plots
  • Derivations
  • Reproducibility: how to run the code / reproduce results

Length suggestion: approximately 6–10 pages + appendices (depending on expectations)