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

All parameter and configuration files as well as utility functions should be moved from ush to parm #1024

Open
chan-hoo opened this issue Feb 15, 2024 · 0 comments
Labels
NCO EE2 compliance For EE2 compliance to meet NCO implementation standards

Comments

@chan-hoo
Copy link
Collaborator

Description

  • Currently, the ush directory is misused.
  • The parameter and configuration files are located in the ush directory now.
  • The python and bash utility function files are located in the ush directory as well.
  • It should contain the files only called from the ex-scripts.

Solution

  • All parameter, configuration, utility files should be move to the parm directory.
  • The workflow generation should run in the parm directory.

Requirements**

Acceptance Criteria (Definition of Done)

Dependencies (optional)

Alternative Solutions (optional)

@chan-hoo chan-hoo added the NCO EE2 compliance For EE2 compliance to meet NCO implementation standards label Feb 15, 2024
@chan-hoo chan-hoo changed the title All parameter and configuration files as well as utility functions should be moved ush to parm All parameter and configuration files as well as utility functions should be moved from ush to parm Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NCO EE2 compliance For EE2 compliance to meet NCO implementation standards
Projects
Status: No status
Development

No branches or pull requests

1 participant