Enclosure 3 - 80HQTR25R7003 APT ATBD Template.pdf

Enter the Descriptive Title of your Algorithm Theoretical Based Document (ATBD)

A.B. Author1, Bert C. Author2, and David Author3

1Affiliation for author1 2Affiliation for author2 3Affiliation for author3

Corresponding author: enter first and last name (provide email address in parentheses)

Key Points:

● List three key points of your research as presented in this ATBD.

● Each point is a short statement.

● Each point has a 140 character limit.

Version: default is 1.0

Release Date: TBD

DOI: TBD

[Comment to Template Users: All elements above should be the only content on the title page.

In the remainder of the document, blue text should be replaced with content. You can structure subheadings as needed to best present your information. Do not change section order or section titles. When your ATBD is completed, remove any remaining blue content (such as this comment). We recommend APA style. If you are unsure of any formatting, it is best to check the

AGU Grammar and Style guide or for detailed information see the Publication Manual of the

American Psychological Association, Sixth Edition. If submitting to a journal, use 1.5 spacing. If submitting to APT for distribution, use 1.15 spacing for sentences. This template has been set at

1.5 spacing.] https://www.agu.org/Publish-with-AGU/Publish/Author-Resources/Grammar-Style-Guide

Abstract

The abstract is limited to 250 words or less. The abstract should state the general question or problem that is being presented, provide background on the question or problem, briefly describe analyses, and describe the key results.

Plain Language Summary The plain language summary should be written for a broad audience that includes journalists and the science-interested public. It should state the general problem, describe what research was conducted, the result, and why the findings are important. For tips, learn how to write a plain language summary, and check out this example.

Keywords: keyword 1, keyword 2, keyword 3…. (Keywords are used to help indexers and search engines find relevant papers. Use standardized keywords where possible. AGU keywords or GCMD keywords are best)

Version Description Provide the ATBD version number and a brief and meaningful description of how this ATBD differs from any previous one. It is important to provide a lineage of all algorithm versions that came before this algorithm document. A table can be used if needed. If this is the first version of your ATBD, simply state “This is Version 1.0 of the <title> algorithm.”

https://www.agu.org/Share-and-Advocate/Share/Community/Plain-language-summary https://www.agu.org/Share-and-Advocate/Share/Community/Plain-language-summary https://agupubs.onlinelibrary.wiley.com/doi/pdfdirect/10.1029/2020MS002301

1 Introduction The main text should start with an introduction. Provide a brief description of the ATBD which concisely gives users the information needed to understand the relevance and usefulness of the

ATBD.

APT ATBDs have standardized sections and subsections (denoted in this template), but user defined subsections can be added where appropriate. Subsections should be numbered 1.1, 1.2; 1.1.1, 1.2.1, and so on.

2 Context/Background

2.1 Historical Perspective

Provide a brief description of the algorithm development history or lineage. Include a description of how the algorithm came to be in its current form. If appropriate, you may use a table to identify changes between versions.

2.2 Additional Information

Provide additional information such as statistical model description or other preparatory work that led to the algorithm described in this document as needed.

3 Algorithm Description

3.1 Scientific Theory

Provide a description of the scientific principles used in product retrieval including the physics and associated geophysical phenomena observed. Use subheadings as needed to organize the information.

Note: Equations must be centered and numbered.

𝐶𝐶𝐶𝐶 = 2𝛺𝛺 = (𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠)𝑣𝑣 (1)

𝛩𝛩 = 𝑇𝑇 + 𝛤𝛤𝜇𝜇(𝑍𝑍− 𝑍𝑍1000𝑚𝑚𝑚𝑚) (2)

3.1.2 Scientific Theory Assumptions

Describe the assumptions or limitations inherent in this algorithm. Any tables must be numbered in chronological order, must include a descriptive caption centered above the table, and should be referenced in the document text.

Table 1. Provide a caption that describes the information displayed in the table.

Header 1 Header 2

Content 1.1 Content 2.1

Content 1.2 Content 2.2

Content 1.3 Content 2.3

3.2 Mathematical Theory

Provide a description of the mathematical theory essential to the algorithm development.

Figures must be numbered in chronological order, include a descriptive caption centered below the figure, and be referenced in the document text.

Figure 1. Provide a caption that describes the figure.

3.2.1 Mathematical Theory Assumptions

Provide a description of any mathematical assumptions, simplifications and approximations made when deriving the algorithm. All mathematical theories have built in assumptions which need to be communicated to users.

3.3 Algorithm Input Variables

The data that is used as input values must be listed in this section. Data sources are provided in Section 8.

Table 2. Provide an appropriate input variable table title caption

Name Long name Unit

In Var 1 Input Variable 1 e.g., m2

In Var 2 Input Variable 2 e.g., s-2

3.4 Algorithm Output Variables

The data resulting from running the algorithm. These would be variables found in the data product released to the public.

Table 3. Provide an appropriate output variable table title caption

Name Long name Unit

Out Var 1 Output Variable 1 e.g., km2

Out Var 2 Output Variable 2 e.g., degrees

4 Algorithm Usage Constraints

Describe the constraints or limitations on output data use based on the algorithm and the various assumptions made in producing the data product(s).

5 Performance Assessment

5.1 Validation Methods

Describe the details of the scientific methods utilized for algorithm performance assessment validation. Details provided should match the current algorithm maturity.

5.2 Uncertainties

Describe the uncertainties applicable to the validation methods and data used. This may include uncertainty in scientific or mathematical methods and/or errors associated with observation retrievals used for comparisons.

5.3 Validation Errors

Provide estimated errors of the output data product variables. Each variable included in the data product should have an associated error value. Use tables and/or figures as appropriate.

6 Algorithm Implementation

6.1 Algorithm Availability

Provide the web address for the algorithm open-source code and any relevant information needed to execute the algorithm source code. For example, this may include execution instructions, memory requirements, programming languages, dependencies, who to contact, software rights. If this information is already provided at a permanent location, then provide the link to that location with a description.

6.2 Input Data Access

Provide the URL or location of the input data product(s) used in the algorithm. Also, provide the relevant information needed to execute the algorithm source code using the input data. For example, this may include execution instructions, memory requirements, programming languages, and dependencies. If this information is already provided at a permanent location, then provide the link. Use a table if needed to identify the URL and the description for each data product.

6.3 Output Data Access

Provide the algorithm output data persistent identifier, such as the DOI provided that the data products are already publicly available. If none is available leave blank, but instead provide any details needed to access the output data, including the name of the point of contact or any special instructions. If the data products are not yet publicly available but will be at a NASA

DAAC, then note which DAAC and state the identifier information is TBD.

6.4 Important Related URLs

This section is for providing any alternative URLs that may be needed, including links to machine services, ordering services, and DAAC websites. Provide details needed to access input or output data through alternative methods, if needed. Ensure readers have the information needed to understand what the related URL is for. If there are no related URLs, then state “No related URLs are needed.”

7 Significance Discussion Describe the significance of the work or the implications for or contributions to the relevant science fields.

8 Open Research The data availability statements are required for journal submission and optional for inclusion in APT. Provide an Availability Statement for the underlying data needed to understand, evaluate, and build upon the reported research at the time of peer review and publication. Authors must include an availability statement for the software that has a significant impact on the research.

9 Acknowledgements If you intend to submit this ATBD to an AGU journal, the acknowledgements section is required. This section is optional for inclusion of the ATBD in the APT. List all needed acknowledgements which may include people, organizations, funding programs, etc.

Contact Details Provide in this section the contact information and respective role(s) for all contributors to this ATBD. Roles should match the CRediT taxonomy. The following information should be included:

First Name, Last Name (required)

UUID (optional) - universally unique identifier - such as ORCID

URL (optional) - relevant URL related to contacting the person - such as LinkedIn URL

Contact mechanism (required) - phone number, email, etc.

Role(s) related to this ATBD (required) - use CRediT - such as writing - original draft, data curation, methodology, software, etc.

Affiliation - name of associated organization

References The list should contain the full citation of all references cited within the text. References for any data or software used should also be included. Information related to reference formatting can be found in the AGU Grammar and Style guide. The following is an example of a reference in the proper style:

Deng, A., & Stauffer, D. R. (2006), On improving 4-km mesoscale model simulations. Journal of Applied Meteorology and Climatology, 45(3), 361–381. doi:10.1175/JAM2341.1

In-text citation style is (last name of author, YYYY) up to two authors. For more than 2 authors, use et al. after the first author. Example in-text references:

(Smith, 2020) - one author (Doe & Smith, 2021) - two authors (Doe et al., 2021) - three or more authors https://www.agu.org/Publish-with-AGU/Publish/Author-Resources/Grammar-Style-Guide#referenceformat