Skip to content

[Feature]: Add parameter to choose NCO version #734

@forsyth2

Description

@forsyth2

How will this affect the next version number?

New feature (increment MINOR version)

Is your feature request related to a problem?

In pull requests that test NCO changes, such as #717, ncclimo has to be manually changed to /home/ac.zender/bin_chrysalis/ncclimo --npo, only to be reverted back once the relevant NCO changes are included in the latest Unified release.

Describe the solution you'd like

It should be straightforward to add a parameter similar to environment_commands that defaults to just ncclimo so that the NCO version can be controlled via the cfg rather than code changes.

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions