From e2e24d6cb61aa43de78476286dd3042c673c7ccc Mon Sep 17 00:00:00 2001 From: Brad Clement Date: Tue, 16 Apr 2024 12:27:02 -0700 Subject: [PATCH] reference Blackbird (#126) * reference Blackbird * fix typo * rewording to fix innacuracies --- .../mission-modeling/advanced-the-merlin-interface.mdx | 8 +++++++- docs/overview/software-design-document.mdx | 10 ++++++++-- 2 files changed, 15 insertions(+), 3 deletions(-) diff --git a/docs/mission-modeling/advanced-the-merlin-interface.mdx b/docs/mission-modeling/advanced-the-merlin-interface.mdx index 1477696..7f5c91d 100644 --- a/docs/mission-modeling/advanced-the-merlin-interface.mdx +++ b/docs/mission-modeling/advanced-the-merlin-interface.mdx @@ -5,7 +5,13 @@ Aerie is a software framework for modeling spacecraft. Within Aerie is **Merlin* Because mission models are expressed in Java, rather than a custom DSL, Merlin has little to no ability to see the actual Java code comprising a mission model. Merlin must instead make inferences about the mission model based on its observable behavior. -Predecessors of Merlin, such as [APGen](https://trs.jpl.nasa.gov/handle/2014/45571) and [SEQGen](https://trs.jpl.nasa.gov/handle/2014/45455), provided a domain-specific language for mission modeling, allowing them to obtain deep, fine-grained information about the composition of a mission model before performing any simulation. +Merlin is a spiritual successor to the +[Blackbird](https://trs.jpl.nasa.gov/handle/2014/52245) planning +system, which similarly uses Java for activity and resource modeling. +Blackbird's design shed light on the myriad choices made in designing +Merlin. + +Predecessors of Merlin and Blackbird, such as [APGen](https://trs.jpl.nasa.gov/handle/2014/45571) and [SEQGen](https://trs.jpl.nasa.gov/handle/2014/45455), provided a domain-specific language for mission modeling, allowing them to obtain deep, fine-grained information about the composition of a mission model before performing any simulation. In some ways, this provides enhanced ergonomics, as a mission modeler can focus on expressing their model directly in the modeling language, without being concerned with the needs of the system that will be interpreting that model. The language itself captures all interesting aspects of the model. diff --git a/docs/overview/software-design-document.mdx b/docs/overview/software-design-document.mdx index bd57c1a..6830e2d 100644 --- a/docs/overview/software-design-document.mdx +++ b/docs/overview/software-design-document.mdx @@ -892,9 +892,15 @@ DSL, Merlin has little to no ability to see the actual Java code comprising a mission model. Merlin must instead make inferences about the mission model based on its observable behavior. -Predecessors of Merlin, such as +Merlin is a spiritual successor to the +[Blackbird](https://trs.jpl.nasa.gov/handle/2014/52245) planning +system, which similarly uses Java for activity and resource modeling. +Blackbird's design shed light on the myriad choices made in designing +Merlin. + +Predecessors of Merlin and Blackbird, such as [APGen](https://trs.jpl.nasa.gov/handle/2014/45571) and -[SEQGen](https://trs.jpl.nasa.gov/handle/2014/45455), provided a +[SEQGen](https://trs.jpl.nasa.gov/handle/2014/45455), provide a domain-specific language for mission modeling, allowing them to obtain deep, fine-grained information about the composition of a mission model before performing any simulation. In some ways, this provides