You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. Project Information:
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. Please highlight how this project will be benefit from and/or provide benefit to other resources on the shared infrastructure.
We conduct a CIROH FY23 project titled “Comparative Assessment of the NWM Channel Routing Models for Enhanced Streamflow Data Assimilation” to evaluate channel routing models included in T-Route and explore the effect of streamflow data assimilation. One of the project objectives is to run T-Route within the NextGen framework by connecting it with other runoff generation models (e.g., CFE). We will benefit from the CIROH computational resources when running a computing-intensive channel routing model (i.e., diffusive wave routing) and will share our findings and developments with the CIROH community.
3. Project Description:
If your project involves developing software or scripts, briefly describe the software you plan to develop.
We evaluate a streamflow assimilation scheme in T-Route and plan to improve the current assimilation scheme with the Muskingum-Cunge method. We also plan to develop and implement a new assimilation scheme for the diffusive wave method with which streamflow assimilation is not currently capable.
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:
HPC or VM: HPC
vCPU: We can start from a basic number of CPUs if it is scalable as our demand increases.
6. Timeline:
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 would like to have the resources as soon as possible, and the project will end in November 2025.
7. Security and Compliance Requirements:
If there are any specific security or compliance requirements for the project, these should be clearly stated in the request. This will help ensure that the necessary security measures are in place for the project.
None
8. Approval:
Indicate the necessary approval processes or sign-offs required for the request.
None
The text was updated successfully, but these errors were encountered:
1. Requester Information:
This should include the name and contact information of the person making the request.
2. Project Information:
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. Please highlight how this project will be benefit from and/or provide benefit to other resources on the shared infrastructure.
We conduct a CIROH FY23 project titled “Comparative Assessment of the NWM Channel Routing Models for Enhanced Streamflow Data Assimilation” to evaluate channel routing models included in T-Route and explore the effect of streamflow data assimilation. One of the project objectives is to run T-Route within the NextGen framework by connecting it with other runoff generation models (e.g., CFE). We will benefit from the CIROH computational resources when running a computing-intensive channel routing model (i.e., diffusive wave routing) and will share our findings and developments with the CIROH community.
3. Project Description:
If your project involves developing software or scripts, briefly describe the software you plan to develop.
We evaluate a streamflow assimilation scheme in T-Route and plan to improve the current assimilation scheme with the Muskingum-Cunge method. We also plan to develop and implement a new assimilation scheme for the diffusive wave method with which streamflow assimilation is not currently capable.
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:
HPC or VM: HPC
vCPU: We can start from a basic number of CPUs if it is scalable as our demand increases.
Memory: 16GB?
Disk Space: 1TB? (scalable?)
Pantarhei/Wukong/NSF Allocations-JetStream (specify one): Pantarhei
5. Working Group Detail
Working Group 1/2/3/4 (select one): 1
6. Timeline:
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 would like to have the resources as soon as possible, and the project will end in November 2025.
7. Security and Compliance Requirements:
If there are any specific security or compliance requirements for the project, these should be clearly stated in the request. This will help ensure that the necessary security measures are in place for the project.
None
8. Approval:
Indicate the necessary approval processes or sign-offs required for the request.
None
The text was updated successfully, but these errors were encountered: