Engineering methods¶
Use these chapters to decide what a result means and whether its assumptions fit your study. Begin with a worked study if you have not yet followed a run from inputs to indexed results.
Each chapter begins with an illustrated Console investigation: a result plot, a selected case or contribution, and the quantities or sources behind it. For hardware, requirement tables and cross-system review, start with the completed-study tour. Open a screenshot for its full-size view; on a narrow screen, swipe wide figures to inspect the labels.
| Question | Read |
|---|---|
| How does the whole spacecraft calculation close? | System sizing and convergence |
| What orbit and operational assumptions drive it? | Environment and operations |
| What shape and configuration are actually analyzed? | Geometry, placement and deployables |
| What is counted, margined and spatially distributed? | Mass and mass properties |
| Does the launch configuration satisfy represented limits? | Launch accommodation |
| Does generation, storage and recharge close? | Electrical power |
| What temperatures and control hardware result? | Thermal balance |
| What electrical capability remains at end of life? | Lifetime and degradation |
| Can the maneuver plan actually be delivered? | Propulsion |
| What attitude-control capability is represented? | ADCS and robustness |
| Does the link and daily data budget close? | Communications |
| What does the estimate include, and what supports it? | Cost and authority |
Follow the input assumptions into the equations, then compare the outputs with the chapter's worked-study links. When two subsystems share a quantity, check which one calculates it and which consumes it; this is especially useful for geometry exposure, heater power and hardware mass.
The glossary explains common result terms. Evidence and limits describes the validation basis shared by these method explanations.
The contract field reference owns exact field names, constraints, defaults and downloadable schemas.