Add NextGen CONUS Documentation

[stcui007]

This PR update documentation to cover all aspect on computations at CONUS scale involving all submodules so far known to be suitable running within ngen framework. One of the purposes is to summarize previous piece meal documentations in one place.

Additions

Removals

Changes

Updates doc/NextGen_ON_CONUS.md

Testing

Visualization in browser

Screenshots

Notes

This is the final draft version for baseline computation on CONUS.

Todos

Checklist

• [x ] PR has an informative and human-readable title
• [x ] Changes are limited to a single goal (no scope creep)
• [x ] Code can be automatically merged (no conflicts)
• [x ] Code follows project standards (link if applicable)
• [x ] Passes all existing automated tests
• [x ] Any change in functionality is tested
• [x ] New functions are documented (with a description, list of inputs, and expected output)
• [x ] Placeholder code is flagged / future todos are captured in comments
• [x ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• [x ] Reviewers requested with the Reviewers tool ➡️

Testing checklist (automated report can be put here)

1. Running ngen jobs listed in the tables

Target Environment support

• [x ] Linux

[PhilMiller]

Do we require the NetCDF Fortran support for ngen itself? I can readily believe that it's necessary for some of the formulations in the set we give examples for. That may be reason enough to document it as required here, maybe with a note about why.

[stcui007]

NetCDF Fortran is not necessary, at least for now, so I simply removed it.

[stcui007]

Good point. In our tests we always linked in the whole NetCDF directory so everything is made available. Since it is for I/O support, maybe NetCDF Fortran is not really necessary, at least for now.

…

On Mon, Sep 2, 2024 at 5:01 PM Phil Miller - NOAA ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In doc/DEPENDENCIES.md <#854 (comment)>: > @@ -14,7 +14,7 @@ | [pybind11](#pybind11) | submodule | `v2.6.0` | Can be [excluded](#overriding-pybind11-dependency). | | [dmod.subsetservice](#the-dmodsubsetservice-package) | external | `>= 0.3.0` | Only required to perform integrated [hydrofabric file subdividing](DISTRIBUTED_PROCESSING.md#subdivided-hydrofabric) for distributed processing . | | [t-route](#t-route) | submodule | see below | Module required to enable channel-routing. Requires pybind11 to enable | -| [NetCDF Libraries](#netcdf-libraries) | external | \>= `4.7.4` | Enables NetCDF I/O support | +| [NetCDF Libraries](#netcdf-libraries) | external | NetCDF-C \>= `4.7.4`, CXX \>= `4.3.1`, Fortran \>= `4.5.4` | Enables NetCDF I/O support | Do we require the NetCDF Fortran support for ngen itself? I can readily believe that it's necessary for some of the formulations in the set we give examples for. That may be reason enough to document it as required here, maybe with a note about why. — Reply to this email directly, view it on GitHub <#854 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACA4SRNYE5OISUZZOLITNC3ZUTNZPAVCNFSM6AAAAABKNPPWC2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDENZWGE3TEMZQG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>