Use computational modeling and simulation tools

I finished a simulation of ventilation effects for the new greenhouse module; send the model files and the two-page summary to Dr. Morales in modeling and then to Claire in project controls for review, with a request they comment by Tuesday. Before sending, run the sensitivity scenarios for wind and temperature bounds, add one-paragraph notes on assumptions in the model input sheet, and ensure the key outputs export as CSV for traceability.

Before I hand the simulation to the senior engineer, make it simple to validate: put the three most sensitive inputs on an assumptions dashboard, generate a one-click table showing output ranges for low/nominal/high environmental conditions, and highlight any boundary conditions where the model becomes unstable. Also flag where experimental data is needed to reduce uncertainty.

When I widened the temperature range the simulation started producing unrealistic oscillations; the lead engineer expects a quick fix and I cannot tell whether the issue is a modeling error, a missing damping parameter, or poor numerical stability. What focused checks should I run first to diagnose the cause and what is the likeliest explanation given this behavior?

I keep rebuilding nearly identical simulation input sheets for every greenhouse project, losing hours mapping sources and re-documenting assumptions. What one template change and what one documentation habit will stop me redoing this work and make peer review faster across future projects?