Mach 30 Technical Roadmap - v 1.0 Roadmap Evaluation of Trajectory (launch and reentry) Subsystem - Open Design Engine

v 1.0 Roadmap Evaluation of Trajectory (launch and reentry) Subsystem

Please comment below on the 5 requirements from Choosing the technology branch for the v 1.0 roadmap regarding projects related to launch vehicle Trajectory. Feel free to brain storm potential projects related to this subsystem, evaluate any or all requirements, or otherwise comment on the suitability of this subsystem for the v 1.0 roadmap. Note, the end result should be group consensus on requirements score and any notes to include on the evaluation page in the wiki.

Replies (4)

RE: v 1.0 Roadmap Evaluation of Trajectory (launch and reentry) Subsystem - Added by Jeremy Wright over 9 years ago

Seems like there could be overlap between this subsystem and the attitude control subsystem. Is there?

RE: v 1.0 Roadmap Evaluation of Trajectory (launch and reentry) Subsystem - Added by J. Simmons over 9 years ago

See my comment on v 1.0 Roadmap Evaluation of Attitude Control Subsystem (TL;DR - this is about the difference between operations in space and operations one the way up and down).

RE: v 1.0 Roadmap Evaluation of Trajectory (launch and reentry) Subsystem - Added by Matt Maier over 9 years ago

Given the limitations on active controls, it seems like this would only be able to be a passive data-gathering system.

RE: v 1.0 Roadmap Evaluation of Trajectory (launch and reentry) Subsystem - Added by J. Simmons over 9 years ago

Yeah, it seems likely that export controls would put a significant limit on the nature of projects we could develop. Even just doing simulations could run into trouble (some software related to trajectory design and analysis is export controlled).

I am also not aware of much engineering expertise in the Mach 30 community related to this subsystem beyond Jason D - score = 1.

(1-4/4)