This article is a stub. You can help the TASOPT.jl community by expanding it
Although the Design and evaluation page exists in documentation, it gives little insight for how TASOPT goes about sizing to a mission. This can be problematic if a user sets a variable in the input file that is not a "design parameter" (i.e., does not drive the design in any way).
More directly, the mission assumptions are not yet stated in the docs, and a page should be created
[ ] Document the mission assumptions (i.e., flight profiles and how that's linked to performance)
[ ] Document the sizing process in broad strokes
[ ] Identify or show how to identify what is a driving parameter. document
This article is a stub. You can help the TASOPT.jl community by expanding it
Although the
Design and evaluationpage exists in documentation, it gives little insight for how TASOPT goes about sizing to a mission. This can be problematic if a user sets a variable in the input file that is not a "design parameter" (i.e., does not drive the design in any way).More directly, the mission assumptions are not yet stated in the docs, and a page should be created