How bpera1111/ayme works
Project Type and Purpose
• This is an academic control‐system simulation and analysis project built with MATLAB and Simulink.
• It comprises two main phases (“Primera_parte” and “Segunda_Parte”), each containing Simulink models (.slx), MATLAB scripts (.m), and data files (.mat).
• It also includes report and presentation artifacts (LaTeX sources, PDFs) under “Informe” and “Presentación.”
High‐Level Architecture
• Components:
• Model Repository: Simulink models (.slx) organized in “Primera_parte” and “Segunda_Parte.”
• Simulation Engine: MATLAB/Simulink running models, generating raw signal outputs and data caches (slprj, varcache).
• Analysis Scripts: MATLAB .m files (e.g., graficos.m, simulacion.m) that load .mat data, compute metrics, tune controllers.
• Data Storage: .mat files under each part’s “signals” or root directory storing simulation results.
• Documentation: LaTeX sources and compiled PDFs in “Informe” and TeX/Beamer files in “Presentación.”
• Auto‐code / Acceleration: Simulink Coder / Rapid Accelerator outputs in slprj/raccel and slprj/_sfprj.
Relationships and Data Flows
• Models → Simulation Engine:
• Simulink loads .slx models to run time-domain tests.
• Rapid Accelerator (raccel) may be invoked to speed up simulations.
• Simulation Engine → Data Storage:
• Results exported as .mat files and stored under “signals” or root.
• Caches (slprj/sim/varcache) are generated automatically.
• Data Storage → Analysis Scripts:
• Scripts read .mat files, calculate control metrics, produce plots.
• Outputs (plots, figures) saved to disk, then imported into reports.
• Analysis Scripts → Documentation:
• Figures and numeric results get embedded into LaTeX reports and presentations.
• Final PDFs are produced in “Informe/…pdf” and “Presentación/presentacion.pdf.”
Architectural Patterns and Principles
• Clear separation of concerns: modeling vs. simulation vs. analysis vs. documentation.
• Reproducibility: simulation scripts and data caches ensure consistent results.
• Modular design: each Simulink subsystem (electromechanical, thermal, control) is a separate .slx.
• Pipeline flow: Model → Run → Process → Report.
Technologies and Frameworks
• MATLAB for scripting (.m), data handling, plotting.
• Simulink for dynamic system modeling (.slx), with Simulink Coder for acceleration.
• LaTeX/Beamer for report and slides.
• Standard file I/O (.mat, .pdf) for portability.