USGS_CRIOHCROP_Pywatershed_Arizona

[chopinzi]

1. Requester Information:
This should include the name and contact information of the person making the request.

• PI's Full Name:
• PI's Affiliated Institute:
• PI's Affiliated Email Address: chopinsong@arizona.edu

2. Project Information:
Provide the CIROH project name associated with this research work along with a brief description of the project and its goals. This can help the infrastructure team understand the context and purpose of the requested resources. Please highlight how this project will be benefit from and/or provide benefit to other resources on the shared infrastructure.

<Project title: Advancing irrigated agriculture water use and resources assessment in nextGen and USGS agricultural water use framework: the upper Colorado River basin as a testing case. The project will benefit from the application of CIROH data and computational resources in the shared infrastructure. In detail, we would like to incorporate our BMI-compitable module with pywatershed and calibrate the model, CIROH data resources, computational resources, and HPC environments, which have been well developed for BMI-relevant model activities, will speed up the research progress of our project>

3. Project Description:
If your project involves developing software or scripts, briefly describe the software you plan to develop.

< Our project develops BMI-compitable CRIOH crop module and integrate it with USGS Pywatershed module>

4. Resource Requirements:
Specify the compute, storage, and network resources needed for the project. Be as specific as possible about the number of resources required and any specific configurations or capabilities needed. This information will help the infrastructure team determine the appropriate resources to allocate.

Options:

1. HPC or VM

2. vCPU

3. Memory

4. Disk Space

5. Pantarhei/NSF ACCESS Allocation (specify one)

• More info about Pantarhei: CIROH Pantarhei Documentation
• More info about NSF ACCESS: ACCESS Resource Allocations

5. Working Group

Working Group 1/2/3/4 (select one):

6. Timeline

Project start date: <10/01/2024>

Project end date: <06/30/2026>

In addition, please indicate the expected timeline for the project and when the resources will be needed. This information can help the infrastructure team plan and allocate resources accordingly.

<We expect to use the requested resources as soon as possible, as we are in the process of coupling model with pywatershed>

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.

8. Approval:
Indicate the necessary approval processes or sign-offs required for the request.