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

Correct GraphInfoDir settings in various cylc scenarios. #315

Open
jim-p-w opened this issue Jul 17, 2024 · 0 comments
Open

Correct GraphInfoDir settings in various cylc scenarios. #315

jim-p-w opened this issue Jul 17, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@jim-p-w
Copy link
Collaborator

jim-p-w commented Jul 17, 2024

Some of the scenarios have a GraphInfoDir setting which points to nonexistent directories, causing workflow failures.
There are also a number of different directories being pointed to by various scenarios, which we may want to change to be uniform?

As noted by @ibanos90 in PR #306

Another thing, I noted that in the reference tests you mentioned about the graph file missing. This is because is using /glade/work/liuz/pandac/prepare_mpas/mpas_static_30km as the path for the GraphInfoDir variable, but this folder does not exist anymore. This is also used in scenarios/VerifyingGFSAnalysesFromRDA.yaml. I would suggest to remove the path from the scenario yaml files and use the default path for GraphInfoDir specified in data/Model.py.

We are using graphs from /glade/work/duda/static_moved_to_campaign (in some scenario yamls) and /glade/campaign/mmm/parc/liuz/pandac_common/static_from_duda (default path), however, my guess is that we could use just /glade/campaign/mmm/parc/liuz/pandac_common/static_from_duda.

To Reproduce
Run the ForecastFromGFSAnalysesMPT test scenario.

@jim-p-w jim-p-w added the bug Something isn't working label Jul 17, 2024
@jim-p-w jim-p-w self-assigned this Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant