bwbaker1
commented
8 months ago @wrynearson This ticket is along the lines of what we talked about a few weeks ago. I know this task isn't going to happen anytime soon, but I would appreciate it if you have any thoughts. I'm not fully certain I understand what a federation of documents is, but can ask him to clarify if needed.
Description
Several science teams (missions) have voiced their need to have their related ATBDs stored together. For example, this could be a folder directory for the TEMPO science team that will hold all of the TEMPO ATBDs. However, a new science team Atmospheric Observing System (AOS) is requesting "Federation of ATBDs." AOS is a big mission that will need to write many ATBDs. This is a portion of the email request:
"The document that I am about to start is the overarching framework for all AOS algorithms, the so-called AOS Synergistic Science Software Suite, AOS5 for short. In it I intend to articulate how the suite of algorithms are integrated to deliver AOS science. Specific, detailed ATBDs are expected for each of the components: aerosols, cloud, convection and precipitation, etc. I am thinking of a multi-volume suite of ATBDs, for example:
AOS Synergistic Science Software Suite (AOS5) Volume 1: Integrated Algorithm Suite Volume 2: Elastic Backscatter Lidar Algorithm Volume 3: Synergistic Aerosol Algorithms Volume 4: Synergistic Cloud, Convection and Precipitation Algorithms Volume 5: Synergistic Radiation Algorithms Etc…
Is this multi-volume approach for a given mission consistent with the APT model?
We do need to start creating content for “Volume 1”, so I will leave the qualifier “Volume 1” out of it until I get guidance from your group."
Tasks