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

#1585 fails when each ensemble is using the same diag/field/data yaml file #1630

Open
uramirez8707 opened this issue Jan 8, 2025 · 0 comments · May be fixed by #1632
Open

#1585 fails when each ensemble is using the same diag/field/data yaml file #1630

uramirez8707 opened this issue Jan 8, 2025 · 0 comments · May be fixed by #1632
Assignees

Comments

@uramirez8707
Copy link
Contributor

Describe the bug
#1585 added the ability for each ensemble/nest to have its own diag/field/data yaml tables. However, in the default case where you are running with multiple ensembles and each ensemble is using the same diag/field/data yaml file, the code fails to find the correct yaml because it expects the *_table_ens_XX.yaml to be present and not just *_table.yaml

To Reproduce
This updated tests reproduce the behavior without the code updates

Expected behavior
Those test cases should work

System Environment
This happens in any system

Additional context
N/A

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