Cloud resources request for project 251033

[etrianaGIT]

1. Requester Information:

• PI's Full Name: Lead PI: Enrique Triana, co-PI: Adrienne Marshal
• PI's Affiliated Institute: Lead PI: RTI International, co-PI: School of Mines
• PI's Affiliated Email Address: etriana@rti.org
• Requester's Full Name: Enrique Triana
• Requester's Affiliated Email Address: etriana@rti.org

2. Project Information:

• CIROH Internal Project Number (as per smartsheet): 251033
• CIROH Project Name: Implementing River and Reservoir Operations in the NextGen to Improve Streamflow Forecast

3. Project Description:
Provide a brief description of the project and its goals. This can help the infrastructure team understand the context and purpose of the requested resources. If your project involves developing software or scripts, briefly describe the software you plan to develop.Please highlight how this project will be benefit from and/or provide benefit to other resources on the shared infrastructure.

The overarching goal of this project is to enhance NOAA’s NextGen hydrologic modeling framework by improving the representation of human-driven streamflow regulation, which is a critical limitation in current forecasting systems. Specifically, the project aims to:

1. Identify pilot locations for improving river and reservoir operations modeling.

• Develop a scientifically rigorous methodology to detect “hotspots” where streamflow forecast errors are most influenced by anthropogenic activities such as reservoir operations, diversions, and return flows.
• Use retrospective simulations from the National Water Model (NWM) and observed data from GAGES II to rank locations based on error metrics aligned with NOAA’s operational priorities (e.g., flood prediction, timing accuracy).

2. Develop a flexible, scalable, and operationally relevant reservoir simulation approach.

• Integrate MODSIM, an optimization-based river basin model, into the NextGen framework using a Basic Model Interface (BMI) to enable dynamic simulation of reservoir storage, releases, and diversions.
• Create a streamlined and generalizable approach for linking MODSIM with NextGen hydrologic models using spatial geofabric and automated workflows.
• Explore hybrid modeling techniques, including empirical, rule-based, and machine learning methods, to improve simulation accuracy across diverse regulatory conditions.

3. Evaluate performance and develop an incremental implementation plan.

• Conduct proof-of-concept tests at selected pilot sites to assess improvements in streamflow prediction and flood risk modeling.
• Use CIROH’s TEEHR system for uncertainty analysis and performance evaluation across multiple spatial and temporal scales.
• Design a roadmap for scaling enhanced reservoir operations modeling nationally and provide training materials for operational adoption by NOAA and River Forecast Centers.

4. Resource Requirements:

This project will utilize existing TEEHR infrastructure. We expect that this project will utilize the TEEHR-HUB Jupyter Notebooks as well as the TEEHR Cloud data warehouse and Apache Spark scalable compute

Options:

1. Cloud Provider Options:

• CIROH AWS
• CIROH Google Cloud Platform (GCP)
• CIROH-2i2c JupyterHub
• NWM BigQuery API Access Only

For detailed information about CIROH cloud accounts and APIs:

• AWS: CIROH AWS Account
• Google Cloud: CIROH Google Account
• CIROH-2i2c JupyterHub: CIROH-2i2c JupyterHub
• NWM BigQuery API: NWM BigQuery API

2. Required Services in the Cloud:

List of AWS Services

• EC2

• S3 – public, private, requester pay, bucket name suggestion?

• EBS (Amazon Elastic Block Store)

• EFS

• RDS

• VPC (Virtual Private Cloud)

• DynamoDB

• ECS

• EKS (Kubernetes Cluster)

• Lambda

• Others: TEEHR HUB

  List of Google Cloud Services

• Google Compute Engine

• Google BigQuery

• Google Kubernetes Engine (GKE)

• Google Cloud Storage

• Google VPC

• Google IAM

• Google Cloud Functions

• Dataflow

• Other: please list

5. Working Group
Please select the working group associated with this project:

• Hydrologic Modeling and Prediction Working Group
• Hydroinformatics Working Group
• Community Resources Working Group
• Artificial Intelligence Working Group
• Model & Forecast Evaluation Working Group

6. Timeline

Project start date: 06/01/2025

Project end date: 03/31/2027

Resource need: 2/1/2026 – 3/31/2027

7. Security and Compliance Requirements:
If there are any specific security or compliance requirements for the project, please state them clearly below. This will help ensure that the necessary security measures are in place for the project.

No.

8. Cost Estimation:
Include any cost estimates or requirements for the project. This will help the infrastructure team select the most cost-effective solutions for the project.
Only required for AWS and GCP access. Ignore for others.

AWS Cost Calculator: https://calculator.aws/#/
Google Cloud Pricing Calculator: https://cloud.google.com/products/calculator

We anticipate ~$160/mo. for EC2/EKS expenses and including approximately $10/mo. for ingress expenses and EFS storage expenses

9. Approval:
Requests require management approval, which typically takes 2-3 weeks to process before access is granted.

[arpita0911patel]

This request has been approved by management. Please feel free to use the existing RTI subaccount for this project.

[benlee0423]

@etrianaGIT
Let me know if you have any help from me.