Required stack
필요 기술
MATLABThermodynamicsHeat TransferMechanical EngineeringSimulationTechnical WritingEngineering DesignTechnical Drawing
Project brief
프로젝트 내용
I’m wrapping up my final-year project on waste heat recovery for a micro gas turbine and I need an extra set of expert hands. The overall Brayton-cycle model is already sketched, but the counter-flow heat exchanger is where I need the most guidance—sizing, effectiveness calculations, pressure-drop estimates, the works.
Here’s the workflow I have in mind: refine the thermodynamic model so the turbine, recuperator and ambient conditions are properly coupled; translate that into a clean, well-commented MATLAB script; then iterate on the exchanger geometry until we hit an efficient balance between recovered power, core pressure losses and realistic manufacturing constraints. Throughout the process I’d like short explanations of each assumption and equation so I can defend them during my viva.
Deliverables I must hand in:
• Design schematics (dimensional drawing or clearly annotated sketch)
• Performance analysis report summarising key figures—ε, NTU, UA, ΔP, gain in overall cycle efficiency
• MATLAB simulation results and the .m files themselves, ready to rerun with new inputs
If you can start right away and keep the code and documentation student-budget friendly, let’s talk.
Here’s the workflow I have in mind: refine the thermodynamic model so the turbine, recuperator and ambient conditions are properly coupled; translate that into a clean, well-commented MATLAB script; then iterate on the exchanger geometry until we hit an efficient balance between recovered power, core pressure losses and realistic manufacturing constraints. Throughout the process I’d like short explanations of each assumption and equation so I can defend them during my viva.
Deliverables I must hand in:
• Design schematics (dimensional drawing or clearly annotated sketch)
• Performance analysis report summarising key figures—ε, NTU, UA, ΔP, gain in overall cycle efficiency
• MATLAB simulation results and the .m files themselves, ready to rerun with new inputs
If you can start right away and keep the code and documentation student-budget friendly, let’s talk.