Skip to content

Scoring rule for LSTM at the CONUS #314

@Amobijones

Description

@Amobijones

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

  • PI's Full Name: Amobichukwu Amanambu
  • PI's Affiliated Institute: University iof Alabama
  • PI's Affiliated Email Address: acamanambu@ua.edu

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.
Using scroing rule for LSTM at the CONUS

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

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

  2. vCPU

  3. Memory

  4. Disk Space

  5. Pantarhei/NSF ACCESS Allocation (specify one)

5. Working Group Detail

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

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.

Summer

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.
Through my email: acamanambu@ua.edu

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions