Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UFS WM RT data directories mismatch with S3 data #162

Open
EdwardSnyder-NOAA opened this issue Oct 25, 2024 · 0 comments · May be fixed by #171
Open

UFS WM RT data directories mismatch with S3 data #162

EdwardSnyder-NOAA opened this issue Oct 25, 2024 · 0 comments · May be fixed by #171

Comments

@EdwardSnyder-NOAA
Copy link
Collaborator

The UFS WM RT data directories in the s3 bucket doesn't match the data directories found on premise. This is causing errors when we run the containerized land da ctest as the UFS WM RT scripts are expecting the directories to look how they look on premise. For the interim and the 2.0.0 release, we added modifications to the ctest dockerfile to mimic the data directories on premise. It should be noted that the land da inputs data on premise matches what is in the cloud. The discrepancy is with the UFS WM RT data. When running this ctest Dockerfile on premise it uses the UFS WM RT directory while the containerized land da ctest uses the data found in the land da inputs data from the cloud. The UFS WM RT data in the land da s3 bucket directory doesn't match the UFS WM RT directory.

There are a number of solutions to resolve this issue:

  1. Restructure the data in s3 bucket to mimic the paths on premise. This would require us to restructure the land da inputs directory for all T1 platforms.
  2. Modify the ctest scripts to look for data directory structure in the cloud.
  3. Keep the method we have.
@chan-hoo chan-hoo linked a pull request Nov 18, 2024 that will close this issue
12 tasks
@chan-hoo chan-hoo linked a pull request Nov 18, 2024 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant