We are studying these changes under the auspices of The Jefferson Project at Lake George, a collaborative effort between IBM Research, Rensselaer Polytechnic Institute and The FUND for Lake George. A core component of this project is the coupled system we developed to both observe and physically model the atmospheric, hydrological, hydrodynamic and ecological aspects of the lake and the surrounding region, which is now running operationally. This system includes a real-time, multi-modal observing system composed of in-situ sensors for atmospheric, stream and lake measurement that supports adaptive sampling driven by forecasted conditions from the models. There are over 50 platforms supporting over 500 sensors in the watershed. These data, as appropriate, are used for model verification, and to improve model initial conditions via data assimilation. Another goal for the coupled system is to drive ecological models that explain the interaction of flora and fauna in the lake as a food web. In addition, the coupled physical models drive geometric modelling to enable fixed and interactive visualizations of the watershed. To support both the modelling and the observing systems, there is an underlying cyberinfrastructure that includes a high-performance computing cluster and storage system, and data acquisition hardware and software. To enable data sharing and software reuse, community data models have been adopted for the data generated by this coupled system. As such, this capability is a testbed for addressing related issues in other lake watersheds, estuaries and similar ecosystems.
Atmospheric forcing is considered for both lake circulation and runoff models, the latter of which hydrologically forces the lake. To address the former, we build upon the on-going work with IBM Deep ThunderTM. It is based, in part, on the Advanced Research Weather (ARW) dynamical core of the Weather Research and Forecasting (WRF) community model. It is run operationally daily (initialized at 00 UTC) nested to 333m horizontal resolution for 36 hours for the watershed with high vertical resolution in the lower boundary layer. It operates in the very large eddy (VLES) regime with no boundary-layer parameterization.
For the runoff, a two-dimensional hydrological model has been implemented operationally using the community WRF-Hydro model, coined “Deep Runoff.” For its daily update, it is driven operationally by the 333m-resolution weather model and employs gridded stream routing at 41m resolution. The model has been extended for the transport of dissolved salt, originating from road surfaces. One of the applications is to consider potential nutrient loading in the lake driven from storm water runoff.
For the lake circulation, we build upon the on-going work with IBM DeepCurrent, which is now based, in part, upon the community, Stanford Unstructured Nonhydrostatic Terrain following Adaptive Navier-Stokes Simulator (SUNTANS), a three-dimensional, hydrodynamic model. It has been deployed with variable horizontal resolution from ~27m (near coastlines) to ~70m (in open water) and vertical variable resolution from 0.5 to 1.5m. Operationally, it is driven by the aforementioned meteorological and hydrological models to produce a 36-hour forecast, once per day.
In order to better understand the movement of biota in the lake, particle tracking and ecological models have been implemented, which are driven by the output of SUNTANS. The particle tracking is implemented as an interactive post-process leveraging the simulated velocity fields. A simple ecological model has been developed and deployed operationally that considers nutrients, phytoplankton, zooplankton, small and large detritus, and oxygen. It uses the aforementioned hydrodynamic and meteorological forcings to consider of phytoplankton and zooplankton. Phytoplankton is represented via a proxy, chlorophyll-a.
We will present an overview of each of these models and the observing system along with the results to date, including the model coupling and computing infrastructure required for operations. We will also discuss the automation for the coupled execution, including monitoring, visualization and validation. In addition, we will outline recommendations for future work.